Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: phone number parsing from E.164 #30

Open
skaaptjop opened this issue Mar 17, 2022 · 0 comments
Open

Feature Request: phone number parsing from E.164 #30

skaaptjop opened this issue Mar 17, 2022 · 0 comments

Comments

@skaaptjop
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant