Table of Contents
For customers with Adobe Analytics, this is the easiest and recommended way to implement. Adobe Analytics forwards data to AAM on Adobe’s backend, allowing for one less request on the page. This also enables key integration features and conforms with our best practices for Audience Manager code implementation and deployment.
- Implement the Experience Cloud ID Service .
- Have administrator rights for Adobe Analytics and Adobe Launch
Enable Server-Side Forwarding
Click on Admin-Report Suites in Adobe Analytics:
Select the Report suite you want to set up, and then click Edit Settings-General-Server Side Forwarding:
Read the info and check the box to Enable Server-Side Forwarding for the report suite(s)：
The official documentation suggests that you still need to map the report suite, but it is not necessary, because when you create a report suite, it is already associated with the Experience Cloud Org by default.
Implementation using Adobe Launch
Check the box to Automatically share Analytics Data with Audience Manager . This will add the Audience Manager “Module” (code) to the Analytics AppMeasurement.js implementation. Add your “Audience Manager Subdomain” (also known as the “Partner Name,” “Partner ID,” or “Partner Subdomain”).
There is another one that can be checked below-Show advanced settings, but generally do not need to check, use the default:
- containerNSID: The default is 0, However, if your company needs to customize ID syncs with a different container, you can specify that container ID here.
- Name: The default is aam_uuid, Optional. This configuration lets you set an Adobe cookie in the first-party domain. This cookie contains the UUID.
- Days: The validity period of the cookie. The default is 100 days.
- Domain: the primary domain of the cookie,
Emphasize again, There is no need for custom settings in Show advanced settings.
Publish and Test
After publishing the library, open the website, and then open the Adobe Experience Cloud Debugger:
You can see that Adobe Audience Manager is deployed.
Then open the browser’s developer tool, find the network, search for a request containing Adobe, and find a request with AQB or S. This is the data sent to Adobe Analytics:
look for a “callback” parameter. It will be set to something like this: s_c_il.doPostbacks，The number 1 means forward once.
You can also check Preview, it will contain references to doPostbacks, as called in the request, and most importantly, it should have a “stuff” object. This is where AAM segment IDs will be sent back to the browser. If you have the “stuff” object, SSF is working!
It may take up to 4 hours for the enabled SSF in the Analytics Admin Console to take effect. If there are errors, please wait for a while before testing.