Hi Joshua,
My apologies if there has been some issues with the example. I'll make sure
to file a request to have this updated, both in the client library and in
the documentation.
As for the workaround, yes, that is correct, you will need to include all
the criteria in an array for the
I believe we found the issue. Looks like the boilerplate example does not
properly set the criteria. You can only make one setCriteria call. When we
changed the criteria setting to one single call, the location information
was included in the request.
Hi Joshua,
Have you tried the exact same filters using the Keyword Planner of the
AdWords UI? Could you confirm if there are discrepancies between the
results you get from the AdWords API and the AdWords UI? If the results
returned are the same or similar then it would indicate that the
Hi, it seems like the location isn't being accounted for when estimating
traffic.
I've been testing this code,
https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201708/Optimization/EstimateKeywordTraffic.php,
exactly (apart from changing the location id and
