Alerts

This reference provides more information about the alerts Adobe Experience Platform Auditor displays for tests.

Alerts show issues you should be aware of, but that don’t affect your score. These are best practice recommendations that, in some cases, may not apply to your implementation.

Test Criteria Recommendation

Advertising Cloud - Correct Conversion Tag Implemented

Weight: 0

Check whether the correct conversion tag is used.

Warning: Using the deprecated TubeMogul conversion tags can result in data loss.

Upgrade your conversion pixels to the new Advertising Cloud image-only conversion tags.

This can be most easily accomplished with the Advertising Cloud extension for Adobe Experience Platform Launch.

Advertising Cloud - Correct JS Tag Used

Weight: 0

Advertising Cloud should use latest JavaScript tags.

Upgrade your Advertising Cloud JavaScript to the latest version. Using the deprecated JavaScript versions can result in lost functionality.

This can be accomplished more easily through the use of the Advertising Cloud extension for Platform Launch.

Advertising Cloud - Image-only tag

Weight: 0

The Advertising Cloud image pixel format should match one of the following recommended formats:

  • http(s)://rtd.tubemogul.com/upi/?sid=<HASH_VALUE>

  • http(s)://rtd-tm.everesttech.net/upi/?sid=<HASH_VALUE>

  • http(s)://pixel.everesttech.net/px2/<NUMERIC_ID>?

Upgrade your Advertising Cloud pixels to the new Advertising Cloud image-only tags, which ensure you are taking advantage of the full Advertising Cloud functionality.

This can be most easily accomplished with the Advertising Cloud extension for Platform Launch.

Advertising Cloud - Segment Pixels DSP Syncing Enabled

Weight: 0

Check whether the TubeMogul segment pixel contains a DSP Syncing setting, and recommend that the setting be added to the pixel.

The DSP Syncing setting is determined by the use of a query string parameter, so

IF the tag is being fired to ("https://rtd.tubemogul.com/upi/?sid=<HASH_VALUE>"

OR "http(s?lang=en)://rtd-tm.everesttech.net/upi/?sid=<HASH_VALUE>"

OR "http(s?lang=en)://pixel.everesttech.net/px2/<NUMERIC_ID>?"

AND the tag contains the URL parameter "sid=")

THEN check to see if the URL parameter "cs=0" or "cs=1" exists, and if not recommend that "cs=1" be added to those pixels so that the audience match rates can improve.

Add the URL parameter "cs=1" to your Advertising Cloud pixels so that DSP Syncing can occur, which increases audience match rates.

This can most easily be accomplished with the Advertising Cloud extension for Platform Launch.

DTM - pageBottom callback placement

Weight: 0

Additional information

Dynamic Tag Management requires the _satellite.pageBottom() function. Add the inline script immediately prior to the closing </body> tag to ensure proper DTM functionality.

Note: It is best practice that the tag be the last tag in the <body>. If it's found within the <body> tag, it has a chance of functioning, but as it is not best practice, it could function incorrectly or with unexpected or undesired results.

Add the inline script immediately prior to the closing </body> tag to ensure proper DTM functionality.

DTM - Self-Hosted

Weight: 0

Additional information

The DTM library is being hosted on Adobe's Akamai instance at assets.adobedtm.com.

Self-hosting is the recommended approach for loading DTM because it provides greater control of website performance through cache control, reducing third-party script dependencies, and greater control of the publishing process. The DTM libraries can be hosted and managed through your own web hosting or CDN.

Self-hosting is the recommended approach for loading DTM on a page. Although DTM hosting via the Akamai CDN works in most cases, self-hosting improves page performance.

Experience Cloud ID Service - Use only one AdobeOrg

Weight: 0

Additional information

In a normal MCID implementation, a single AdobeOrg should be used.

Validate that multiple AdobeOrg IDs exist for this implementation.

Launch - pageBottom callback placement

Weight: 0

Additional information

Platform Launch should have a pageBottom callback function defined last in the body of the page if synchronously deployed.

Note: It is best practice that the tag be the last tag in the <body>. If it's found within the <body> tag, it has a chance of functioning, but as it is not best practice, it could function incorrectly or with unexpected or undesired results.

Platform Launch requires the _satellite.pageBottom() function for synchronous deployments. Add the inline script immediately prior to the closing </body> tag to ensure proper Platform Launch functionality.

Launch - Self-Hosted

Weight: 0

Getting started with Adobe Experience Platform Launch

Platform Launch asynchronous deployment

The Platform Launch library is being hosted on Adobe's Akamai instance at assets.adobedtm.com.

Self-hosting is the recommended approach for loading Platform Launch because it provides greater control of website performance through cache control, reducing third-party script dependencies, and greater control of the publishing process. The Platform Launch libraries can be hosted and managed through your own web hosting or CDN.

Although Platform Launch hosting via the Akamai CDN works in most cases, it is recommended that self-hosting be implemented as the first step in improving page performance.

Launch - should be asynchronously deployed

Weight: 0

Additional information

Platform Launch should be asynchronously deployed for optimal performance.

Include the async parameter in the inline script to ensure proper async Platform Launch functionality

Target - Content in mboxDefault

Weight: 0

Additional information

Content should exist in mboxDefault when using at.js.

Verify that the content is available.

On this page