Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards

[Issue] AA Segments shared to Experience Cloud not syncing to Target after 72h (Retroactive Audience Use Case)

Avatar

Level 1

Hi everyone,

I am facing a persistent issue trying to use Adobe Analytics segments as audiences within Adobe Target.

My specific goal is to target users based on historical/retroactive behavior (e.g., users who visited a specific page in the last 60 days). Therefore, using real-time Profile Scripts (which I have already tested and work fine) is not a solution for this specific requirement.

Steps I have taken to troubleshoot:

  1. Segment Creation: To rule out logic errors, I created a very simple segment in AA: Page equals [URL]. I have tested creating this with all three scopes: Hit, Visit, and Visitor.

  2. Publishing: I confirmed that "Publish this segment to the Experience Cloud" is checked.

  3. Data Verification in AA: I pulled a report in Analytics and confirmed that my test user's ECID is present in the segment.

  4. Target Activity: I created an activity in Target using this shared audience.

  5. Wait Time: I waited 72 hours to allow for full backend processing and audience propagation.

  6. Testing: I revisited the site using the same browser and cookies (ensuring the ECID remained the same as the one captured in AA).

The Issue: Despite the ECID existing in the AA segment and waiting 72 hours, the user does not qualify for the activity in Target.

Has anyone experienced a complete sync failure like this with legacy Core Services integration? Given that the data exists in AA but isn't triggering the Target audience after 3 days, could this be an account provisioning issue or a specific delay in the "Shared Audiences" backend?

Any guidance on debugging this retroactive audience flow would be appreciated.

Thanks!

0 Replies