I would like to know what happens with the Facebook Audiences connector when you check the: Check if user identifier is already hashed. option.
Which attributes are affected by this option? Will the following attributes will be affected?:
Thanks and kind regards
Solved! Go to Solution.
When using the Facebook Audiences connector in Tealium, checking the "Check if user identifier is already hashed" option will specifically affect the processing of user identifiers (i.e., email addresses, phone numbers) that you are sending to Facebook.
When this option is enabled, Tealium assumes that the user identifiers you are providing are already hashed and will not attempt to hash them again before sending the data to Facebook. If your user identifiers are not hashed, you should leave this option unchecked, and Tealium will hash the user identifiers for you.
Regarding the attributes you mentioned:
Mobile Advertiser Id: This attribute is not affected by the "Check if user identifier is already hashed" option. Mobile Advertiser Ids are not considered as user identifiers that need to be hashed.
Country: This attribute is also not affected by the option. Country information is considered as non-personally identifiable information (non-PII) and doesn't require hashing.
In summary, the "Check if user identifier is already hashed" option primarily affects user identifiers like email addresses and phone numbers, while other attributes like Mobile Advertiser Id and Country remain unaffected.
If you have any further questions or need assistance, feel free to ask.
Yes, that's correct. Sending the country attribute hashed won't have any effect inside Facebook, as Facebook expects this field to follow a specific format (usually a two-letter country code, e.g., 'US' for the United States). Since the country information is non-personally identifiable information (non-PII), there's no need to hash it. Sending the hashed value of the country would likely result in Facebook not being able to recognize or process that information correctly.
It's always best to follow the expected format for each attribute, as specified by the platform you're sending the data to, in this case, Facebook.