Overview
This check validates that your Adobe Experience Platform (AEP) Web SDK tags are firing only once per intended user action.
Duplication occurs when the same XDM (Experience Data Model) payload is sent multiple times for a single page load or a single click. Because AEP feeds real-time services like Journey Optimizer and Customer Journey Analytics, duplicate tags can lead to a "double-counting" effect that compromises your entire data ecosystem.
Why it is important
Duplicate AEP tags introduce significant noise into your data and can lead to costly operational errors:
Inflated Behavioral Metrics: Duplicates artificially double your Page Views, Sessions, and Interaction counts, making it impossible to calculate true conversion rates or engagement levels.
Journey Orchestration Errors: If you use Adobe Journey Optimizer (AJO), a duplicate "Order Confirm" event could trigger the same "Thank You" email or "Push Notification" twice to a single customer, damaging the brand experience
Profile Fragmentation: While AEP attempts to deduplicate data at the ingestion level, high-frequency duplicate hits can cause processing delays or unexpected behavior in calculated profile attributes.
Increased Costs: Adobe Experience Platform and the Edge Network often operate on "Addressable Audience" or "Call Volume" licensing models. Sending twice the necessary data can lead to unnecessary overages in your Adobe contract.
Implementation
We have made implementing this check for AEP Tags simple.
Use the pre-built ObservePoint Tags Report displaying the pages where duplicate tag events are showing up.
Create a Journey and review the Variable Summary column for the number (2) representing duplicates OR contact our team to help set up a custom alert for Journey tag duplicates.
ObservePoint flags these as duplicates if two or more identical AEP network requests are detected for a single event trigger.
Remediation
If your AEP tags are firing in duplicate, investigate these common configuration errors:
Multiple Rule Triggers: Check your AEP Tag (Launch) property for overlapping rules. For example, you may have one rule firing the Web SDK on "Library Loaded" and another firing it on "Core - Window Loaded."
Hardcoded vs. Tag Manager: Ensure the AEP Web SDK base code hasn't been hardcoded into the site's template while also being deployed via AEP Tags. This often results in two
alloy("sendEvent")commands executing simultaneously.Looping Custom Code: Review any Custom Code blocks in your Tag rules. A JavaScript loop or a poorly placed event listener (e.g., an
addEventListenerthat is called multiple times without being cleared) can cause the SDK to fire repeatedly.Single Page Application (SPA) Logic: In SPAs, ensure that your "View Change" trigger is properly managed. If the "initial load" event and the "virtual page view" event both trigger on the first page, a duplicate hit will occur.
Extension Configuration: Verify that "Enable Link Tracking" in the Web SDK extension isn't conflicting with a manual "Link Click" rule you created. If both are active, a single click will send two requests.
Duplicate Type | Common Cause | Remediation |
Page View Duplicate | Overlapping Rule Triggers | Consolidate "Page Load" events into a single global rule. |
Interaction Duplicate | Link Tracking Conflict | Disable "Auto-tracking" in the SDK if using manual click rules. |
Recursive Duplicate | JS Event Bubbling | Use |
Conclusion
Clean data is the prerequisite for effective analysis and personalization. Duplicate tags act as a "multiplier" for errors, leading to incorrect business decisions and poor customer experiences. By using ObservePoint to monitor for and eliminate duplicate AEP requests, you ensure that your Adobe Experience Platform implementation remains a source of truth for your organization.