DocumentationExperience PlatformMobile App Tutorial

Create and display offers with Decisioning

Last update: July 23, 2026

CREATED FOR:

  • Beginner
  • Intermediate
  • Developer

Learn how to show offers from Journey Optimizer Decisioning in your mobile apps with Experience Platform Mobile SDK.

Journey Optimizer Decisioning is the next generation of offer management and the successor of Decision Management. The Decisioning feature empowers you to deliver personalized marketing offers by combining a centralized catalog of decision items with a powerful decision engine. Whether you’re tailoring content for individual audiences or optimizing strategies with AI-powered rankings, Decisioning provides the tools to make data-driven decisions at scale. Dive into the key concepts such as decision items, rules, and policies, and explore how these elements work together to select and prioritize the best content for your campaigns. From managing collections and placements to leveraging Adobe Experience Platform data, this comprehensive guide helps you unlock smarter personalization and drive impactful customer experiences.

Architecture {modal="regular"}

Decisioning simplifies personalization by offering a centralized catalog of marketing offers known as ‘decision items’ and a sophisticated decision engine. This engine leverages rules and ranking criteria to select and present the most relevant decision items to each individual. These decision items are seamlessly integrated into messages and experiences across Adobe Journey Optimizer channels: code-based experience, email, SMS, push notifications, and more.

In this lesson, the focus is on the use of the code-based experience channel to deliver offers in the mobile app. And not on explaining in depth all capabilities of the Decisioning solution. Refer to the Decisioning documentation for more information.

NOTE
This lesson is optional and only applies to Journey Optimizer users looking to use the Decisioning functionality to display offers in a mobile app.

Prerequisites

Learning objectives

In this lesson, you will

  • Update your Edge configuration for Decisioning.
  • Create a schema to represent offers.
  • Validate setup in Assurance.
  • Configure a code-based experience channel configuration.
  • Create a code-based experience campaign, based on offers in Journey Optimizer - Decisioning.
  • Implement offers from Decisioning in your app.

Setup

TIP
If you have set up your environment already as part of the Setup A/B tests with Target lesson, you might already have performed some of the steps in this setup section.

Update datastream configuration

To ensure data sent from your mobile app to Platform Edge Network is forwarded to Journey Optimizer - Decisioning, update your datastream.

  1. In the Data Collection UI, select Datastreams, and select your datastream, for example Luma Mobile App.

  2. Select More for Experience Platform and select Edit Edit from the context menu.

  3. In the Datastreams > Folder > Adobe Experience Platform screen, ensure Offer Decisioning, Edge Segmentation, and Adobe Journey Optimizer are enabled.

    • If you plan to only do this Decisioning lesson and not the Decision management lesson, you do not need to enable Offer Decisioning.
    • If you do the Target lesson, select Personalization Destinations, too. See Adobe Experience Platform settings for more information.

  4. To save your datastream configuration, select Save .

    AEP datastream configuration {modal="regular"}

Define your schema

  1. Navigate to the Data Collection interface and select Schemas from the left rail.

  2. Select Browse from the top bar.

  3. Open the Personalized Offer Items - Experience Decisioning schema. This schema is the dedicated schema to configure your offer items, their attributes and metadata.

  4. Add additional field groups to your schema that represent how you want to use offers in Decisioning. Refer to Create schema to understand how you can create schemas. For this lesson, two field groups are created as part of the _techmarketingdemos sandbox configuration: Offer and Offer Metadata. You can see the full structure of the schema below.

    • All mediaAssets fields, like image or imageLowRes are of type DesignAssets and automatically do have destinationURL, edgePath, repository, sourceURL, trackedURL and type string fields.
    • All other fields are either of type Object (for example offerMetadata) or String (for example fullDescription).

    Schema experience decisioning {modal="regular"}

    You can define your Personalized Offer Items - Experience Decisioning schema any way you want. The above structure is just an example that is used for the remainder of this lesson.

  5. Ensure you select Save to save any changes you make to the Personalized Offer Items - Experience Decisioning schema.

