You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means that when we push data around the datalayer, event parameters etc. we need to have a custom variable that formats the number for the Conversion API alone adding in unnecessary steps.
The text was updated successfully, but these errors were encountered:
It would be handy to have the tag code strip out the + symbl from E.164 provided phone numbers before hashing.
My rationale is as follows.
The Conversions API wants us to provide phone numbers hashed from a digits-only version e.g.
Example:
Input: US phone number (650)555-1212
Normalized format: 16505551212
but the common event data model expects E.164 format with the + symbol included.
This means that when we push data around the datalayer, event parameters etc. we need to have a custom variable that formats the number for the Conversion API alone adding in unnecessary steps.
The text was updated successfully, but these errors were encountered: