Thank you all. The dashes in the ID was indeed the issue. I am able to push
the mutations successfully now.
On Tuesday, April 23, 2024 at 10:44:47 AM UTC-4 Google Ads API Forum
Advisor wrote:
> Hi,
>
> Thank you for your input on the issue.
>
> This message is in relation to case
>
Hi,
Thank you for your input on the issue.
This message is in relation to case "ref:!00D1U01174p.!5004Q02tPHgL:ref"
(ADR-00232263)
Thanks,
Google Ads API Team
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
"The login customer id header \\\'Optional[XXX-XXX-]\\\' could not be
validated."
If you're passing in the customer ID value with hyphens like "111-222-"
you need to pass without for the API: "111222".
D.H.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find
Il lun 22 apr 2024, 13:09 'Google Ads API Forum Advisor' via Google Ads API
and AdWords API Forum ha scritto:
> Hi,
>
> Thank you for reaching out to the Google Ads API support team.
>
> I understand that you have encountered the error "INVALID_CUSTOMER_ID
>
Hi,
Thank you for reaching out to the Google Ads API support team.
I understand that you have encountered the error "INVALID_CUSTOMER_ID." It
means that the provided
customer ID is invalid. In order to replicate the issue from our end, provide
us with the complete API logs (request and