Activity created from AEM Targeted Component not returned in Web SDK __view__ propositions | Community
Skip to main content
T
test1234567
Level 6
August 18, 2026
Question

Activity created from AEM Targeted Component not returned in Web SDK __view__ propositions

  • August 18, 2026
  • 1 reply
  • 11 views

Hi Team,

We are using:

  • AEM 6.5 LTS
  • Adobe Target
  • AEP Web SDK (Alloy)
  • AEM ↔ Target integration (activities are successfully created in Target)

We have an AEM Targeted Parsys on a page to target the content based on the audience. The activity is successfully synchronized to Adobe Target and is Live.

However, personalized content never displays. The component always renders the default content.

Observations

The rendered HTML contains:

<div class="mboxDefault" data-target-applied="fallback">


and AEM generates maekup:

mboxDefine(...)

CQ_Analytics.TestTarget(...)

 

Web SDK Behavior

The page sends an Alloy request:
 

{

"decisionScopes": ["__view__"]

}
 

and Target returns propositions successfully.

Returned activity IDs:
xxxxx

However, our activity:
123456
 

is never returned in the proposition response.

Activity Details

  • Activity Type: XT
  • Status: Live

Additional Findings

The browser does not have at.js loaded:

typeof adobe?.target

returns: 

undefined

but Alloy is loaded:

typeof alloy

returns:
function

 

Question

Is the OOTB AEM Targeted Component in AEM 6.5 LTS expected to work with AEP Web SDK (Alloy), or does it still require the legacy at.js/mbox delivery model?

If using Web SDK:

  1. Should the activity be returned under __view__ automatically?
  2. Is additional decision-scope configuration required?
  3. Does the OOTB Targeted Component support Web SDK proposition delivery?
  4. Is migration to Experience Fragments/Web SDK-based personalization the recommended approach?

Has anyone successfully used the AEM 6.5 LTS OOTB Targeted Component with Adobe Target delivered exclusively through AEP Web SDK?

 

 

 

 

 


 

 

1 reply

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
August 19, 2026

Hi ​@test1234567 

Based on the detail - it seems like you’re having the legacy implementation even though the Target request successful ..  

The OOTB AEM Targeted Component was originally built around the legacy Target integration model using mbox requests. The presence of mboxDefine() and CQ_Analytics.TestTarget() in the generated markup is a strong indication that the component is expecting the traditional Target delivery mechanism rather than new (Alloy )Web SDK proposition rendering.  

 

So, When using AEP Web SDK, Target activities are returned only for the requested decision scopes. An activity created from the AEM Targeted Component is not automatically converted into a Web SDK __view__ proposition, so it may never appear in the Alloy response even though the activity is Live in Target.

 

Can you confirm which implementation you’re referring to -  

 https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/personlization/target 

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/integration/target 

https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/sites/administering/integration/target-configuring#manually-integrating-with-adobe-target   - here I can see some old references in the documentation like DTM, mbox.js etc .. which no longer exist today. 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/personalization/targeted-content  

 

So I’m not sure if OOTB supports the web sdk implementation at all … and I am not seeing anywhere in documentation so better to go with new approach using Adobe Launch ( Adobe Tags) 

 

Hope this helps. 

Thank you. 

Thanks, Gokul
Terms & ConditionsAccessibility statement

Loading footer...