Adobe’s server-side technology is powered by Adobe Experience Platform (AEP). This allows Adobe customers to route multiple Adobe products through a single tag using the AEP SDK. Analytics, Personalization, Commerce and more can all use the same AEP tag.
If you have migrated to AEP, but you can't tell which Adobe products have successfully on-boarded to the AEP SDK on all your pages, this guide is for you.
Learn how to use ObservePoint to validate Adobe Server Side tagging through Adobe Experience Platform (AEP). This guide explains the new tag categorization method, enhanced reporting features, and how to get the most accurate data from your AEP implementation.
Overview of Adobe Experience Platform (AEP):
AEP consolidates network requests for multiple Adobe products.
Server-side tagging enhances performance and security but can complicate tag identification because most variable level information is passed as part of the request payload instead of query string parameters. It is this payload that we use to correctly identify the underlying technology.
How AEP is Recognized in ObservePoint?
Deep Payload Inspection: ObservePoint analyzes AEP request payloads to identify the underlying technology.
Event Type Reporting: Get detailed visibility into:
Analytics (historically Adobe Analytics)
Adobe Personalization (historically Adobe Target)
Adobe Commerce
Custom event types
How Will AEP Be Represented in ObservePoint Reports?
Four new AEP tags will be added to the ObservePoint tag identification system:
Adobe Experience Platform (AEP): Analytics
Adobe Experience Platform (AEP): Personalization
Adobe Experience Platform (AEP): Commerce
Adobe Experience Platform (AEP): Custom (for all custom event types)
Adobe Experience Platform (AEP) Interact
How Will Existing AEP Tags Be Affected?
ObservePoint will stop reporting Adobe Experience Platform (AEP) Collect.
Required Action: Update Alerts, Consent Categories, and Rules
Because AEP Interact and AEP Collect will no longer be recognized by ObservePoint, updating Rules, Consent Categories, or Alerts is a critical next step.
Any rules, consent categories, or alerts that reference these tags will need to be updated to expect one of the four new AEP tags noted above.
If updates are not made:
Rules may fail if they rely on these tags.
Alerts may fail to trigger as expected.
Consent Categories may show the four new tags as unapproved.
What Are the Differences Between the AEP Tags We Support?
Adobe Experience Platform (AEP) Loader: This the alloy.js JavaScript library and enables AEP technologies to work on a website.
Adobe Experience Platform (AEP) Intentify: Used for user identification and profile stitching. These requests are crucial for recognizing users across different devices and sessions, enabling personalized experiences and accurate audience segmentation.
Adobe Experience Platform (AEP) Interact/Collect: These requests constitute the client-side portion of AEP and are responsible for carrying events and data between the client (e.g., a website or app) and Adobe’s server-side services. One of the following four tags will be recognized instead of AEP Interact/Collect based on the payload sent to Adobe:
Adobe Experience Platform (AEP): Analytics - Measures user interactions (like clicks or video plays) are sent via AEP Interact to Adobe Analytics, which records the events for reporting and analysis.
Adobe Experience Platform (AEP): Personalization - Request is triggered to determine the best personalized offer. Adobe Target rules and logic will then respond with targeted promotions or recommendations.
Adobe Experience Platform (AEP): Commerce - Events that capture eCommerce transaction data, including order details, purchase amounts, and product information.
Adobe Experience Platform (AEP): Custom - Tracking for custom events defined by the Adobe customer.