Advertisers with an Advertising Cloud-Adobe Analytics Integration Only
Advertisers with Advertising Cloud DSP only
Analytics sends site traffic metrics (such as page views, visits, and time spent) and any Analytics custom or standard events to Advertising Cloud hourly, using the EF ID as the key. These Analytics metrics then run through the Advertising Cloud attribution system to connect the conversions to the click and exposure history.
If you don’t already have the code, then contact the Advertising Cloud support team.
You can perform validation using any packet sniffer type of tool (such as Charles, Fiddler, or Chrome Developer Tools) by comparing the values of the four IDs between the request going to Advertising Cloud and the request going to Analytics, as outlined below.
Open Chrome Developer Tools and click the Network tab.
Filter the Network tab by “last” and review two rows:
The second row is the call sending the request to Advertising Cloud. It begins as follows:
If you don’t see the call to Advertising Cloud, then it might not be the first page view of your visit. For testing purposes, you can remove the cookie so that the next call will be the first page view for the corresponding visit:
Filter on “/b/ss” to see the Analytics hit.
Compare the ID values between the two hits. All of the values will be in query string parameters except for the report suite ID in the Analytics hit, which is the URL path immediately after /b/ss/.
|ID||Analytics Parameter||Advertising Cloud Parameter|
|Experience Cloud IMS Org||mcorgid||_les_imsOrgid|
|Supplemental Data ID||sdid||_les_sdid|
|Analytics Report Suite||The value after /b/ss/||_les_rsid|
|Experience Cloud Visitor ID||mid||_les_mid|
Open the Adobe Experience Cloud Debugger on your homepage.
Go to the Network tab.
In the Solutions Filter toolbar, click Advertising Cloud and Analytics.
In the Request URL – Hostname parameter row, locate “lasteventf-tm.everesttech.net.”
In the Request – Parameters row, audit the signals generated, similar to Step 3 in “How to Confirm the Code with Chrome Developer Tools.”