Install Journey Optimizer tags extension

For your app to work with Journey Optimizer, you must update your tag property.

  1. Navigate to Tags > Extensions > Catalog.
  2. Open your property, for example Luma Mobile App Tutorial.
  3. Select Catalog.
  4. Search for the Adobe Journey Optimizer extension.
  5. Install the extension.

When only using offers based on Decisioning in your app, in Install Extension or Configure Extension, you do not need to configure anything. If you already have followed the Push notifications lesson in the tutorial, you see that for the Development environment, the AJO Push Tracking Experience Event Dataset dataset is selected from the Event Dataset list.

Implement Journey Optimizer in the app

As discussed in previous lessons, installing a mobile tag extension only provides the configuration. Next you must install and register the Messaging SDK. If these steps aren’t clear, review the Install SDKs section.

NOTE
If you completed the Install SDKs section, then the SDK is already installed and you can skip this step.
iOS

  1. In Xcode, ensure that AEP Messaging is added to the list of packages in Package Dependencies. See Swift Package Manager.

  2. Navigate to Luma > Luma > AppDelegate in the Xcode Project navigator.

  3. Ensure AEPMessaging is part of your list of imports.

    import AEPMessaging

  4. Ensure Messaging.self is part of the array of extensions that you are registering.

    code language-swift 
    let extensions = [
    AEPIdentity.Identity.self,
    Lifecycle.self,
    Signal.self,
    Edge.self,
    AEPEdgeIdentity.Identity.self,
    Consent.self,
    UserProfile.self,
    Places.self,
    Messaging.self,
    Optimize.self,
    Assurance.self
]
Android

  1. In Android Studio, ensure that aepsdk-messaging-android is part of the dependencies in build.gradle.kts in Android ChevronDown > Gradle Scripts. See Gradle.

  2. Navigate to Android ChevronDown app > kotlin+java > com.adobe.luma.tutorial.android > LumaApplication in the Android Studio project navigator.

  3. Ensure com.adobe.marketing.mobile.Messaging is part of your list of imports.

    import import com.adobe.marketing.mobile.Messaging

  4. Ensure Messaging.EXTENSION is part of the array of extensions that you are registering.

    code language-kotlin 
    val extensions = listOf(
    Identity.EXTENSION,
    Lifecycle.EXTENSION,
    Signal.EXTENSION,
    Edge.EXTENSION,
    Consent.EXTENSION,
    UserProfile.EXTENSION,
    Places.EXTENSION,
    Messaging.EXTENSION,
    Optimize.EXTENSION,
    Assurance.EXTENSION
)

Validate setup in Assurance

You do not need to validate the setup for Decisioning in Assurance. Decisioning does not use a specific Experience Platform Data Collection Tag extension, nor does Decisioning requires an additional package for your app. Decisioning relies on the Messaging extension in your app, which you already should have added as part of the Install Adobe Experience Platform Mobile SDKs and Create and send in-app messages lessons in this tutorial.

Create code-based experience channel configuration

To display offers in the screens of your app, you need to configure a dedicated code-based experience channel. This code-based experience channel defines the surface (the location) in the app where you display your offers.

To create a code-based experience channel.

  1. In the Journey Optimizer UI, select Channel Channels from Administration in the left rail.

  2. Select Channel configurations from General Settings.

  3. Select Create channel configuration.

  4. In Channel configuration details:

    Channel configuration details

    1. Enter a Name. For example: LumaMobileAppCodeBased.

    2. Enter a Description. For example: Code-based experience for Luma app used in Mobile SDK tutorial.

    3. Select Code-based experience from the Select channel drop-down menu.

    4. Select one or more marketing actions from the Select one or multiple marketing actions. For example Onsite Personalization.

    5. Select the platforms for which you want to configure the code-based experience. For this tutorial, select iOS or Android or both.

      • For iOS:

        1. Enter of select App id. For example, the identifier of your app: com.adobe.luma.tutorial.swiftui.
        2. Enter of select a location for Location or path inside the app. For example: offersLocation.
        3. Enter a Preview URL. For example: lumatutorialswiftui://.

      • For Android:

        1. Enter of select App id. For example, the identifier of your app: com.adobe.luma.tutorial.android.
        2. Enter of select a location for Location or path inside the app. For example: offersLocation.
        3. Enter a Preview URL. For example: lumatutorialandroid://default.

      • Content

        • Select JSON for the Format.

  5. Select Submit to submit your code-based experience.

