Adobe Experience Platform Implementation: Adobe Experience Platform Tags fire at the optimal time

Overview

This check validates that the Adobe Experience Platform (AEP) Web SDK is triggered at the ideal moment during the page load cycle. "Optimal timing" means firing the tag late enough that the Data Layer is fully populated, but early enough to capture users who may navigate away quickly. For AEP, this is typically balanced between the Library Loaded and Top of Page events.

Why it is important

Timing is a trade-off between Data Richness and Data Volume:

Preventing Under-reporting: If a tag fires too late (e.g., Window Loaded), you lose data from "bouncers" who leave before the page fully finishes loading.
Ensuring Data Integrity: If a tag fires too early (e.g., before the Data Layer is initialized), the XDM object will be missing critical information like Page Name or User ID, leading to "Anonymous" or "Untitled" entries in AEP.
Personalization Speed: When using AEP for Adobe Target or Offer Decisioning, the tag must fire early to prevent "flicker" or content shifting, which degrades the user experience.

Implementation

ObservePoint automates timing validation through Audits:

1. Create an Audit: Go to Audits and create a new one; Enter the URL and run the scan

2. Configure the Tag Rule in the Standards section (Tag & Variable Rules): Set up a new rule including the following details:

Trigger: URL Contains - adobedc.net/ee
Rule: Load Event - Is Not - Window Loaded

3. Review the Report Template: Use the pre-built ObservePoint report to identify tags firing significantly after the primary page content is visible.

Remediation

If your AEP tags are firing at sub-optimal times, consider these adjustments:

Standardize on "Top of Page": For most implementations, triggering the Web SDK on the Library Loaded or Page Top event is the optimal balance for AEP.
Synchronize the Data Layer: Ensure your Data Layer is defined above the AEP Tags embed code in the <head>. This allows the tag to fire early while still capturing all required metadata.
Audit "Window Loaded" Triggers: If rules are set to fire on window.onload, move them to an earlier trigger unless they specifically require assets (like images) to be fully rendered.
Optimize Custom Code: Review any "Custom Code" blocks that might be delaying the rule execution through heavy processing or long setTimeout functions.

Conclusion

Optimal timing ensures your Adobe Experience Platform data is both complete and comprehensive. By using ObservePoint to monitor firing sequences, you ensure your implementation is fast enough to capture every visitor and smart enough to capture every variable.