Expand my Community achievements bar.

SOLVED

Web SDK - Adobe AdCloud Analytics

Avatar

Level 4

Hi all, I am in the process of migrating the existing Adobe AdCloud tags to the web SDK. The documentation suggests that the only thing which is needed is the script below.

 

<script src="https://www.everestjs.net/static/le/last-event-tag-latest.min.js">
<script>
     if("undefined" != typeof AdCloudEvent)
          stitchId = AdCloudEvent('IMS ORG Id','rsid').generateRandomId();
</script>

 

Above code is in the sync tag, which which is loaded straight after the AEP base code.

 

Validation / Debugging:

  1. Open Chrome Developer Tools and click the Network tab.

  2. Load a website page that contains the Analytics for Advertising JavaScript.

  3. Filter the Network tab by last and review two rows:

Franc_G_0-1729603601105.png

 

  • The first row is the call to the JavaScript library and is titled last-event-tag-latest.min.js.

  • The second row is the call sending the request to Adobe Advertising. It begins as follows: _les_imsOrgId=[your_imsOrgId_here]&_les_url=[your_encoded_url]

    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 is the first page view for the corresponding visit

 

WHEN I filter on /interact to verify that the request payload to the Edge Network contains advertisingStitchID

I can not find anything in the _adCloud property in the xdm request (obviously no advertisingStitchIDeither).

 

Documentation: JavaScript Code for Analytics for Advertising | Adobe Advertising

 

Question: Do I need to see OR interact with the ad in order to do this test ?

I know the question sounds a bit silly, but just wanted to be 100% sure.

 

1 Accepted Solution

Avatar

Correct answer by
Level 4

Got some help from Adobe engineering team.

Troubleshooting:

Some general troubleshooting steps that can be performed are:

  • Review SDK and Data Stream Configurations: Ensure that both the AEP Web SDK and the data streams are correctly configured to handle the advertisingStitchID.

  • Check Integration Setup: Verify that the integration between AEP and Adobe Advertising Cloud is complete and correctly configured.

  • Validate Data Mappings: Ensure that the advertisingStitchID is correctly mapped within the AEP Data Collection UI.

  • Test for JavaScript Errors: Use browser developer tools to check for JavaScript errors that might be affecting the SDK's operation.

  • Analyse Timing of Events: Ensure that the advertisingStitchID is generated before or at the time the SDK sends its payload.

  • Review Consent Management Configuration: Make sure that consent management settings are correctly configured and that they align with user consent preferences.

  • Consider Browser and Ad Blocker Impact: Test the implementation across different browsers and with ad blockers disabled to see if these factors are affecting the capture of the advertisingStitchID.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 4

Got some help from Adobe engineering team.

Troubleshooting:

Some general troubleshooting steps that can be performed are:

  • Review SDK and Data Stream Configurations: Ensure that both the AEP Web SDK and the data streams are correctly configured to handle the advertisingStitchID.

  • Check Integration Setup: Verify that the integration between AEP and Adobe Advertising Cloud is complete and correctly configured.

  • Validate Data Mappings: Ensure that the advertisingStitchID is correctly mapped within the AEP Data Collection UI.

  • Test for JavaScript Errors: Use browser developer tools to check for JavaScript errors that might be affecting the SDK's operation.

  • Analyse Timing of Events: Ensure that the advertisingStitchID is generated before or at the time the SDK sends its payload.

  • Review Consent Management Configuration: Make sure that consent management settings are correctly configured and that they align with user consent preferences.

  • Consider Browser and Ad Blocker Impact: Test the implementation across different browsers and with ad blockers disabled to see if these factors are affecting the capture of the advertisingStitchID.