Known Limitations or Delays When Using Streaming Data Sources in Adobe RTCDP | Community
Skip to main content
AnkitJasani29
AnkitJasani29
Level 6
April 23, 2025
Solved

Known Limitations or Delays When Using Streaming Data Sources in Adobe RTCDP

  • April 23, 2025
  • 1 reply
  • 559 views

I'm working with streaming data sources and wanted to check if there are any known limitations or delays when it comes to processing or qualifying data in real time.

 

Specifically, I’m curious about:

  • Any known lags or edge cases where real-time processing might not behave as expected

  • Best practices to minimize delays or troubleshoot issues

Would love to hear from others who’ve worked with streaming data in RTCDP. Thanks in advance for your help!

Best answer by AnkitJasani29

RTCDP typically ingests events in under a few seconds, but network latency, payload size, or throttling policies (API limits) can introduce slight delays.

 

Real-time identity stitching is not truly immediate. While profiles can update quickly, identity graph updates may take a few minutes, especially in complex merging scenarios.

 

Real-Time Segments are evaluated immediately after an event hits the profile, but there's often a 1-3 minute delay before the segment qualification becomes visible or usable in activation.

 

1 reply

AnkitJasani29
AnkitJasani29AuthorAccepted solution
Level 6
April 25, 2025

RTCDP typically ingests events in under a few seconds, but network latency, payload size, or throttling policies (API limits) can introduce slight delays.

 

Real-time identity stitching is not truly immediate. While profiles can update quickly, identity graph updates may take a few minutes, especially in complex merging scenarios.

 

Real-Time Segments are evaluated immediately after an event hits the profile, but there's often a 1-3 minute delay before the segment qualification becomes visible or usable in activation.

 

    Terms & ConditionsAccessibility statement

    Loading footer...