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 A
email being an email that has access
to all clients' Ads accounts
- Redid flow for getting access token, same result. "Invalid customer ID
"
On Saturday, June 25, 2022 at 9:58:54 PM UTC-5 Alley wrote:
> Using service account, nodejs, not using a client. This setup
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
