AEM target Integration
•Download as PPTX, PDF•
5 likes•2,106 views
The document discusses common issues with integrating Adobe Experience Manager (AEM) and Adobe Target. It provides an overview of how AEM-Target integration works and the configuration steps. It then covers general troubleshooting methods like using the MC Debugger and checking AEM logs. The remainder of the document details some specific common issues seen in AEM-Target integration and their resolutions.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to AEM target Integration
Similar to AEM target Integration (20)
More from Kanika Gera
Recently uploaded
Recently uploaded (20)
AEM target Integration
- 1. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. AEM-Target Integration & Top Issues Kanika Gera| Support Engineer
- 2. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Agenda AEM-Target Integration Configurations AEM- Target Integration: Common Issues Demo Q&A 2
- 3. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. AEM - Target Integration What & Why?
- 4. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 4 AEM-Target Integration Using AEM – Target Direct Integration, without using DTM Use Classic Target – Targeting is driven by Authors within AEM
- 5. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 5 AEM-Target Integration: WHY? Submit data to target when visitors interact with website pages Create personalized experience for targeted Audience Content Targeting A/B Testing Track Conversion rates
- 6. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. How it Works? 6
- 7. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. AEM Target Configuration Target Configuration using Cloud Services
- 8. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 8 AEM-Target Configuration Js will be saved beneath your cloud services configuration and the following will be added to your webpage <script type="text/javascript" src="/etc/cloudservices/testandtarget/adobecq5/_jcr_content/public/mbox.js"></script
- 9. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 9 AEM-Target Configuration • Add the cloud service configuration to your website (page properties -> cloud services -> add service). • This will enable the targeting option in the AEM touch UI
- 10. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. General AEM – Target Troubleshooting Common AEM- Target troubleshooting Methods
- 11. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 11 MC Debugger javascript:void(window.open("","dp_debugger","wi dth=600,height=600,location=0,menubar=0,status =1, toolbar=0,resizable=1,scrollbars=1").document.wr ite("<script language='JavaScript' id=dbg src='https://www.adobetag.com/d1/digitalpulsede bugger/live/DPD.js'></"+"script>")); Save this URL and it can be used to see whether the configuration is correct and traffic is coming.
- 12. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 12 MC Debugger When the page is configured fine and the data is being returned, the screen shows as the diagram. It displays the visitor ID and the report suite ID.
- 13. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 13 AEM Logs A debug level logs can be configured on the following classes: • com.adobe.cq.cq-target-integration • com.adobe.cq.cq-analytics-integration • com.adobe.cq.cq-targetrecommendations
- 14. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 14 AEM Configurations for Target
- 15. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Common AEM Target Integration Issues Common AEM- Target Integration Issues
- 16. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 16 AEM-Target Common Issues & Resolution • Issue: Audiences do not show up in publish instances in AEM 6.2 Solution: This is an intermittent issue and is fixed in AEM 6.2 SP1 • Issue: Audiences can not be deleted in the Touch UI since AEM 6.1 Solution: This is an improvement logged and tracked in NPR-16767 http:// localhost:4502/libs/cq/personalization/touch-ui/content/audiences.h
- 17. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 17 AEM-Target Common Issues & Resolution • Issue: Angular Variables are not compiling in a targeted component present in Angular page. Add a component which has some angular variables; Target that component. The angular variables are not compiling in author and publish mode. Solution: This is an improvement logged as CQ-56726 and has not implemented yet till AEM 6.2
- 18. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 18 AEM-Target Common Issues & Resolution • Issue: Components inside a Container cant be Targeted Solution: This is marked as an improvement and tracked by CQ- 82200. Use Classic UI as workaround
- 19. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 19 AEM-Target Common Issues & Resolution • Issue: When you create the activity it is not saved Solution: It happens when a user trying to create the activity does not has enough right on target side. In the case below, Zofia can create and save activity but Mackay cannot.
- 20. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 20 AEM-Target Common Issues & Resolution • Issue: Segments not Synchronizing between Target and AEM Solution: Verify the account credentials, the AEM logs whether the sync failed or the connectivity to the Target Admin URL configured in AEM Configuration on Felix console
- 21. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 21 AEM-Target Common Issues & Resolution • Issue: Targeted Segments are not shown on Publish Instances Solution: Make sure the dispatcher is not blocking the /etc in the filters and also the anonymous users have read access to the /etc. Make sure the segment id is resolved and all the activities and audiences are activated.
- 22. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 22 AEM-Target Common Issues & Resolution
- 23. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Demo
- 24. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Questions & Answers
- 25. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 25 THANK YOU !!
- 26. © 2017 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Editor's Notes
- The agenda for this session includes various best practices on AEM Assets and
- can author targeted content that sends visitor data to Adobe Target Audiences console enables you to create, organize, and manage audiences for your Adobe Target account or manage segments for ContextHub or Client Context Activity is same as Campaign Audience is same as Segments The Activities console enables you to create, organize, and manage the marketing activities of your brands: Add brands. For each brand, add and configure activities. Administer activities. :
- Installation of AEM Author & Publish instance provisioned either on Cloud ( AMS ) or on premise. AEM License must be procured for such a setup. The Customer needs to be provisioned a valid Adobe Target Account ( Standard or Premium based on the requirement ).The account must have a approver level permission.When you register with Adobe Target, the customer will receive a client code. The client code and the Adobe Target login name and password is required to connect AEM to Adobe Target.
- Synchronize segments from Adobe Target: this option will allow a user to map Experience names defined in AEM to segments created in Adobe Target in order to reuse the full segmentation capabilities provided by Target Use mbox.js delivered by DTM: this will only work if you configured a DTM account. Otherwise, mbox.js will not be loaded. Custom mbox.js allows you to add your custom mbox.js script. If no mbox.js is defined, the out-of-the-box version shipped with AEM will be used. Note the version used in AEM 6.1 doesn't seem 100% up to date, as a result I would recommend: Use mbox.js delivered by DTM or use the mbox.js provided in your Adobe Target account
- localhost:4502/libs/cq/personalization/touch-ui/content/audiences.html
- https://testandtarget.omniture.com/ ClientCode geometrixx Account Username: jjacobs@adobe.com Account password:jacobs111
- "Include resolved segments" is a feature of the target component that allows an user to send the name of the segments to Adobe Target instead of the parameters, and then you can use the cq.resolved.segments profile parameter to target the experience on the Target side. However, this require the campaign to be altered in Target after it has been synced from AEM (with bogus segments, so the synchronization wouldn't fail). Another way to achieve the same thing is to create the "or" segments in Target, synchronize them in AEM (by checking the "Synchronize segments from Adobe Target" option in the Adobe Target cloud service configuration) and then use them in the campaign.