Create offers

In this section you create offers for Decisioning.

  1. In the Journey Optimizer UI, select DecisionItems Catalogs from Decisioning in the left rail.

  2. Select Offers from Catalogs to see the list of Offers.

  3. Select Create item.

    1. In the ➊ Attributes step of creating an offer (decision item):

      Attributes for an offer in Decisioning {modal="regular"}

      1. In the Standard attributes section:

        1. Enter an Offer name. For example: Luma - Desiree Fitness Tee.
        2. Enter a Start date or select one using Calendar . For example: 7/1/2026, 12:00 AM.
        3. Enter a End date or select one using Calendar . For example: 12/31/2026, 12:00 AM.
        4. Enter a Priority. For example: 10.
        5. Select one or more appropriate tags from the Tags drop-down menu. For example: Luma - Mobile App.

      2. In the Custom attributes section, enter values for the offer content and metadata. What data you can enter and how you can enter that data is entirely determined by how you have defined your schema for offers. In this tutorial, you want to provide a title, text and an image for each offer.

        1. In the Offer container, within the Media Assets subcontainer:

          1. Select Add from URL for Image and enter an appropriate value for Enter source URL. For example: https://newluma.enablementadobe.com/images/ws05-yellow_main.jpg.
          2. Select Add from URL for Image (high resolution) and enter an appropriate value for Enter source URL. For example: https://newluma.enablementadobe.com/images/ws05-yellow_main.jpg.

        2. In the Offer container, within the Text subcontainer:

          1. Enter a value for Full description. For example: When you're too far to turn back, thank yourself for choosing the Desiree Fitness Tee. Its ultra-lightweight, ultra-breathable fabric wicks sweat away from your body and helps keeps you cool for the distance.
          2. Enter a value for Title. For example: Desiree Fitness Tee.

      3. Select Next.

    2. In the ➋ Elgibility step of the creation of an offer (decision item):

      Create offer item - Eligibility {modal="regular"}

      1. In Eligibility, ensure All visitors is selected.
      2. You do not need to create a capping in the Capping section.
      3. Select Next.

    3. In the ➌ Review step op the creation of an offer (decision item):

      Create offer item - Review {modal="regular"}

      1. Review the offer. You can use Edit to change Standard attributes, Customer attributes, or Profile constraints.
      2. Select Save.

  4. Repeat step 3 (Create item) for the following additional offers:

    table 0-row-4 1-row-4 2-row-4 3-row-4 4-row-4
    Name Title Full description Image and Image (high resolution)
    Luma - Affirm Water Bottle Affirm Water Bottle You'll stay hydrated with ease with the Affirm Water Bottle by your side or in hand. Measurements on the outside help you keep track of how much you're drinking, while the screw-top lid prevents spills. A metal carabiner clip allows you to attach it to the outside of a backpack or bag for easy access. https://newluma.enablementadobe.com/images/ug06-lb-0.jpg
    Luma - Aero Daily Fitness Tee Aero Daily Fitness Tee Need an everyday action tee that helps keep you dry? The Aero Daily Fitness Tee is made of 100% polyester wicking knit that funnels moisture away from your skin. Don't be fooled by its classic style; this tee hides premium performance technology beneath its unassuming look. https://newluma.enablementadobe.com/images/ms01-black_main.jpg
    Luma - Adrienne Trek Jacket Adrienne Trek Jacket You're ready for a cross-country jog or a coffee on the patio in the Adrienne Trek Jacket. Its style is unique with stand collar and drawstrings, and it fits like a jacket should. https://newluma.enablementadobe.com/images/wj08-gray_main.jpg
    Luma - Juno Jacket Juno Jacket On colder-than-comfortable mornings, you'll love warming up in the Juno All-Ways Performanc Jacket, designed to compete with wind and chill. Built-in Cocona™ technology aids evaporation, while a special zip placket and stand-up collar keep your neck protected. https://newluma.enablementadobe.com/images/wj06-purple_main.jpg

    All other values, like Start date, End date, Priority, Capping, Eligibility, and other sthat are not explicitly defined in the table above should be the same across all offers and based on what you defined for the first offer.

