Location Criteria seems to be useless in TrafficEstimatorService?

[Joshua Kozlowski]

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 echo'ing it out and using my own ini file).

  | location id: 2840 (USA)
-- | --
  |  
  | Results for the platform with ID 30000 and name 'Desktop':
  | Estimated average CPC: 805686.00
  | Estimated ad position: 4.47
  | Estimated daily clicks: 151.93
  | Estimated daily cost: 121466368.00
  |  
  | Results for the platform with ID 30001 and name 'Mobile':
  | Estimated average CPC: 687972.00
  | Estimated ad position: 3.29
  | Estimated daily clicks: 607.32
  | Estimated daily cost: 414612608.00
  |  
  | Results for the platform with ID 30002 and name 'Tablet':
  | Estimated average CPC: 805338.00
  | Estimated ad position: 3.84
  | Estimated daily clicks: 116.32
  | Estimated daily cost: 92955896.00
  |  
  | Results for the keyword with text 'mars cruise' and match type 'BROAD':
  | Estimated average CPC: 315898.00
  | Estimated ad position: 1.06
  | Estimated daily clicks: 0.02
  | Estimated daily cost: 5694.00
  |  
  | Results for the keyword with text 'cheap cruise' and match type 'PHRASE':
  | Estimated average CPC: 736021.00
  | Estimated ad position: 4.27
  | Estimated daily clicks: 158.41
  | Estimated daily cost: 115699104.00
  |  
  | Results for the keyword with text 'cruise' and match type 'EXACT':
  | Estimated average CPC: 721342.00
  | Estimated ad position: 3.62
  | Estimated daily clicks: 717.14
  | Estimated daily cost: 513330080.00

location id: 1014485 (Denver)
--
  |  
  | Results for the platform with ID 30000 and name 'Desktop':
  | Estimated average CPC: 805896.00
  | Estimated ad position: 4.46
  | Estimated daily clicks: 153.78
  | Estimated daily cost: 122980812.00
  |  
  | Results for the platform with ID 30001 and name 'Mobile':
  | Estimated average CPC: 689388.00
  | Estimated ad position: 3.27
  | Estimated daily clicks: 610.89
  | Estimated daily cost: 417908704.00
  |  
  | Results for the platform with ID 30002 and name 'Tablet':
  | Estimated average CPC: 806074.00
  | Estimated ad position: 3.82
  | Estimated daily clicks: 117.41
  | Estimated daily cost: 93914592.00
  |  
  | Results for the keyword with text 'mars cruise' and match type 'BROAD':
  | Estimated average CPC: 315900.00
  | Estimated ad position: 1.06
  | Estimated daily clicks: 0.02
  | Estimated daily cost: 5739.00
  |  
  | Results for the keyword with text 'cheap cruise' and match type 'PHRASE':
  | Estimated average CPC: 738061.00
  | Estimated ad position: 4.25
  | Estimated daily clicks: 160.06
  | Estimated daily cost: 117224744.00
  |  
  | Results for the keyword with text 'cruise' and match type 'EXACT':
  | Estimated average CPC: 722398.00
  | Estimated ad position: 3.61
  | Estimated daily clicks: 722.01
  | Estimated daily cost: 517573632.00

Notice, for example, that the "Estimated daily clicks" for "EXACT" "cruise" is 717.14 for the USA and 722.01 for Denver. Shouldn't the numbers vary more than that?

Any ideas?

[Peter Oliquino]

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 estimates are indeed being returned correctly.

However, in the event that you see any discrepancies, you may send to me the screenshot of your keywords planner, your clientCustomerId and the SOAP request and response generated so I can further investigate. You may reply via Reply privately to author.

Best regards,

Peter

ADWords API Team

[Joshua Kozlowski]

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.

$campaignEstimateRequest->setCriteria([$english, $unitedStates]);

[Peter Oliquino]

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 setCriteria() method.

Thanks and regards,

Peter

AdWords API Team