Personalization issue through AEP Edge Segmentation

[kchaitanya]

Hi experts, 

We are trying to deploy personalization through Adobe Target leveraging the Edge segmentation capability of AEP and ran into issues. While the segment is getting qualified in AEP, Target is not able to qualify for the segment and hence not delivering the experience. I have followed all steps mentioned in the document: https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-ta... and can't figure out why the qualification is not happening in Target?

Below is the screenshot of the Target activity with the segment id: "platformSegment":"509b9e02-4f9b-457a-abe8-fe5316af2632"

When I check for the profile id through Postman (for my ECID), I am seen qualifying to the same segment in AEP: 

Has anyone faced similar issue of the segment not qualifying in Target though the ECID qualifies for the segment in AEP? And how did you solve the issue?

Thanks & regards,

K Chaitanya

[DisaRas · Accepted solution]

Hi @kchaitanya,

I have implemented this integration (AEP>Target) and it's working for me. Do note the given prerequisites have been met - 

a. Target enable in Datastream

b. AEP enable in Datastream (also enable edge segmentation and personalization decision option)

c. Default merge policy to be active on edge

d. Create Target Destination in AEP and activate segments to this destination

Refer below Adobe documentation for above -

https://experienceleague.adobe.com/docs/experience-platform/destinations/catalog/personalization/ado...

https://experienceleague.adobe.com/docs/experience-platform/destinations/ui/activate/configure-perso...

Hope this helps.

[kchaitanya]

Thank you @DisaRas for your response. Had followed the steps you mentioned. Had to raise a clientcare ticket and there seems to be some caching issue on the site I was trying to render the personalization. Now it is working for me as well. 

[kchaitanya]

Landed into this problem again recently and sharing the resolution (thanks to clientcare) here if anyone else faces similar issue: 

Problem was with a different datastream being used to send webSDK calls to Target and a different datastream used in Target Destination configuration in AEP. Over a period of time when multiple properties are created for implementation it is important to ensure the right Target destination is used for the right property for segment sharing.