Thank you, Peter.
For the issue with refresh_token: we have taken a note and write to support
Google API Console.
For the issue with delay in the reports: unfortunately, we can't provide
screenshots for the 18th June from the UI, because now there are already
updated data in the interface, and
Hi, excuse my broken English.
We are started use Google Ads API (new version) and faced several problems:
1) We request reports using AQWL. Request:
SELECT segments.date, campaign.name, campaign.advertising_channel_type,
campaign.id, metrics.impressions, metrics.clicks, metrics.ctr,
>> In that blog post, we say, "Any developers applying for a new developer
token after today will only be given access to the Google Ads API. "
Sorry I didn't answer right away. Thank you very much, we started working
with the new documentation and now everything is fine. The two Google Ads
API
Hello, tried again - the error persists.
We need this API, so we really look forward to your comments and
recommendations.
The developer token was created very recently (a few days ago) and did not
touch the updates (April 22), which are mentioned in neighboring similar
topics.
понедельник,
Hi, and please accept our apologies in advance for the broken English.
Our developer token has been approved (basic access), but when I try to use
the allowed methods (creating report's), the Google Ads server returns an
error:
***error***
QuotaCheckError.INVALID_TOKEN_HEADER
New developers
