Hi Experience League Community,
I came across the "Authenticated state" parameter when creating an Identity map data element. Could you please explain how this is used in the RTCDP context and whether it has any implications or effects on data tracking and profile merging?
I tried researching online, but most articles imply that this parameter is mainly used for Audience Manager or Target. I would be grateful if you could provide some pointers on this.
Many thanks,
Zac
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hello @ZacharyTa1
The merging of identity values will be performed upon the value present in the field which has been marked as identity value.
{
"identityMap":{
"ECID":[
{
"id":"83238819066235616291057085344313877718",
"authenticatedState":"ambiguous",
"primary":true
}
]
}
}
Using the sample above only the value for ECID will be merged together with other sources.
Hi @ZacharyTa1,
I share with you what I know until the moment.
The Authenticated State inside RTDCP can indicate whether a user is authenticated (logged in) or unauthenticated (anonymous). It can be one of the following scenarios:
-Authenticated: User is logged in, and have a known identifier (ex: email, userID)
-Logged Out: User has logged out previously but was previously authenticated during the session.
-Anonymous: User has never logged in or hasn't provided any identifiable information.
In terms of Implication for data tracking and profile merging I can share the following conclusions:
- Enhances data accuracy cause you can distinguish when a user is recognized and when they are not reducing the chances of creating duplicate profiles or misattributing behaviours.
-As recognizing whether a user is authenticated, the tool can better unify profiles, ensuring that all interactions, promote an holistic view of the customer.
-Regarding personalization it will be more effective to personalize experiences. If the user is authenticated will trigger more personalized content or offers compared to when they are anonymous.
Hope this helps, and happy to learn more about it cause the info is quite limited!
Regards,
Celia
@jpetermarias
Hi Celia,
Thank you for your response.
I would like to understand more in terms of the impact on profile merging.
While it can be imagined that having an additional parameter will benefit with data accuracy, however, do you know if the "Authenticated state" would affect the data being tracked? i.e. in the case that a user is identified as "Logged Out", would the web data such as pageview/ link clicks still be tracked and unified under the same profile view? or does having the "Authenticated" status helps the system to prioritise identities gathered in the "Authenticated" state over the "Anonymous" state? (i.e. having the email captured in the "Authenticated" state as the prime identity for segmentation and activation.)
Thank you very much!
Zac
Hello @ZacharyTa1
The merging of identity values will be performed upon the value present in the field which has been marked as identity value.
{
"identityMap":{
"ECID":[
{
"id":"83238819066235616291057085344313877718",
"authenticatedState":"ambiguous",
"primary":true
}
]
}
}
Using the sample above only the value for ECID will be merged together with other sources.
@ZacharyTa1 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Likes
Replies
Views
Likes
Replies