As per my understanding, we need to have the trait key name and value in
place in AAM even though if we use regex to consider “ALL” (i.e.: .*) .
Highlighted below. Assume that, we have sent only 3 different dealcode
trait key value to AAM but wanted to exclude those 3 key value but need
to include rest of the new upcoming key value. Scenario:We would like to
consider all users falls under dealcode by using regex .* and at the
same time exclude the users with the specific value(“yaa|abc|tst”)
@snielson Instead of relying on AAM UI, i'm using API url to check the
trait qualification to confirm.
Hi, As per my understanding, we can use event call to make any user
qualify for the onboarded trait.
https://clientname.demdex.net/event?d_sid=traitID I tried this in
Microsoft Edge but it doesnt seem to be working. Any idea. Thanks
thanks @snelson. this helps. As a follow question, if user viewed 5
times and incase for testing purpose, if we need to make them qualify
again for that same segment just for that browser using
http://companyname.demdex.net/event?d_sid=traitID , will it work or do
we need to create new segment with frequency setup change to make the
user qualify. to see it.
@jusaha - you can use multiple customer ID(one for AAM & another one for
Customer Attribute) in a website.
Hi, QA preview urls works fine for client side mboxes. But, not working
for Server side mboxes. Is there any additional details that we need to
pass as part of REST API call to utilize QA Preview urls.