Overview
This check validates that the Adobe Experience Platform Web SDK Analytics Tag is present and successfully executing on every page of your website. In an AEP-driven architecture, this tag acts as the single gateway for analytics and data collection.
Unlike legacy implementations, where different tags might be spread across different tools, AEP relies on a unified "Global Page View" event. If a page is missing this tag, that user’s entire journey, including their profile attributes and segment membership, becomes fragmented, leading to inaccurate attribution and broken personalization.
Why it is important
Ensuring 100% coverage of AEP Tags is the foundation of a reliable Customer Data Platform (CDP):
Unified Customer Profile: AEP builds a 360-degree view of the customer. If a user visits a "dark" page (one without a tag), their activity isn't stitched to their profile, leading to incomplete behavioral data.
Accurate Attribution: If landing pages or conversion pages are missing the AEP tag, marketing attribution models will fail to credit the correct channels, leading to skewed ROI reports.
Consistent Personalization: If you are using Adobe Target or AEP Offer Decisioning, a missing tag means the user will see default content instead of personalized experiences, creating a jarring and inconsistent brand journey.
Privacy & Consent Compliance: The AEP Web SDK handles consent signaling. If a page lacks the tag, you cannot reliably enforce a user's "opt-out" preference for that specific portion of their visit.
Implementation
We have made implementing this check for AEP Tags simple.
Create an Audit that crawls your entire site or a specific set of high-value URLs.
Then, check the pre-built ObservePoint report for Tag Presence.
Remediation
If pages are identified as missing an AEP Tag, follow these steps to restore coverage:
Verify Tag Manager Deployment: Ensure that the AEP Tags (Launch) embed code is present in the
<head>of the global header template. Check for CMS templates that might be bypassing the standard header.Check Rule Conditions: If the tag is present but not firing, review the "Global Page View" rule in AEP Tags. Ensure there are no restrictive "Exceptions" or "Conditions" (like specific path exclusions) preventing it from triggering on those pages.
Audit Load Order: Ensure the Web SDK isn't being suppressed by a Consent Management Platform (CMP). If a user hasn't interacted with a banner, some CMPs block all tags, which may appear as a "missing tag" in an audit if not configured correctly.
Investigate JavaScript Crashes: Check the No Console Errors report. A script error occurring early in the page load can stop the AEP Tag from ever initializing.
Conclusion
Total coverage is non-negotiable for a data-driven organization. A single missing tag on a high-traffic page can compromise the integrity of your entire Adobe Experience Platform ecosystem. By using ObservePoint to automate the discovery of tracking gaps, you ensure that every customer touchpoint is captured, stitched, and utilized for real-time engagement.