Product
Adobe Journey Optimizer (AJO) – Experience Decisioning
AJO Mobile SDK (Messaging)
Mobile App Behavior
The mobile application supports two locales: German(DE) and English (EN).
Users can switch between these locales at any point while navigating the app. When a locale is selected, the entire app UI is translated accordingly.
AJO Setup
Adobe Journey Optimizer (AJO) Experience Decisioning is used to configure multiple offers that are delivered via Code-Based Campaigns.
-
Each offer can be configured to apply to:
-
DE only
-
EN only
-
Both locales
-
A user should be eligible only for offers matching the currently selected locale in the mobile app
-
Locale-based eligibility must be evaluated in real time
Server-Side Capability (Reference)
In a server-side implementation, locale-based eligibility works as expected by passing contextual data in the decisioning request, for example:
This value is then used in offer eligibility rules within AJO.
Mobile SDK Limitation
In the mobile app, offers are fetched using the AJO Mobile SDK, specifically:
-
Messaging.updatePropositionsForSurfaces(SURFACES[])
-
Messaging.getPropositionsForSurfaces(SURFACES[])
However, unlike the server-side API, the Mobile SDK does not provide a mechanism to pass contextual or XDM data (such as preferredLanguage) in the updatePropositionsForSurfaces call. Only the list of surfaces can be provided.
How locale-specific contextual data can be passed to AJO decisioning when using the Mobile SDK?
