Dear all,
I have been trying out real-time audiences. I understand that a real-time audience can be created from Analytics eVars, events and props (recently added). This is what I did:
1) In the web properties, I populated a customer eVar to hold authenticationStatus. The value is either 'logged in' or 'logged out'. I set this eVar in DTM as part of page loading rule. I also populated a customer prop to the same value as the eVar. I validated in Experience Cloud debugger that both variables have the right value set on each page load.
2) I then created two real-time audiences in Audience Library: RTA: visitors who have logged in before (eVar1 equals 'logged in') and RTA: visitors who are currently logged in (prop1 equals 'logged in').
3) I then created a Target Experience activity and tried with both of the above segments.
This is what I observed:
1) With real-time audience RTA: visitors who have logged in before (eVar1 equals 'logged in'), I saw the targeted experience after login. However, the targeted experience stays even after I log out. Once logout, I did set the eVar1 to 'logged out'. However, the targeted experience stays there until I clear the cookie. If the real-time audience is evaluated at hit level, shouldn't I see the default experience after logout?
2) I got the same result after changing to real-time audience RTA: visitors who are currently logged in (prop1 equals 'logged in'). If I am right, prop value is held only for a hit. Somehow the new prop value, 'logged out', isn't evaluated correctly in the audience.
Did I miss something or was my audience library not provisioned correctly?
Many thanks!
Paul Rao