Adobe Experience Platform allows you to ingest Adobe Analytics data through the Analytics Data Connector (ADC). ADC streams data collected by Analytics to Platform in real-time, converting SCDS-formatted Analytics data into Experience Data Model (XDM) fields for consumption by Platform.
This document provides an overview of Analytics and describes the use-cases for Analytics data.
Analytics is a powerful engine to help you learn more about your customers, how they interact with your web properties, see where your digital marketing spend is effective, and identify areas of improvement. Analytics handles trillions of web-transactions per year and ADC allows you to easily tap into this rich behavioral data and enrich the Real-time Customer Profile in a matter of minutes.
At a high level, Analytics collects data from various digital channels and multiple data centers around the world. Once the data is collected, Visitor Identification, Segmentation and Transformation Architecture (VISTA) rules and processing rules are applied to shape the incoming data. After raw data has gone through this lightweight processing, it is then considered ready for consumption by Real-time Customer Profile. In a process parallel to the aforementioned, the same processed data is micro-batched and ingested into Platform datasets for consumption by Data Science Workspace, Query Service, and other data-discovery applications.
See Processing rules overview for more information on processing rules.
XDM is a publicly documented specification that provides common structures and definitions for an application to use to communicate with services on Experience Platform.
Adhering to XDM standards allows data to be uniformly incorporated, making it easier to deliver data and gather information.
To learn more about XDM, please see the XDM System overview.
When a source connection is established for bringing Analytics data into Experience Platform using the Platform user interface, data fields are automatically mapped and ingested into Real-time Customer Profile within minutes. For instructions on creating a source connection with Analytics using the Platform UI, see the Analytics data connector tutorial.
For detailed information on the field mapping that occurs between Analytics and Experience Platform, please visit the Adobe Analytics field mapping guide.
|Analytics Data||Expected Latency|
|New data to Real-time Customer Profile (A4T not enabled)||< 2 minutes|
|New data to Real-time Customer Profile (A4T is enabled)||< 15 minutes|
|New data to Data Lake||< 45 minutes|
|Backfill data (13 Months of Data or 10 Billion events, whichever is lower)||< 4 weeks|
Latency will vary depending on customer configuration, data volumes, and consumer applications. For example, if the Analytics implementation is configured with
A4T the latency to Pipeline will increase to 5-10 minutes.
Every hit from the Analytics data connector contains a primary identifier that is dependant on whether an ECID or an AAID exists. If there is an ECID, the ECID is designated as the primary identifier. If there is an AAID, then the AAID is designated as the primary.