You should now have the following list of offers:

Offers list {modal="regular"}

Create a collection

To present an offer to your mobile app user, you must create an offer collection, consisting of one or more of the offers you created. You use rules to select which offers belong to a collection.

  1. In the Journey Optimizer UI, select DecisionItems Catalogs from Decisioning in the left rail.

  2. Select Collections from Catalogs to see the list of Collections.

  3. Select Create collection.

  4. In the Details section:

    1. Enter a Name for the collection. For example: Luma - Mobile App Collection.
    2. Enter a Description for the collection. For example: Collection of Luma mobile app offers.

  5. In the Collection rules section, underneath NUMBER OF ITEMS:

    1. Select Click to create a decision item…

    2. Use Select attribute to select an attribute.

      1. In the Select an attribute dialog select a Decision attribute. For example Offer name.
      2. Select Save.

    3. Use the Equals drop-down menu to select a condition. For example Starts with.

    4. In the textfield enter the value for the condition. For example: Luma -. This value will select all offers which name starts with Luma - to be part of the collection. You can create any kind of rule and also combine rules, using AddCircle Add rule.

  6. Select Create to create the collection.

    Offers - Collection {modal="regular"}

Create a selection strategy

A selection strategy is reusable, and consists of a collection associated with an eligibility constraint and a ranking method to determine the offers to be shown when selected in a decision policy. The decision policy is covered in the Create a campaign section.

In our implementation, the selection strategy is kept as simple as possible.

  1. In the Journey Optimizer UI, select Strategy Strategy setup from Decisioning in the left rail.

  2. Select Selection strategies.

  3. Select Create selection strategy. In the Create selection strategy dialog:

    1. Enter a Selection strategy name. For example: Luma - Mobile App Selection Strategy.

    2. Use Select collection to select the collection for the selection strategy.

      1. In the Collection dialog select a collection. For example: Luma - Mobile App Collection.
      2. Select Save.

    3. Ensure All visitors is selected for Eligibility.

    4. Ensure Offer priority is selected for Ranking method.

  4. Select Create to create the selection strategy.

    Create selection strategy

Create a campaign

You now create a campaign that uses both your offer collection and your code-based experience configuration channel. Campaigns are coordinated marketing actions that deliver content to a specific audience across one or more channels.

