Thanks to you also for the swift diligent responses!
--
Jonathan Clarke
On 12 October 2017 at 5:19:27 PM, 'Nadine Sundquist (AdWords API Team)' via
AdWords API Forum (adwords-api@googlegroups.com) wrote:
Hello Jonathan,
Thank you for being so understanding and for phrasing your qu
e more use case tends to help in trying to find an overall solution to
> mind-bending issues like this one.
>
> Take care,
> Nadine, AdWords API Team
>
> On Thursday, October 12, 2017 at 1:36:24 PM UTC-4, Jonathan Clarke wrote:
>>
>> OK, you've confirmed your API
m trying
> to direct you to other avenues that most likely would have the answer.
>
> Best,
> Nadine, AdWords API Team
>
> On Thursday, October 12, 2017 at 8:42:34 AM UTC-4, Jonathan Clarke wrote:
>>
>> Hi Nadine,
>>
>> Thanks for looking into this. I do feel
Regards,
Jonathan Clarke
On Wednesday, October 11, 2017 at 5:21:35 PM UTC-4, Nadine Sundquist
(AdWords API Team) wrote:
>
> Hello Jonathan,
>
> I have a feeling that part of the differences are appearing because of
> this:
>
>- The content site where your ad was clicked
api/docs/guides/reporting#criteria_prefixes>.
>
> Please try taking a look at those to see if they match what you're seeing.
> If you need further help, feel free to reach out.
>
> Cheers,
> Nadine, AdWords API Team
>
> On Monday, October 9, 2017 at 5:59:07 PM
We've been working successfully with the AdWords API (Google Ads Python
Client Library: https://github.com/googleads/googleads-python-lib) for a
good while building internal reports for our application. Until, that is,
we hit placements…
I define placements as anywhere an AdWords ad is shown. T
