Advertisers with an Adobe Advertising-Adobe Analytics Integration Only
Advertisers with Advertising DSP only
SDID) or b) uses the Adobe Experience Platform Web SDK
generateRandomID method to generate a
StitchID. Either ID is used to stitch data from Adobe Advertising to the visitor’s Adobe Analytics hit. Adobe Analytics then queries Adobe Advertising for the AMO ID and EF ID associated with the ad exposure. The AMO ID and EF IDs are then populated in their respective eVars. These values persist for a designated period (by default, 60 days).
Analytics sends site traffic metrics (such as page views, visits, and time spent) and any Analytics custom or standard events to Adobe Advertising hourly, using the EF ID as the key. These Analytics metrics then run through the Adobe Advertising attribution system to connect the conversions to the click and exposure history.
<script> if("undefined" != typeof AdCloudEvent) AdCloudEvent('IMS ORG Id'); </script>
<script> if("undefined" != typeof AdCloudEvent) stitchId = AdCloudEvent('IMS ORG Id').generateRandomId(); </script>
StitchID is included in your Analytics call.
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 Adobe Advertising 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 Adobe Advertising. It begins as follows:
If you don’t see the call to Adobe Advertising, 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:
adcloudcookie, and verify that the cookie contains
_les_v(last visit) with a value of
yand a UTC epoch timestamp that expires in 30 minutes.
ad cloudcookie and refresh the page.
(Implementations that use the Experience Cloud Identity Service
visitorAPI.js code) Filter on
/b/ss to see the Analytics hit.
(Implementations that use the Experience Platform Web SDK
alloy.jscode) Filter on
/interact to verify that the request payload to the Edge Network contains
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
|ID||Analytics Parameter||Edge Network||Adobe Advertising Parameter|
|Experience Cloud IMS Org||
|Supplemental Data ID||sdid||
|Analytics Report Suite||The value after
|Experience Cloud Visitor ID||mid||
Open the Adobe Experience Cloud Debugger on your homepage.
Go to the Network tab.
In the Solutions Filter toolbar, click Adobe Advertising and Analytics.
In the Request URL – Hostname parameter row, locate
In the Request – Parameters row, audit the signals generated, similar to Step 3 in “How to Confirm the Code with Chrome Developer Tools.”
visitorAPI.jscode) Make sure the
Sdidparameter matches the
Supplemental Data IDin the Adobe Analytics filter.
alloy.jscode) Make sure the value of the
advertisingStitchIDparameter matches the
Sdidsent to the Experience Platform Edge Network.