Issue with Adobe Analytics Audiences not qualifying in Adobe Target(A4T) | Community
Skip to main content
G
GV16
Level 2
April 10, 2026
Question

Issue with Adobe Analytics Audiences not qualifying in Adobe Target(A4T)

  • April 10, 2026
  • 1 reply
  • 23 views

I have a list of 3,784 users that I want to target with specific data. To achieve this, I created segments in Adobe Analytics, where I defined the condition as User ID equals any of x, y, z, using approximately 500 user IDs per segment.

 

These segments are visible in Adobe Target via A4T, and I have used them to create an experience. However, I am unable to see the experience being delivered to the intended audience.

 

Could you help identify what might be causing this issue?

1 reply

P
PrasanthV
Level 3
April 13, 2026

Hi ​@GV16 ,

 

This is a common issue when using Analytics-to-Target (A4T) for audience delivery. The primary reason you aren't seeing the experience is likely the latency and identity "handshake" between the two platforms.

Here is why your implementation is failing:

1. The "A4T Latency" Gap

When you create a segment in Adobe Analytics and share it with Target, it is not real-time.

  • The Delay: It typically takes 24–48 hours for the segment to process in Analytics and "sync" to the Experience Cloud Audience service.

  • The Lookback: Analytics segments are often processed based on historical data. If a user qualifies for the segment in Analytics today, Target might not know they belong to that segment until the next day.

2. Identity Mismatch (ECID vs. User ID)

Adobe Target delivers experiences based on the Experience Cloud ID (ECID).

  • If your Analytics segment is based on a custom User ID (like a login ID), Target has no way of knowing which ECID (the browser cookie) belongs to that User ID until the user actually visits the site and "stitches" those IDs together in a single session.

  • If the user is on a new device or cleared cookies, the link is broken.

3. Segment Volume & Processing

Using "User ID equals x, y, z" with 500+ values is extremely heavy for an Analytics segment. If the segment is still "calculating" in Analytics, it will show as 0 or "unavailable" in Target.

Terms & ConditionsAccessibility statement

Loading footer...