As part of the campaign you also create a decision policy. Decision policies are containers for your offers that leverage the Decisioning engine to dynamically return the best content to deliver for each audience member. Their goal is to select the best offers for each profile, while the campaign/journey authoring allows you to indicate how the selected decision items should be presented, including which item attributes to be included in the message.

  1. In the Journey Optimizer UI, select Claxon Campaigns from Journey management in the left rail.

  2. Select Create campaign.

  3. In the Create your campaign dialog, select Scheduled - Marketing as the type of campaign you want to create.

  4. Select Confirm.

  5. In the Properties tab in the Campaign - timestamp screen:

    1. Enter a Name for the campaign. For example: Luma - Mobile App Offers.
    2. Optionally, enter a Description.

  6. Select Actions.

    1. In the Actions section:

      1. Select Add Add action. From the drop-down menu, select Code Code-based experience.
      2. In the Code-based experience action configuration section, select your code-based experience channel configuration LumaMobileAppCodeBased from the Code-based experience channel configuration drop-down menu.

    2. Leave all other settings for Optimization, Languages and Conflict management unchanged.

  7. Select Content.

    1. In the Code-based experience screen, select Edit Edit code.

    2. In the Code-based experience | Channel configuration : LumaMobileAppCodeBased screen:

      1. In the editor, type the following JSON:

        code language-json 
        {
   "version": "1.0",
   "offers": [
   ]
}

      2. Select DecisionItemsConfiguration Decision policy from the second left rail.

        1. Select DecisionItemsConfiguration Add decision policy.

        2. In the Create decision policy dialog wizard, in the ➊ Details step:

          1. Enter a Name for the decision policy. For example: Luma - Mobile App Decision Policy.
          2. Select or enter 2 for the Number of items. This entry assures two offers are returned.
          3. Select Next.

        3. In the Create decision policy dialog wizard, in the ➋ Strategies step:

          1. In the Strategy sequence, select AddCircle Add to add a strategy sequence.

          2. From the context menu, select Selection strategy.

            1. In the Add a selection strategy dialog, select the selection strategy that you created earlier, Luma - Mobile App Selection Strategy.
            2. Select Save.

          3. Select Next.

        4. In the Create decision policy dialog wizard, in the ➌ Review step, review your decision policy.

          1. Select Create to create the decision policy.

      3. Now that a decision policy is available, you can use the Luma - Mobile App Decision Policy rail to insert proper elements from that decision policy into the JSON editor.

        1. In the JSON editor, add a newline between [ and ].

        2. From the Luma - Mobile App Decision Policy rail:

          1. Select Add Insert policy to insert the decision policy as JSON in the editor.
          2. Position the cursor in the editor on a line before the closing {{/each}}.
          3. Select tenant-name (for example: _techmarketingdemos) > Offer > Text content > Title and then +. This adds the title of the offer to the JSON as a title element.
          4. Select tenant-name > Offer > Text content > Full description and then +. This adds the description of the offer to the JSON as a text element.
          5. Select tenant-name > Offer > Media assets > Image > sourceURL and then +. This adds the source URL for the high resolution image of the offer to the JSON as an image element.

          Your final JSON should look similar to below, with updated values for the decision policy identifier and tenant names.

          Final JSON for decisioning policy

          Ensure your title, text, and image JSON elements are wrapped as an object, using { }. And that you do insert a , after that object and just before {{/each}} in the JSON.

      4. Use FileCode Validate to validate the JSON.

      5. Select Save and close.

  8. Select Review to activate.

  9. The Review to activate (Luma - Mobile App Offers) screen provides an overview of your campaign.

    Review to activate

  10. If you do not see any warnings or errors, select Activate to activate the campaign. In the confirmation dialog, select Activate once more.

  11. In the list of campaigns, you should see the campaign changing status from StatusOrange Activating to StatusOrange Processing to StatusBlue Live.

Now your code-based experience campaign is live and you can update the mobile app to use the code-based experience campaign to render offers on the location or suface defined in the code-based experience channel configuration.

Implement offers in your app

As discussed in previous lessons, installing a mobile tag extension only provides the configuration. Next you must ensure the Messaging extension is configured for your app. If these steps aren’t clear, review the Install SDKs section.

iOS

  1. In Xcode, ensure that AEP Messaing is added to the list of packages in Package Dependencies. See Swift Package Manager.

  2. Navigate to Luma > Luma > AppDelegate in the Xcode Project navigator.

  3. Ensure AEPMessaging is part of your list of imports.

    code language-swift 
    import AEPMessaging

  4. Ensure Messaging.self is part of the array of extensions that you are registering.

    code language-swift 
    let extensions = [
    AEPIdentity.Identity.self,
    Lifecycle.self,
    Signal.self,
    Edge.self,
    AEPEdgeIdentity.Identity.self,
    Consent.self,
    UserProfile.self,
    Places.self,
    Messaging.self,
    Optimize.self,
    Assurance.self
]

  5. Navigate to Luma > Luma > Model > Data > general in the Xcode Project navigator. Ensure showDecisioning is set to true and showPersonalization is set to false in the config section.

    code language-json 
    ...
