Facebook Destination mapping multiple email source fields to target fields?

[C82028302]

Hello, 

I recently activated several segments to a Facebook Destination account, and I am seeing a large number of identity failures.

I do have several non-identity email & phone number source fields mapped to their respective target fields for the destination. Would this be causing an issue? All of my source data is in the proper format for activations, I do know there is a composite key within our Email identity map, so I expect some errors from this. Additionally, will RTCDP activate all emails for a profile within the Identity Maps? 

 

TLDR summary of questions:

• Can I map multiple source fields to the email & phone target fields?
• Will all values for a profile within the "IdentityMap: Phone_E.164" & "IdentityMap: Email_LC_SHA256" namespaces distribute to the Facebook destination? 
• Is there a way to get more details to why identities failed, other than the brief description?

Thank you for the help and guidance.

[kautuk_sahni]

@DavidRoss91 @akshaykapil23@pradnya_balvir@Kumar_Saurabh_@Travis_Jordan@vishnuunnikrishnan

Kindly take a moment to review this question and share your valuable insights. Your expertise would be greatly appreciated!

[GigiCotruta · Accepted solution]

Hello, @C82028302,

• Can I map multiple source fields to the email & phone target fields?
  • No. It might collide, In your case, if a profile has an "Email_Hashed" and a "PersonalEmail_Hashed", the connector will try to write 2 values in 1 field. Make sure that all your PII information is sha256 hashed as it one of Facebook's requirements.
• Will all values for a profile within the "IdentityMap: Phone_E.164" & "IdentityMap: Email_LC_SHA256" namespaces distribute to the Facebook destination? 
  • It depends, in theory, yes, it is supposed to share all the "phone_sha256" and "email_lc_sha256" that a profile might have, now, try to find the API calls in order to make sure. Ask your Adobe Manager to ask the team in charge of this connection. Our team right now is doing the same thing with Google Destinations. 
• Is there a way to get more details to why identities failed, other than the brief description?
  • Sadly, the UI is very limited with all these external connectors. I think that the best aproach is to elevate this problem with Adobe Engineering team in case the answer to the 1st question didn't solve anything.