E.164 Format for Enhanced Leads

[Amc oudomthin]

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,

Amc

[Google Ads API Forum Advisor]

Hi,

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

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.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vEAkr:ref" (ADR-00259745)

Thanks,
 

Google Ads API Team

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