Issue with Adobe target powered personalization when an activity is created in AEM and pushed to Adobe Target.

[prashantonkar]

Issue Description

When the AEM is integrated with Target through Adobe I/O and an XT activity is created in AEM and synced to target, the end-user personalization fails to work as expected on the end site. Instead of replacing only the personalized part of the HTML, the whole HTML is being replaced with personalized content.

Steps to reproduce

1. Created an Adobe I/O integration for target API under default workspace
2. Provided this integration "Editor" product role in admin console
3. Created IMS Configuration, Legacy target integration configuration in AEM. Connection is verified to be successful.
4. Enabled context hub at template level.
5. Created a new brand under personalization.
6. In sites added the configuration path and added target cloud configuration.
7. Opened a page, add a text component
8. Switched to targeting mode.
9. Selected my brand and created an activity

Step9

 10. Selected the text component and clicked on targetStep10

 11. Configured the target options. Provided a custom mbox idStep1112. Configured two experiences for two audiences (Chrome and firefox users) and corresponding text in the text component.Step1213. Saved the activity with metrics as Engagement and page views.LastStep

Issue

When I view the targeted page in publish or select "View as published" in author, I just see the personalized content covering the entire page.

actual behaviour

Expected Behavior

Only the default content should be replaced with personalized content, not the entire page.

Expected

Issue Analysis

1. When the offers are created using API, instead of configured custom mbox, a place holder is being sent.

Log entry:

23.04.2020 11:43:48.573 *DEBUG* [0:0:0:0:0:0:0:1 [1587622426050] POST /libs/cq/analytics/testandtarget/command HTTP/1.1] com.day.cq.analytics.testandtarget.impl.service.WebServiceImpl Target API Request: POST https://mc.adobe.io/xyz/target/offers/content {"name":"apr-23-wknd-mbox--author-chrome_browser-targettest1-text","content":"<script type='text/javascript'>(function() { CQ_Analytics.TestTarget.pull('/content/campaigns/wknd/master/April23-TestActivity/chrome_browser/targettest1-text.tandt.html','${mbox.name}','1.0.0');})();<\/script>"}

This can be verified in Adobe Target also – in offers

2. Hence, the global mbox id is received as response from target API call (Instead of custom mbox id)
Request:

Response:

 3. If I edit the offer in target and replace the placeholder with my custom mbox id, the targeting is working fine.

Question:

Can the mbox be sent in request while creating an offer instead of sending a '${mbox.name}' placeholder ?