You now know that XDM data is flowing into platform. You’ll explore more about what XDM is in Module 2, as well as how to build your own schema to track custom variables. For now you’re going to look at what happens when you set your Datastream to forward data to Analytics and Audience Manager.
The Adobe Experience Platform Web SDK maps certain values automatically, making a new implementation of Analytics via the Web SDK as quick as possible. The automatically mapped variables are listed here.
For XDM data that is not automatically mapped to Adobe Analytics, you can use context data to match your schema. Then it can be mapped into Analytics using processing rules to populate Analytics variables. Context Data and Processing Rules will be concepts familiar to those that have worked with Analytics in the past, but don’t worry about the details for now if they are new concepts.
You can also use a default set of actions and product lists to send or retrieve data with the AEP Web SDK. To do this, see Products.
To be used by Analytics, XDM data is flattened using dot notation and made available as
contextData. The following list of value pairs shows an example of
All data collected by the edge network can be accessed via processing rules. In Analytics, you can use processing rules to incorporate context data into Analytics variables.
Server-side forwarding is a not a new concept for Audience Manager, and the same process as before applies. You can also sync identities.
In case you want to send data collected by Web SDK to Adobe Analytics and Adobe Audience Manager, follow these steps.
Go to https://experience.adobe.com/launch/ and go to Datastreams. Open your specific Datastream.
Click to open your Development Environment.
You’ll then see this. To enable Adobe Analytics, click the toggle for Adobe Analytics.
You’ll then see this, which means that you need to add the report suite in Adobe Analytics to send data into. In this tutorial, this is out of scope.
Click to open your Datastream’s Development Environment.
You’ll then see this. You can now decide to enable or disable Adobe Audience Manager cookie destinations and/or URL destinations. In this tutorial, this configuration is out of scope.
Next step: 1.6 Implement Adobe Target