identify audiences across Adobe solutions so insights are taken from one solution can be applied in another.
Adobe's Dynamic Tag Manager (DTM) allows marketers to manage tags, distribute data, and simplifies tag management.
Integrate Adobe Dynamic Tag Management with AEM so that you can use your Dynamic Tag Management web properties to track AEM sites. Dynamic Tag Management enables marketers to manage tags for collecting
Cloud Services - Digital Marketing cloud services are the AEM mechanism to configure integrations between AEM and cloud services such as Adobe Marketing
Steps to follow before integrating DTM with AEM:
Dynamic Tag Management is used load client library for Adobe Target. AEM synchronizes segments from Adobe Target
Integrate your AEM sites with Adobe Target to personalize content in your pages:Implement content targeting.Use Target audiences to create personalized experiences.Submit context data to Target when visitors interact with your pages.Track conversion rates.
When you target a component in AEM author, the component makes a series of server-side calls to Adobe Target to register the campaign, set up offers, and retrieve Adobe Target segments (if configured). No server-side calls are made from AEM publish to Adobe Target.
Integrating AEM with Adobe Target requires knowledge of Adobe Target, AEM Activities management, and AEM Audiences management. You should be familiar with the following information:
- Adobe Target (See the Adobe Target documentation).
- AEM Activities console (See Managing Activities).
- AEM Audiences (See Managing Audiences).
When working with Adobe Target, the following is the maximum number of artifacts allowed within a campaign:
- 50 locations
- 2,000 experiences
- 50 metrics
- 50 reporting segments
Author targeted content using Targeting mode of the AEM touch-optimized UI. Targeting mode and the Target component provide tools for creating content for experiences:
- Easily recognize the targeted content that is on the page. A dotted line forms a border around all targeted content.
- Select a brand and an activity to see the experiences.Add experiences to an activity or remove experiences.
- Perform A/B testing and convert winners (Adobe Target only).
- Add offers to an experience by creating offers or using offers from a library.
- Configure goals and monitor performance.Simulate the user experience.
- For more customization, configure the Target component.
- Activity - rule set defining which content is shown to which visitor
- Experiences - collection of offers, bound to an audience
- Offer - content to be shown in a location
- Audience - class of visitors defined by specific criteria
- Location - specific area on the page where content is targeted
|contexthub.kernel.js||The first include in your page header. This
loads the Context Hub base library
including the code for the stores.
|satelliteLib.js||The second include in your page template.
This loads the DTM library.
||This is the request that loads the data for
our donation store.
||This is the request made by the auto-
|These are the 2 targeted locations on our
The difference between the /ajax request for the global mbox and the /standard request for the targeted components is that we don’t expect content to be returned by the global mbox request. So we can send this as an asynchronous request that just sends the profile data required for the current user and then forget about it.
The targeted components and their mbox however are expected to return actual content to be displayed. In the lab setup we are using a synchronous request for the targeted components to make sure our page loads smoothly without any flicker. For the mbox managed by the targeted components this means that on the AEM publish instance we are using an mboxCreate call to define the mbox. But using synchronous requests can affect page load performance.
When inspecting the responses for the local mbox request you can see that AEM just synchs a JS snippet that takes care of loading the experience from AEM. This means the actual content stays in AEM and will be delivered from there, which allows to leverage AEMs powerful content aggregation and management