RT CDP Profiles timing for stitching/merging. | Community
Skip to main content
A
AlexandreSa8
Level 2
September 9, 2025
Question

RT CDP Profiles timing for stitching/merging.

  • September 9, 2025
  • 2 replies
  • 588 views

Hi, everyone.
I have a use case where I need to wait for the RT CDP Profiles to be stitched or merged before using them in an AJO Journey. While I wait for this to happen, I need to minimize the waiting time, which is currently over 40 minutes. I'm wondering if this is the best approach and what the ideal waiting time should be, based on real-life experience and guardrails.

2 replies

itsMeTechy
itsMeTechy
Level 4
September 10, 2025

if you trigger your journey based on audience qualification, then the profile must have stitched already. 

    A
    AlexandreSa8Author
    Level 2
    September 10, 2025

    Hi there.

    It is actually an unauthenticated to authenticated, ECID event that should be stitched, based on durable identities, so I can use the profile data.

    M
    marc_stowe_za
    Level 3
    September 10, 2025

    Hi

     

    if you are using an AJO unitary event type trigger then what i normally do is put a trigger on the event table and set a 30 second wait before it does much. So it triggers off the event datastream and waits 30 seconds which gives the profile enough time to stitch into the identity graph. If you are basing it on audiences when it should take more than about 30 minutes for the stream to push into the dataset and stitch, so your 40 minutes makes sense.

     

    in the example above I send the profile and event info at the same time, but the graph needs to update hence the 30 second delay in the AJO journey.

      Sukrity_Wadhwa
      Community Manager
      Sukrity_WadhwaCommunity Manager
      Community Manager
      September 22, 2025

      Hi @alexandresa8,

      Was the given solution by @marc_stowe_za helpful to resolve your query or do you still need more help here? Do let us know. In case the given solution was helpful, then kindly choose it as the 'Correct Reply'.

      Thanks!

      Sukrity Wadhwa
      Terms & ConditionsAccessibility statement

      Loading footer...