Expand my Community achievements bar.

Adobe Summit is live! Tune in to take part in the premier digital experience event.

Analytics segments not triggering personalizations in Target

Avatar

Level 1

Hello,

 

I've created two segments in the segment builder in Adobe Analytics and shared them with the Experience Cloud so they could be used as audiences in Adobe Target. These 2 segments were tests, so I set them up so that they would catch all users (one was set to visitors with a visit > -1 and the other was set to visits with a Day that exists). I can see the segments as audiences in target, and i can create the activities with them but I can't see the personalizations when visiting the site. In the trace it picks up as a matched activity, but in unmatched audiences i see both of my segments. What am i doing wrong?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

3 Replies

Avatar

Level 1

Also note this is a webSDK implementation.

Avatar

Employee Advisor

Hi @CWi1 ,

 

Adobe Analytics segments are not processed in real-time; there is typically a delay of up to 8 hours. This delay occurs because Analytics segments are historical and require processing time before they can be utilized in Target activities.

To achieve real-time personalization in Adobe Target, you can use Adobe's Real-Time Customer Data Platform (RTCDP). By creating segments in RTCDP and integrating them with Adobe Target, you can deliver personalized experiences without the delay associated with Analytics segments. This integration allows for both same-page and next-page personalization with governance and privacy support.

Implementing the Adobe Experience Platform Web SDK can further enhance this integration, enabling real-time data collection and activation across Adobe Experience Cloud applications, including Adobe Target.

Avatar

Community Advisor

@CWi1  suggest to use RTCDP segments not Analytics segment, also segment moves to target via RTCDP qualifies when use visit your page -> this is further needs a revisit to existing WebSDK implementation on your end.