"showPersonalisation": false,
"showDecisioning": true,
...

    These settings ensure Decisioning is used for offers in the Personalisation tab of the app.

  6. Navigate to Luma > Luma > Model > Data > general in the Xcode Project navigator. Ensure a decisioning section with a surface element is configured, identifying the location or surface you have configured for your code-based experience channel. For example: offersLocation.

    code language-json 
    "decisioning": {
   "surface": "offersLocation"
},

  7. Navigate to Luma > Luma > Utils > MobileSDK in the Xcode Project navigator. Find the func updatePropositionsForSurface() function. Add the following code:

    code language-swift 
    // get the propositions for the surfaces configured.
Logger.aepMobileSDK.info("MobileSDK - updatePropositionsForSurfaces: Updating \(surfaces.count) surface(s)")
for surface in surfaces {
   Logger.aepMobileSDK.info("MobileSDK - updatePropositionsForSurfaces: Surface URI: \(surface.uri)")
}

// Call the Messaging extension API to fetch propositions
Messaging.updatePropositionsForSurfaces(surfaces)

Logger.aepMobileSDK.info("MobileSDK - updatePropositionsForSurfaces: Update triggered successfully")

    This function:

    • gets the propositions for the surfaces.

    In this implementation, only one surface is configured and used. The code requires updates if you want to handle multiple configured surfaces.

  8. Navigate to Luma > Luma > Views > Personalization > EdgeDecisioningOffersView in the Xcode Project navigator. Find the func fetchPropositions() async function and inspect the code of this function. The most important part of this function is the Messaging.getPropositionsForSurfaces([surface]) { propositionsDict, error in API call, which

    • retrieves the propositions for the current profile based on the surface,
    • retrieves the offer from the proposition,
    • unwraps the content of the offer (using the parseCodeBasedContent function) so it can be displayed properly in the app.

  9. Still in EdgeDecisioningOffersView, see how in the .task modifier:

    1. Propositions are updated using self.updatePropositionsForSurface().
    2. A brief wait is implemented for Edge network to respond and cache propositions.
    3. The cached propositions are fetched using await self.fetchPropositions.
Android

  1. In Android Studio, ensure that aepsdk-optimize-android is part of the dependencies in build.gradle.kts (Module :app) in Android ChevronDown > Gradle Scripts. See Gradle.

  2. Navigate to Android ChevronDown > app > kotlin+java > com.adobe.luma.tutorial.android > MainActivity in the Android Studio navigator.

  3. Ensure Optimize is part of your list of imports.

    code language-kotlin 
    import com.adobe.marketing.mobile.optimize.Optimize

  4. Ensure Optimize.EXTENSION is part of the array of extensions that you are registering.

    code language-kotlin 
    val extensions = listOf(
   Identity.EXTENSION,
   Lifecycle.EXTENSION,
   Signal.EXTENSION,
   Edge.EXTENSION,
   Consent.EXTENSION,
   UserProfile.EXTENSION,
   Places.EXTENSION,
   Messaging.EXTENSION,
   Optimize.EXTENSION,
   Assurance.EXTENSION
)

  5. Navigate to Android ChevronDown > app > assets > data > general.json in the project navigator. Ensure showDecisioning is set to true and showPersonalization is set to false in the config section.

    code language-json 
    ...
"showPersonalisation": false,
"showDecisioning": true,
...

    These settings ensure Decisioning is used for offers in the Personalisation tab of the app.

  6. Navigate to Android ChevronDown > app > assets > data > general.json in the project navigator. Ensure a decisioning section with a surface element is configured, identifying the location or surface you have configured for your code-based experience channel. For example: offersLocation.

    code language-json 
    "decisioning": {
   "surface": "offersLocation"
},

  7. Navigate to Android ChevronDown > app > kotlin+java > com.adobe.luma.tutorial.android > models > MobileSDK in the Android Studio navigator. Find the suspend fun updatePropositionsForSurfaces(surfaces: List<Surface>) function. Add the following code:

    code language-kotlin 
    // get the propositions for the surfaces configured
withContext(Dispatchers.IO) {
   Log.i("MobileSDK", "updatePropositionsForSurfaces: Updating ${surfaces.size} surface(s)")
   surfaces.forEach { surface ->
      Log.i("MobileSDK", "updatePropositionsForSurfaces: Surface URI: ${surface.uri}")
   }

   Messaging.updatePropositionsForSurfaces(surfaces)
   Log.i("MobileSDK", "updatePropositionsForSurfaces: Update triggered successfully")
}

    This function:

    • gets the propositions for the surfaces.

    In this implementation, only one surface is configured and used. The code requires updates if you want to handle multiple configured surfaces.

  8. Navigate to Android ChevronDown > app > kotlin+java > com.adobe.luma.tutorial.android > views > EdgeDecisioningOffersView.kt in the project navigator. Find the suspend fun fetchPropositionsForSurface(surface: Surface): DecisioningResult = withContext(Dispatchers.IO) function and inspect the code of this function. The most important part of this function is the Messaging.getPropositionsForSurfaces(listOf(surface)) { propositionsMap -> propositionsMap[surface]?.let { propositions -> API call, which

    • retrieves the propositions for the current profile based on the surface,
    • retrieves the offer from the proposition,
    • unwraps the content of the offer (using the parseCodeBasedContent function) so it can be displayed properly in the app.

  9. Still in EdgeDecisioningOffersView.kt, see how in the LaunchedEffect function:

    1. Propositions are updated using MobileSDK.shared.updatePropositionsForSurfaces(listOf(surface)).
    2. A brief delay is implemented for Edge network to respond and cache propositions.
    3. The cached propositions are fetched using fetchPropositionsForSurface(surface).

Validate using the app

iOS

  1. Rebuild and run the app in the simulator or on a physical device from Xcode, using Play .

  2. Go to the Personalization tab.

  3. Scroll to the top, and you see two random offers displayed from the collection that you have defined in the Surface Offers Location tile.

    {width="300"}

    The offers are random, as you have given all offers the same priority and the ranking for the offers is based on priority.

Android

  1. Rebuild and run the app in the simulator or on a physical device from Android Studio, using Play .

  2. Go to the Personalization tab.

  3. Scroll to the top, and you see two random offers displayed in the upper box from the collection that you have defined in the Surface Offers Location tile.

    {width="300"}

    The offers are random, as you have given all offers the same priority and the ranking for the offers is based on priority.

Validate implementation in Assurance

To validate the offers implementation in Assurance:

  1. Review the setup instructions section to connect your simulator or device to Assurance.

  2. Select Events in the left rail.

  3. Look for Message propositions response events in the event list.

  4. In the right pane, unfold such an event: ACPExtensionEventData > propositions > 0 > items > 0 > data > content > offers. You see two offers 0 and 1 each with the data you expect.

    Decisioning offers assurance

Next steps

You should now have all the tools to start adding more functionality to your Journey Optimizer - Decisioning implementation. For example:

  • apply different parameters to your offers (for example, priority, capping)
  • collect profile attributes in the app (see Profile) and use these profile attributes to build audiences. Then use these audiences as part of the eligibility rules in your decisioning.
  • combine more than one surface.
SUCCESS
You have enabled the app to display offers using the Decisioniong.
Thank you for investing your time in learning about Adobe Experience Platform Mobile SDK. If you have questions, want to share general feedback, or have suggestions on future content, share them on this Experience League Community discussion post.

Next: Perform A/B tests

recommendation-more-help
platform-learn-help-tutorial-mobile-sdk