Adobe Experience Platform Implementation: Adobe Experience Platform interaction events capture the correct variables

Overview

This check validates that your Adobe Experience Platform (AEP) Web SDK interaction events—such as link clicks, form submissions, or custom button interactions—are capturing the specific metadata required by your business requirements.

In AEP, these interactions are sent as XDM (Experience Data Model) objects. Unlike legacy analytics that used a flat list of Props and eVars, AEP uses a nested JSON structure. This check ensures that when a user interacts with an element, the resulting web.webInteraction or a custom XDM object contains the correct values for fields like name, type, and URL.

Why it is important

Capturing the correct variables during an interaction is essential for granular behavioral analysis:

Accurate Pathing Analysis: If the web.webInteraction.name is missing or generic (e.g., "Link Click" instead of "Footer - Contact Us"), you cannot distinguish which site elements are driving user engagement.
Conversion Attribution: For events like "Add to Cart" or "Lead Start," missing variables (like productID or formName) prevent you from understanding the specific drivers of your conversion funnel.
Schema Compliance: AEP is schema-driven. If an interaction event captures a variable that is incorrectly formatted or missing a required field, the entire event may be rejected by the Edge Network.
Audience Segmentation: Real-time segments in AEP often rely on specific interaction flags. If an interaction event fails to capture the "Member Level" or "Region" variable, users may not be placed into the correct personalization segments.

Implementation

Validating consent behavior takes three steps: interact with the banner at scale, simulate the resulting user paths, and codify the expected outcome as a rule.

Note: Validating these criteria requires Journeys that cover your key user experiences.

Use ClickAll+ to interact with your consent banner at scale. Because consent behavior depends on a click (Accept All, Reject All, or a partial-consent selection) rather than just a page load, ClickAll+ is the recommended way to trigger those banner interactions across a large set of pages within an Audit and capture what fires — or doesn't fire — as a result. Follow the ClickAll+ Solution Implementation Guide to configure the on-page action for your CMP's Accept/Reject selectors.
Build Journeys for your priority consent scenarios. For conversion paths where consent behavior matters most (checkout, lead forms, account creation), create Journey variants that simulate Opted In, Opted Out, and GPC Signal Enabled states. This lets you confirm AEP respects consent throughout a full user path, not just on the landing page.
Codify the expected behavior with Tag & Variable Rules. Create a rule with a WHEN condition scoped to your "Reject All" or GPC-enabled Audits/Journeys, and an EXPECT condition confirming the AEP Web SDK tag is either absent or excludes the relevant XDM fields. This turns a one-time check into an ongoing, automated pass/fail signal in your reports.

Remediation

If AEP tags are firing outside of the consent state a user selected, investigate these common causes:

CMP/Tag load order: The AEP Web SDK extension or library is loading before the CMP has resolved the user's choice, so the tag fires on default behavior rather than actual consent.
Missing consent gate on the extension: The Web SDK's built-in consent settings (e.g., setConsent) aren't wired to your CMP's callback, so AEP never receives the updated consent status.
Category mismatch: Your CMP's consent categories aren't mapped to the specific AEP data collection purposes, so a "Reject All" selection doesn't actually restrict the request.
GPC not honored: The Global Privacy Control signal isn't being read and passed into the same consent logic used for banner-based opt-out.

Conclusion

Because consent is captured through interaction rather than page load, validating it requires ClickAll+ to trigger the relevant banner states, Journeys to confirm behavior holds across a full user path, and Rules to make the check repeatable. Together, these give you an automated, ongoing signal that your AEP implementation is honoring the choices your visitors actually make.