Update time: July 18, 2023
This article will demonstrate how to implement the Server-side deployment of Adobe Analytics through the Web SDK. If you want to learn about Client-Side Deployment, read more: Step-by-step deployment of Adobe Analytics with Adobe Launch.
Create XDM
In Adobe Launch, click 「Schemas」——「Create schema」——「XDM ExperienceEvent」:
You can customize XDM, or use some built-in XDMs. I use the built-in Consumer Experience Event here. This way is the simplest, it will implement some mappings automatically, without requiring you to customize all the mappings.
Click 「Add 」in Field Group，then search for “Consumer Experience Event”:
Add it, and the basic XDM is there.
This XDM is mainly used for Page View tracking. If you also need to track eVars, Props, Events, you also need to add Adobe Analytics ExperienceEvent Full Extension.
Name this XDM “BCS Event Data”:
This step is complete.
Create Datastreams
Click 「Datastreams」——「New Datastreams」，then do the following configuration:
Name it “BCS”, and the XDM created in the previous step is selected in the Event Schema.
Then click Save.
If the data structure you send is determined, you can map it here in advance.
If not, just click Save.
Return to Datastreams, click on the BCS just created, and click 「Add Service」
- Service: Indicates which Adobe product to send the data to.
- Report Suites ID: Indicates which report suite to send data to.
After setting, save it.
Configure Extensions
Click 「Tags」——「Extensions」——「Catalog」，then search for “Adobe Experience Platform Web SDK“，add it，SDK instances are all default, no need to modify, mainly depends on Datastreams, here indicates which Datastreams (edge server) the data is sent to：
I send the data of the three environments to the Datastreams of BCS. In practice, you need to create different datastreams.
Send Data
It is to send the page data to AA, and the Web SDK uses sendEvent by default, such as：
alloy("sendEvent", {
"documentUnloading": true,
"xdm": {
"commerce": {
"order": {
"purchaseID": "a8g784hjq1mnp3",
"purchaseOrderNumber": "VAU3123",
"currencyCode": "USD",
"priceTotal": 999.98
}
}
}
});
You can also use Custom Event, DCR, ACDL/EDDL, etc.
I don’t use a special method here, just use page loading directly, so I will use Library Loaded in the subsequent Rules.
Configure Data Element
The data sent in the previous step is obtained and stored through Data Elements. The specific setting depends on the way you send data.
The next step is to set the mapping, and map the value obtained by the Data Element to XDM.
Create a Data Element, name it “xmd.event.data”, and configure it as follows:
Map the cid to the tracking code, and the tracking code is in the marketing field:
There is a Web field, which is used to configure page information, set webPageDetails—pageViews—Value to 1, which means tracking pages.
Other web fields are configured according to the actual situation.
Configure Rules
Click 「Rules」——「Add Rule」，then do the following configuration:
The configuration in Action is:
web.webpagedetails.pageViews means tracking pageview.
XDM data is the mapping relationship in data elements.
Test
The last thing is to test, use “configid” to filter the network in the browser developer tool:
Click it, you can see a lot of information, and the configuration data can be found in xdm in events.
You can use the Adobe Experience Platform Debugger to debug.
Finally, check whether there is any data in the AA amount real-time report:
You can see the data, indicating that the data is basically going through.
