Real-Time Personalization Not Working Despite Segment Qualification in AEP | Community
Skip to main content
pradeep_07
Level 4
July 9, 2025
Question

Real-Time Personalization Not Working Despite Segment Qualification in AEP

  • July 9, 2025
  • 2 replies
  • 464 views

Hi Community,

We’re implementing real-time personalization using Adobe Experience Platform (AEP) and Adobe Target (POC). Our goal is to personalize content based on an Employee ID passed in the URL.

Here’s what we’ve done so far:

  1. Captured Employee ID using Web SDK (migrated from at.js).
  2. Configured Datastream with Edge segmentation and Destination personalization enabled.
  3. Configured Datastream to Adobe Target.
  4. Created and activated an audience in AEP using a merge policy that prioritizes real-time data.
  5. Mapped the audience to an experience in Adobe Target.

We can see the Employee ID being captured and stitched with ECID. The user qualifies for the segment under audience membership, but the personalized experience does not show up on the landing page or subsequent pages.

Has anyone faced a similar issue? Are there any known delays or best practices for ensuring real-time personalization works as expected?

Thanks in advance!

2 replies

Level 3
July 10, 2025

You may need to check/consider the below.

 

- Hope, you have created the AEP audience using Edge evaluation method

- Based on my experience, once we created the Edge segment we need to wait for 15 mins upto 1 hr before we use for activation.

- If user is eligible for audience membership then check if anything wrong in the target setup/rendering/displaying the content in the UI. 

pradeep_07
Level 4
July 10, 2025

Yes , I have enabled the Active on Edge under Merge policy. Still don't see expected result.

KumarRishii
July 10, 2025

Yes, this is a common challenge when implementing real-time personalization using AEP + Adobe Target via Web SDK. I will suggest you to Fix Flow by below steps

Ensure Web SDK setIdentity() is called before sendEvent() for Target.

Add a short delay (e.g., setTimeout) or wait until onDeviceDecisioningReady.


Test with multi-step flow: capture Employee ID → reload page → evaluate experience.

Use Target QA links and Platform Debugger to validate activation and decision responses.

pradeep_07
Level 4
July 11, 2025

Tried but no luck yet.