Overview
This check validates that your Data Layer (e.g., adobeDataLayer, digitalData, or a custom JSON object) is present and correctly initialized on every page of your website.
In an AEP implementation, the Data Layer acts as the bridge between your website's front-end and the AEP Web SDK. If the Data Layer is missing on a page, the Web SDK will most likely have no source to pull from, resulting in "empty" XDM payloads being sent to the Edge Network. This check ensures that the foundational data structure required for tracking is globally available.
Why it is important
The Data Layer is the single source of truth for your AEP implementation. Its absence leads to systemic data failures:
Incomplete XDM Payloads: AEP Tags use Data Elements to map website info into XDM. If the Data Layer object is missing, these elements return
undefined, leaving your AEP profiles and analytics reports without context (e.g., no Page Name, no Product ID, no User Status).Broken Rule Triggers: Many AEP Tag rules rely on "Data Layer Events" to fire. If the object isn't present to push these events, your tracking tags (like Click tracking or Purchase events) will never trigger.
Personalization Failures: Adobe Target and AEP Offer Decisioning often use Data Layer attributes to determine which experience to show a user. A missing object means the user will always see the "Default" experience.
Implementation Scalability: A consistent Data Layer across all pages allows you to use a single set of AEP Tag rules for your entire site. If the object is missing on certain pages, you are forced to create "one-off" fixes that increase technical debt.
Implementation
We have made implementing this check for AEP Tags simple.
Configure a Data Layer (only needed for custom Data Layer names): ObservePoint recognizes common Data Layer names by default. If you are using a custom data layer add it.
Create an Audit: Set up a scan that crawls your entire website or at least a significant sample. if you completed the previous step, it will report pages missing the Data Layer object.
Review this Report to identify any pages where the object does not exist. Additional variable level analysis can be done in other reports.
ObservePoint identifies the Data Layer by inspecting the browser's JavaScript environment on every page load.
Remediation
If the Data Layer object is missing from specific pages, investigate these common implementation gaps:
Global Header Consistency: Ensure the Data Layer initialization script is included in the global header of your CMS or site template. Check for "landing page" templates or "checkout" pages that might be using a unique, stripped-down header.
Initialization Timing: Ensure the Data Layer is defined above the AEP Tags (Launch) embed code. If the Tag Manager loads first, it may attempt to read from a Data Layer that hasn't been created yet.
Conflict with Minification: Ensure your build process or "uglyfiers" aren't renaming or stripping the global Data Layer object during production deployments.
Expected Object | Status | Impact on AEP |
| Missing | No XDM data collected; rules fail to trigger. |
| Empty | "Success" status sent, but all variables are null/empty. |
| Present | Data Elements map correctly to XDM; full profile enrichment. |
Conclusion
Without a Data Layer, the Adobe Experience Platform is essentially "blind." By using ObservePoint to ensure your Data Layer object is present on every single page, you guarantee a stable and rich flow of information into your Customer Data Platform, enabling accurate analytics and powerful real-time personalization.