Expand my Community achievements bar.

SOLVED

Debugging AEP (Adobe Experience Manager) Audience

Avatar

Level 4

Hello,

I'm looking for support/guidance on how to potentially debug an AEP audience? I'm running an Adobe Target test and I'm utilizing an audience coming from AEP. I'm having difficulty receiving the proper experience when using this AEP audience, it seems to work correctly with a different segment, not the AEP one. Is there any way to see whether a user is qualifying for this AEP audience on the front end? Would this information appear within the Adobe Experience Platform Debugger extension?

I would love any additional information.

Thanks!

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

You would have to go to AEP profiles and search for your profile based on the namespace. For example, if the user is logged to the website and the email Id is getting ingested in the profile attributes, then in that case you can search based on the email ID namespace. In case, it's an anonymous user details might be profiled based on ECID (marketing visitor cloud ID) as it's namespace. Once you are able to find your profile ID, navigate to the segment membership tab and it's will show whether this profile is qualified for any particular segment or not.

 

Kindly go through with the following link that would provide you insights about what I have mentioned above. 

 

https://experienceleague.adobe.com/docs/experience-platform/profile/ui/user-guide.html?lang=en#profi... 

View solution in original post

8 Replies

Avatar

Community Advisor

Hi @ben_mrm 

 

I don't think the AEP segmentation details are available on the cloud debugger extension. You would have to go to AEP and check whether your profile is qualified for that segment or not which you are exporting as an audience in Adobe Target.

 

Hope this help.

Avatar

Level 4

Understood. Thank you @Avinash_Gupta_ 

So the process of checking within AEP then is what, looking to see if the segment is capturing a users specific marketing cloud visitor ID or something?

Avatar

Correct answer by
Community Advisor

You would have to go to AEP profiles and search for your profile based on the namespace. For example, if the user is logged to the website and the email Id is getting ingested in the profile attributes, then in that case you can search based on the email ID namespace. In case, it's an anonymous user details might be profiled based on ECID (marketing visitor cloud ID) as it's namespace. Once you are able to find your profile ID, navigate to the segment membership tab and it's will show whether this profile is qualified for any particular segment or not.

 

Kindly go through with the following link that would provide you insights about what I have mentioned above. 

 

https://experienceleague.adobe.com/docs/experience-platform/profile/ui/user-guide.html?lang=en#profi... 

Avatar

Level 1

Hi,

Were you able to resolve this?

I'm able to identify my profile is part of an audience that is linked to Target as a destination. But it doesn't trigger the experience.

 

Kind regards

Leonie

Avatar

Level 4

Hi @leonieswart-iDA , 

Were you able to get to the bottom of your issue? I am facing a similar issue where I am able to qualify for the segment in AEP but I don't seem to qualify for the same shared audience in Target. 

Regards,

Chaitanya

Avatar

Community Advisor

Hi @kchaitanya @ben_mrm @leonieswart-iDA  I'm also facing the similar issue.
I can see my CRMID is present in the AEP segment but when I use the segment in Target and access the activity url as loggedIn user , I do not qualify for the segment and so I do not get the experience.

 

Is there any specific configuration we need to get this work ?

Thank you.

Avatar

Level 4

@ambikaTewari_ATCI ,

In my case after raising a clientcare ticket we discovered that the Datastream id used in webSDK configuration was different from the one used in Target Destination configuration to which the segment was shared. Creating a new Target Destination with the same Datastream id and remapping the segment to this new Target Destination in AEP helped me resolve the issue. 

Regards,

Krishna Chaitanya