Adobe Target and Offer Decisioning integration - Mobile App | Community
Skip to main content
N
Neal_Davis
April 29, 2025
Solved

Adobe Target and Offer Decisioning integration - Mobile App

  • April 29, 2025
  • 2 replies
  • 863 views

Hi Everyone, Good Day!


I'm working on personalizing experiences for a mobile app and planning to use Adobe Target and Offer Decisioning integration. If we implement the Adobe Optimize SDK in the app (referring https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/experience-cloud/target) , will it be able to fetch personalized offers from OD via Target and display them in real time?

Just want to confirm that this setup works for mobile personalization before going too far down this path.

 

Has anyone here done this before? Anything I should watch out for?


Many thanks in advance,
Neal

 

Best answer by VikasOhlan

Hello @neal_davis ,

 

Yes, you are on the right path - this setup works just fine. When you implement Optimize SDK in your mobile app and configure your DataStream/Edge Network appropriately, your app can request and receive personalized offers created in OD and delivered them via Target activities. Here, OD will decide on the decisioning part regarding which offer to deliver and Adobe Target will act as a delivery middleware. 

Just make sure your org has the 'OD offers in Target' feature enabled — if not, Adobe Support can quickly toggle it on. Once that is done, option to 'Add Offer Decision' will be available in form based activity setup as shown below:

In Mobile App, use updatePropositionsWithCompletionHandlerAndTimeout() to retrieve the offers for any decision scope. Hope this helps!

Regards,
Vikas Ohlan
LinkedIn Profile 

2 replies

VikasOhlan
Adobe Employee
VikasOhlanAdobe EmployeeAccepted solution
Adobe Employee
April 29, 2025

Hello @neal_davis ,

 

Yes, you are on the right path - this setup works just fine. When you implement Optimize SDK in your mobile app and configure your DataStream/Edge Network appropriately, your app can request and receive personalized offers created in OD and delivered them via Target activities. Here, OD will decide on the decisioning part regarding which offer to deliver and Adobe Target will act as a delivery middleware. 

Just make sure your org has the 'OD offers in Target' feature enabled — if not, Adobe Support can quickly toggle it on. Once that is done, option to 'Add Offer Decision' will be available in form based activity setup as shown below:

In Mobile App, use updatePropositionsWithCompletionHandlerAndTimeout() to retrieve the offers for any decision scope. Hope this helps!

Regards,
Vikas Ohlan
LinkedIn Profile 

    AnkitJasani29
    AnkitJasani29
    Level 6
    April 30, 2025

    Hi @neal_davis ,

     

    Yes, your plan is on the right track, and Adobe Target + Offer Decisioning via the AEP SDK can indeed support mobile app personalization in real time - but there are a few important details to be aware of.

     

    What works:
    If you implement the AEP SDK and configure Adobe Target along with Offer Decisioning, you can:

    • Personalize experiences on mobile in real time.
    • Fetch offers that are stored in Adobe Journey Optimizer > Offer Decisioning.
    • Use Target activities to deliver offers based on real-time context and identity.

     

    How it works:

    • Mobile app SDK (AEP SDK) sends context data (location, language, user traits, etc.) to Adobe Experience Edge.
    • Adobe Target is called through the SDK, which evaluates the request.
    • If you're using Offer Decisioning, Target can fetch offers from AJO/OD based on predefined rules and decisions.
    • The offer is returned to the app, rendered natively or through HTML (depending on your implementation).

     

    Key things to watch out for:
    Identity Syncing: Make sure ECID is set up properly for consistent visitor recognition. If the identity is inconsistent, targeting might fail.

    Edge Network Usage: Offers are fetched from the Edge Network, not directly from OD or Target servers. Ensure your implementation supports this flow.

    Real-time decisioning limits: While decisioning can be fast, depending on payload size, network latency, or rules complexity, there might be some delay. Test for responsiveness.

    Offer format compatibility: JSON offers are easier to use in native apps. HTML offers may require a WebView and are less performant.

    Debugging Tools: Use Adobe Assurance for mobile SDK debugging — this will save you a lot of time during implementation.

    Caching: Consider the caching strategy for repeat visitors, especially if offers change dynamically.

     

    Some teams reported friction when trying to deeply personalize offers based on user behavior without first unifying the customer profile in AEP or sending sufficient context. So it's critical to ensure your context data and identity are consistent across all channels (web, mobile, email, etc.).

    Terms & ConditionsAccessibility statement

    Loading footer...