E.164 Format for Enhanced Leads

2024-07-15 Thread Michael DeWulf
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.16

Re: e.164 format for enhanced leads

2024-07-15 Thread Michael DeWulf
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 form

Enhanced Conversions for Leads: 100% CLICK_NOT_FOUND

2024-09-11 Thread Michael DeWulf
Hi, We've been using the Google Ads API for a while now. Our non-enhanced conversions (GCLID, GBRAID, WBRAID) are working fine. However, we've yet to see an enhanced conversion match. All of them are returning CLICK_NOT_FOUND. We suspect that some of these are incorrect, because we can see