Re: Ad Performance Report missed data when CriterionId is included

2020-09-29 Thread Google Ads API Forum Advisor Prod
Hi Dmitry, >From what I could find out, we cannot expose criterionId for Discovery >campaigns in AdWords API without adding full support for this campaign type in >AdWords API. However, we recently announced general availability for Google >Ads API , which is the next version of AdWords API.

Re: Ad Performance Report missed data when CriterionId is included

2020-09-28 Thread don....@gmail.com
Helllo Anthonly, I have similar issue, if CriterionId is included into query we do not get full cost for certain campaigns Example 1. Call without CriterionId curl --location --request POST

Re: Ad Performance Report missed data when CriterionId is included

2020-09-08 Thread Google Ads API Forum Advisor Prod
Hi Dmitry, We will need your CID and report results that Mitchell mentioned to further look into this. Please do so using reply privately to author. Thanks, Anthony Google Ads API Team Anthony Google Ads API Team ref:_00D1U1174p._5004Q20VVw3:ref -- --

Re: Ad Performance Report missed data when CriterionId is included

2020-09-07 Thread 'Dmitry Kozyrev' via AdWords API and Google Ads API Forum
Hi Mitchell, Sorry for the late reply. Unfortunately I did not receive the permission to share that data. But recently we ran into a similar issue (for another customer): curl --http1.1 \ --header "Authorization : Bearer {AuthorizationToken}" \ --header "developerToken :

RE: Ad Performance Report missed data when CriterionId is included

2020-06-02 Thread Google Ads API Forum Advisor Prod
Hi Dmitry, Thank you for reaching out. Can you please share your client customer ID, both downloaded reports, and a screenshot of the data in the UI via Reply privately to author so I can further investigate the issue? Regards, Mitchell Google Ads API Team ref:_00D1U1174p._5004Q20VVw3:ref --

Ad Performance Report missed data when CriterionId is included

2020-06-02 Thread 'Dmitry Kozyrev' via AdWords API and Google Ads API Forum
Hi, Our customer uses automated report fetching similar to following: curl --http1.1 \ --header "Authorization : Bearer {AuthorizationToken}" \ --header "developerToken : {DeveloperToken}" \ --header "includeZeroImpressions: false" \ --header "clientCustomerId : {CustomerId}" \