ConversionsAPI-Tag-for-GoogleTagManager icon indicating copy to clipboard operation
ConversionsAPI-Tag-for-GoogleTagManager copied to clipboard

Feature Request: phone number parsing from E.164

Open skaaptjop opened this issue 3 years ago • 0 comments

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.

skaaptjop avatar Mar 17 '22 10:03 skaaptjop