Hi Alley,
Thank you for updating us that this issue has been resolve.
With regard to, "The Ads API requires it to be only numeric, so the dashes need
to be stripped out.", this is indeed correct. When specifying your customer ID
in your request, you should note that you need to remove the hyphe
This is solved. For others that get here, it was simple: The other APIs
like Analytics take customer ID as they present it on the site,
"xxx-xxx-." The Ads API requires it to be only numeric, so the dashes
need to be stripped out.
On Sunday, June 26, 2022 at 5:07:07 PM UTC-5 Alley wrote:
>
More debug:
- Carefully read docs, realized service accounts can only communicate
with the Ads API via impersonating a user
- Added domain-wide delegation in Workspace for the service account,
scoped to https://www.googleapis.com/auth/adwords
- The JWT now included sub with the em
Using service account, nodejs, not using a client. This setup works great
for Analytics, failing to get anything back from Ads.
- Auth performs fine, get JWT and sending Developer-token header w/ the
access token as Bearer
- Every request to googleAds:searchStream results in INVALID_ARG
