Guardrails
Guardrails are recommended thresholds that provide guidance for data, observed latencies and system usage in Adobe Experience Platform and applications. Guardrails reflect system constraints and performance expectations to optimize customer architecture and use case performance, and help to avoid errors or unexpected results. Guardrails are not intended to be service level agreements, service level agreements are documented in the Product Descriptions linked below and in the customer license agreements. Guardrails are intended to provide guidance in architecting solutions for specific customer use cases to ensure stability and execution.
For information on specific service level agreements for applications and features, refer to the Application and feature descriptions section at the bottom of this page.
Note that for any customer use case that has strict latency or volume requirements, Adobe recommends reviewing your use case in detail with your Adobe Account Team and Implementation partner. In certain cases it is advisable to test and observe a given use case implementation prior to production launch of the use case to observe and understand expected behavior - as each customer implementation has varying factors at play including the nature and cadence of data ingestion, the specifics of the segment rules being built and the various activation channels and payloads - each use case implementation will have varying observed performance. As such it is best to establish and test the expected performance up front to ensure proper architecture and implementation according to the latency and performance requirements of the use case.
Guardrails Reference Documentation for Adobe Experience Platform and Applications
The following pages provide information about guardrails for Adobe Experience Platform features, services, and applications:
Experience Platform applications
Experience Platform services
End-to-end latency diagrams end-to-end-latency
Experience Platform Edge Network and Hub Primary Observed Latencies edge-hub-latencies
The following diagram depicts the primary edge and hub observed latencies to be aware of when architecting use case on the Experience Platform and Applications.
Data ingestion data-ingestion
The diagram below displays expected data ingestion latency values through streaming ingestion and batch ingestion when bringing data into Real-Time CDP. Click the image to see a high-resolution version.
Segmentation segmentation
The diagram below displays expected latency values when working with audiences in the Real-Time CDP segmentation service. Click the image to see a high-resolution version.
Real-time Customer Data Platform & Edge Network adobe-edge-latency
The diagram below displays expected latency values when leveraging the Edge Network - for example to leverage RTCDP audiences in Adobe Target. Click the image to see a high-resolution version.
Customer Journey Analytics customer-journey-analytics
The diagram below displays expected latency values when working with Customer Journey Analytics. Click the image to see a high-resolution version.
Journey Optimizer journey-optimizer
The diagram below displays expected latency values when working with Adobe Journey Optimizer. Click the image to see a high-resolution version.
Application and feature descriptions application-feature-descriptions
For information on feature-specific service level agreements, refer to the product descriptions below: