E.164 Format for Enhanced Leads

164 views
Skip to first unread message

Michael DeWulf

unread,
Jul 15, 2024, 4:31:43 PM7/15/24
to Google Ads API and AdWords API Forum
Hello,

We're working on sending enhanced leads via the API. We're using NodeJS, so we're using the rest API - not an existing library.

We wanted to validate that we are formatting our phone numbers correctly.

Specially, the library we've been using to parse a phone number and return it as E.164 returns zero spaces.  I.e. the format for a US phone number is: "+15555551234".

The "no spaces rule" does not seem to be required by Google, however.  If you look at the python example of normalizing and hashing a phone number, you'll see the number has spaces: "+1 800 5550102".

This obviously hashes to a different value:

"+1 800 5550102" => "5b0ab2d6e32d4073681bf36498ad2d32f7a1289629710fe0052f300af19646dc"

"+1800550102" => "c5383c2eeada28210d27f011bc127d4f9562cf38ff0c9bba33dd45ae79b9fe7c"

What is the correct way to normalize a phone number for enhanced leads?

Thank you,
Mike

Google Ads API Forum Advisor

unread,
Jul 15, 2024, 9:39:24 PM7/15/24
to mtde...@goarrowsup.com, adwor...@googlegroups.com
Hi,

Thank you for reaching out to the Google Ads API support team.

I understand your concern but your concern is outside of our team scope. Please note that our team can only assist with the technical queries/concerns related to the Google Ads API. I would recommend that you reach out to the Google Ads Product support team as they are better equipped to assist you with your issue.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02vDcrt:ref" (ADR-00251049)

Thanks,

 
Google Logo Google Ads API Team

Register for the upcoming workshop: Performance Max and the Google Ads API!
 


asif...@instaview365.com

unread,
Jul 15, 2024, 9:57:42 PM7/15/24
to adwor...@googlegroups.com

Dear 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum,


We would like to acknowledge that we have received your request and a ticket has been created.

A support representative will be reviewing your request and will send you a personal response (usually within 24 hours).



Thank you for your patience.


Sincerely,

asif...@instaview365.com

Michael DeWulf

unread,
Jul 15, 2024, 10:54:21 PM7/15/24
to Google Ads API and AdWords API Forum
I appreciate that this may question may straddle the border between the API team and the Product team.  However, can you please verify the documentation for the API examples are correct?  The Python example I linked in my initial post states:

        # Phone number to be converted to E.164 format, with a leading '+' as
        # required.
        "phone": "+1 800 5550102",


On the other hand, the E.164 standard indicates there should not be spaces in the formatted number, which is why we're confused.

Unfortunately, the example code is the only reference we've found to verify our implementation, and it appears incorrect.

Asif Khan

unread,
Jul 16, 2024, 4:40:59 AM7/16/24
to Google Ads API and AdWords API Forum
try to use Postmen for the api

Google Ads API Forum Advisor

unread,
Jul 16, 2024, 8:45:45 AM7/16/24
to mtde...@goarrowsup.com, adwor...@googlegroups.com
Hi,

I would like to inform you that the E.164 format explicitly states that there should be no spaces in the phone number. The correct format for the provided phone number would be: "+18005550102".

If you still need any further assistance, kindly reach out to the Google Ads Product support team as they are better equipped to assist you with your issue.

asif...@instaview365.com

unread,
Jul 16, 2024, 9:08:08 AM7/16/24
to adwor...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages