Join Adobe Experience Platform experts for a live Ask Me Anything on September 2nd at 8 AM PT!
SOLVED
Data Lake updates
1 Accepted Solution
Correct answer by
@Silvio6 Adobe Campaign Standard (ACS) runs on a cloud-based PostgreSQL database, storing data in a table, while AEP has a different approach.
Even though events like bounces, opens, and clicks are recorded almost instantly in Adobe Journey Optimizer, they are processed into the AEP Data Lake in micro-batches rather than in real-time. Typically, Adobe’s SLA for Data Lake ingestion falls within the 15–30 minute range, influenced by load and pipeline latency. Additionally, when data arrives in the Data Lake, AEP performs schema validation (XDM), enrichments, and identity stitching, which adds some processing time before the profile dataset becomes available. It's important to note that the data is stored in the Data Lake using Parquet format, and metadata indexes are updated, which takes longer than a direct stream.
Thanks, Sathees
Correct answer by
@Silvio6 Adobe Campaign Standard (ACS) runs on a cloud-based PostgreSQL database, storing data in a table, while AEP has a different approach.
Even though events like bounces, opens, and clicks are recorded almost instantly in Adobe Journey Optimizer, they are processed into the AEP Data Lake in micro-batches rather than in real-time. Typically, Adobe’s SLA for Data Lake ingestion falls within the 15–30 minute range, influenced by load and pipeline latency. Additionally, when data arrives in the Data Lake, AEP performs schema validation (XDM), enrichments, and identity stitching, which adds some processing time before the profile dataset becomes available. It's important to note that the data is stored in the Data Lake using Parquet format, and metadata indexes are updated, which takes longer than a direct stream.
Thanks, Sathees
