Target not showing experience for Segment AAM says I belong to | Community
Skip to main content
Level 2
September 9, 2019

Target not showing experience for Segment AAM says I belong to

  • September 9, 2019
  • 1 reply
  • 12251 views

I've created a bunch of "onboarded traits" that make up a segment rule (lets call it Seg123), and I've uploaded a data file that contains my declared ID and the traits that would put me in the segment Seg123.

When I check my Profile in AAM Visitor Profile Viewer (searching for my UUID) it shows that I qualify for Seg123, however when I visit the URL, I DONT see the experience for that segment, I fall into the "All visitors" experience (which is ranked 2nd in the list)

People Core Services shows Seg123 current size as "Collecting Data" - could it not be done syncing?

Thoughts? could it just be a timing issue? What else could I be missing?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Andrey_Osadchuk
Level 10
September 9, 2019

Hi Steve,

  • is the AAM segment the only criteria applied for targeting?
  • are you working with an XT or other type of activities?
  • is it the only activity targeted to this page or mbox (check the Collisions tab in AT )?
  • is Experience Cloud ID implemented on the targeted page(s)?
Level 2
September 9, 2019
  • is the AAM segment the only criteria applied for targeting? - Yes, and according to AAM visitor profile viewer, i belong to the segment
  • are you working with an XT or other type of activities? - XT
  • is it the only activity targeted to this page or mbox (check the Collisions tab in AT )?  - Yes it should be, I will double check
  • is Experience Cloud ID implemented on the targeted page(s)?  - Yes, "Experience B" is a "all visitors" catch-all type segment, which is working (and I am seeing that experience). However this

The "all visitors" audience is ranked #2, even if I remove it, i still wont get my intended experience.

Level 2
September 9, 2019

Also check that the declared ID (customer ID) passed to the Experience Cloud ID Service has the "authenticated" flag


Thanks for your suggestion, whats the best way to check for that authenticated flag?