Adobe Target sending wrong experience to mobile app | Community
Skip to main content
A
alben
Level 2
October 9, 2023
Solved

Adobe Target sending wrong experience to mobile app

  • October 9, 2023
  • 1 reply
  • 3845 views

Hi everyone,

 

we are trying to integrate Adobe Target with our native Android app which uses the Adobe AEP Mobile SDK.

Apart from the fact that documentation for this kind of integration is not really clear, there are tutorials and demos related to old version of the Adobe Target SDK, which use functions deprecated from the current version.
The only documentation available seems to be this one: https://developer.adobe.com/client-sdks/documentation/adobe-target/

 

That said, coming back to the question, we managed to integrate the Adobe Target extension in our app, and we are testing a simple retrieval of an HTML according to the user which uses the app.
We created a Target Activity with two experiences.
Experience A contains an HTML for an Audience which contains only our test consumer.
Experience B contains a different HTML for the "All visitors" audience.

 

We tried to enable the Mobile Preview mode and we have checked that visually both experiences work correctly.

The issue is that when we disable the Mobile Preview mode, and we use the app with the test consumer that should be receiving Experience A, it actually receives the fallback expereince B, as if the user of the app was not recognized.

We did not pass the ECID to the Target request call in any custom way, assuming that is dealt with automatically with the integration.

And it seems to be correct, since from the Android Studio logs, we see that the calls to/from Target contain the correct "marketingCloudVisitorId"/ECID.

 

We do not understand why the user qualifies for the wrong experience though.

We tried with both an AB test and XT activity.


Any help woul be appreciated.

Many thanks!

Alberto

    Best answer by alexbishop

    Hi

    I'm also trying to implement Adobe Target using the Mobile SDK (via Edge), and I have some questions:

     

    1) To implement Adobe Target for mobile (using Mobile SDK) is it necessary to install the Target extension? When we implemented Analytics using the Mobile SDK it was not necessary to install the Analytics extension. Same for our Web SDK Analytics & Target implementation.

    2) The Journey Decisioning extension is really mandatory for implementing Target mobile using SDK (via Edge)? In my environment I cannot select the "Offer Decisioning" and "Edge Segmentation" options in the Datastream configuration (https://developer.adobe.com/client-sdks/edge/adobe-journey-optimizer-decisioning/)

     

    Thanks

     


    For i) the typical approach involves using Adobe Tags (fka Launch) & the extension; this is effectively generating a config file, so if you don't want to use Tags for some reason, you can either programatically set config options or use your own config file

    ii) Yes, that extension is necessary; however, you don't need "Edge Segmentation" or "Offer Decisioning" enabled at the datastream level, you just need Adobe Target enabled 

    1 reply

    alexbishop
    Adobe Employee
    alexbishopAdobe Employee
    Adobe Employee
    October 26, 2023

    Could you explain/share a screenshot of how you've defined the "test consumer" audience?

      A
      albenAuthor
      Level 2
      October 26, 2023

      Sure, basically my test audience contains just a couple of ECID as a fixed rule. These are the ECID of my android emulators, where I'd expect to receive Experience A. I'm doing this just for testing purposes.

      This audience is activated to the Target Destination.
      In Target this audience is connected to Experience A.
      The All visitor "audience" to Experience B.
      I always receive experience B even if my ECID is inside the audience for Experience A.

      In this example you see a batch audience, but I also tested with Streaming and Edge audiences with the same result.


      Thanks!

        alexbishop
        Adobe Employee
        alexbishopAdobe Employee
        Adobe Employee
        October 27, 2023

        Ah ok so it's a CDP audience being shared to the Target destination. In that case I'm wondering how you have implemented Target in the Mobile App. You'd need to use the Platform Edge and Journey Decisioning extensions in order to utilise that CDP audience; I'm wondering if you've implemented the Target library instead? 

         

        In case you haven't seen it before, there is a tutorial here that explains the different steps & also provides a sample application which includes that Journey Decisioning implementation

          Terms & ConditionsAccessibility statement

          Loading footer...