how to get traffic estimates for keywords for a single campaign?

[petros...@gmail.com]

Is it possible to match the ui when looking for traffic estimates for keywords? From my understanding and following this: https://developers.google.com/adwords/api/docs/guides/traffic-estimator-service . It seems like if you want to match the same criteria, you can pass in the ids for campaign estimate request. However I was hitting an error for search rate limit. Is there a better way of doing this?

[Peter Oliquino (AdWords API Team)]

Hi Petros,

Yes, the results from the UI as compared to the API should be similar as long as you pass the correct parameters/filters in your requests. However, since you are encountering an error using the TrafficEstimatorService, could you provide to me the complete SOAP request and response so I can further investigate? You may reply to me using the Reply privately to author option.

Note:

We are running an annual developer feedback survey. Please take opportunity to leave feedback on how we can make managing campaigns at scale even easier.

Thanks and regards,

Peter

AdWords API Team

[petros...@gmail.com]

Hi Peter, I sent a private reply. Did you receive it?

[Sreelakshmi Sasidharan (AdWords API Team)]

Hello, 

Yes, we did receive the private reply. You are right, you could set the campaign IDs and campaign criteria to fine tune the results of traffic estimator service. However, it looks like your issue is hitting rate limit errors. This is not specific to the attributes that you set but based on how many API calls you make in a day which also depends on your developer token's access level(DEVELOPER scope). In a different scenario, it could also depend on how fast you are making the API call against a specific account (ACCOUNT scope). Based on the type of error, you may need to handle such errors in your application. Please check the linked guide which talks bout the rate limits. If you are able to share the error logs for rate limit errors I may be able to guide you better. 

Thanks,
Sreelakshmi, AdWords API Team

[petros...@gmail.com]

Hi Sreelakshmi,

I don't think I'm hitting a rate limit but rather a search limit. The return I'm getting back is this:

[Sreelakshmi Sasidharan (AdWords API Team)]

Hello,

There is a limit of 2,500 Keyword estimates per request and 50,000 sum of keywords x locations x languages in each campaign estimate request. Please check the limits guide for reference. You may need to adjust these to make the API call. Please let me know if you have any additional questions.

[petros...@gmail.com]

Correct me if I'm wrong, I thought you had to call the request with all its adgroups and then each adgroup has all its keywords. Could I make the call and have lets say a third of my adgroups in one call, the second third of adgroups in the second call and the last group in the third call assuming keywords x locations x languages is less than 50,000 for each.

[Sreelakshmi Sasidharan (AdWords API Team)]

Hello, 

Ideally, the request should be containing criteria for the specific keyword, its ad group and its campaign level details. The estimates being for the specific keyword, you could split the requests to contain data from a few ad groups so that the API will not hit this limit of number of criteria in one API call or number of keyword estimates in one API call. Please let me know if that helps. 

[petros...@gmail.com]

also since we cant input date range into the qpi request. what is the returned date range that is given for the traffic estimates.

[Luis Xander Talag (AdWords API Team)]

Hi,

I'm a colleague of Sreelakshmi and allow me to assist you as she is OOO. With regards to your concern on the date range for the TrafficEstimatorService, I'm afraid it is not supported on the API side as you can see on the comparison of Keyword Planner to AdWords API on the lower section of this guide.

Hope this clarifies your concern.

Thanks and regards,

Luis

AdWords API Team

[petros...@gmail.com]

Hi, 

I know the data range isn't supported but I was wondering when I pull the data, what is the data range. Is it a week?

[Luis Xander Talag (AdWords API Team)]

Hi,

There is no specific date range for the result of TrafficEstimatorService. This service is used to estimate future traffic based on your proposed or existing campaigns, ad groups, and keywords.

Regards,

Luis

AdWords API Team

[petros...@gmail.com]

I'm not sure I follow. When I pull data I'm getting back results like clicks etc... Is there no data range for which you are predicting I will get x amount of clicks. 

[Luis Xander Talag (AdWords API Team)]

Hi,

The TrafficEstimatorService does not support date range. What this service does is provide estimates on performances of your keywords or other AdWords entities based on historical data. The data returned by this service is an estimate on a daily basis via the StatsEstimate such as the clicksPerDay field or impressionsPerDay field.

Also, you should take note that the returned values are estimates, and are not a guarantee that actual performance will be within these bounds.

Regards,

Luis

AdWords API Team

[petros...@gmail.com]

Hi Luis,

That makes a lot more sense now. Thank you. I just have one last question. What would be the best way to make the calls to get all the keywords for the campaigns. I'm currently am hitting traffic limits when I limit to just 1 adgroup id at a time and when I split the request further down to an x amount of keywords per adgroup, I hit a rate limit. Is there a service I can use in conjuction with the traffic estimate service to do it for large jobs.

[Luis Xander Talag (AdWords API Team)]

Hi,

I'm afraid that there is no other service available that you could use in conjunction with the TrafficEstimatorService to do a large jobs because the BatchJobService does not support it. Also, you may take note that there is a limit of 2,500 keyword estimates per request which is stated on our system limits guide. 

However, one of the simplest ways to recover from the RateExceededError is to slow down your request. You could use the value of the RateExceededError.retryAfterSeconds as the interval when retrying your request again to further avoid the error. You may check this guide for more information about the rate limits.

Regards,

Luis

AdWords API Team

[Hammad Saleem Ch]

Hi Luis,

I am getting a problem with TrafficEstimatorService because the stats of Keyword Planner UI and TrafficEstimatorService in the AdWords are not matched. 
The estimated clicks and CPC are different. Please guide how we can relate the stats and validate if this is not possible so tell me which stats are valid TrafficEstimatorService or Keyword Planner.

Regards,
Hammad Saleem

[Hammad Saleem Ch]

Estimates:  {

    'campaignEstimates': [

        {

            'Estimate.Type': 'CampaignEstimate',

            'campaignId': None,

            'adGroupEstimates': [

                {

                    'Estimate.Type': 'AdGroupEstimate',

                    'adGroupId': None,

                    'keywordEstimates': [

                        {

                            'Estimate.Type': 'KeywordEstimate',

                            'criterionId': None,

                            'min': {

                                'averageCpc': {

                                    'ComparableValue.Type': 'Money',

                                    'microAmount': 143681

                                },

                                'averagePosition': 1.1308206751828902,

                                'clickThroughRate': 0.10041292416286662,

                                'clicksPerDay': 1318.9349,

                                'impressionsPerDay': 11821.6,

                                'totalCost': {

                                    'ComparableValue.Type': 'Money',

                                    'microAmount': 210562512

                                }

                            },

                            'max': {

                                'averageCpc': {

                                    'ComparableValue.Type': 'Money',

                                    'microAmount': 175611

                                },

                                'averagePosition': 1.0,

                                'clickThroughRate': 0.12272691322135731,

                                'clicksPerDay': 1612.0316,

                                'impressionsPerDay': 14448.623,

                                'totalCost': {

                                    'ComparableValue.Type': 'Money',

                                    'microAmount': 257354192

                                }

                            }

                        }

                    ]

                }

            ],

            'platformEstimates': [

                {

                    'platform': {

                        'id': 30000,

                        'type': None,

                        'Criterion.Type': 'Platform',

                        'platformName': 'Desktop'

                    },

                    'minEstimate': {

                        'averageCpc': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 138872

                        },

                        'averagePosition': 1.1199432245875258,

                        'clickThroughRate': 0.16054574868955207,

                        'clicksPerDay': 560.48346,

                        'impressionsPerDay': 3142.0022,

                        'totalCost': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 86483680

                        }

                    },

                    'maxEstimate': {

                        'averageCpc': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 169732

                        },

                        'averagePosition': 1.0,

                        'clickThroughRate': 0.19622259118280816,

                        'clicksPerDay': 685.03534,

                        'impressionsPerDay': 3840.2249,

                        'totalCost': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 105702288

                        }

                    }

                },

                {

                    'platform': {

                        'id': 30001,

                        'type': None,

                        'Criterion.Type': 'Platform',

                        'platformName': 'Mobile'

                    },

                    'minEstimate': {

                        'averageCpc': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 145423

                        },

                        'averagePosition': 1.1349618735568225,

                        'clickThroughRate': 0.07837393076223975,

                        'clicksPerDay': 750.3579,

                        'impressionsPerDay': 8616.667,

                        'totalCost': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 121243808

                        }

                    },

                    'maxEstimate': {

                        'averageCpc': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 177739

                        },

                        'averagePosition': 1.0,

                        'clickThroughRate': 0.09579036443429345,

                        'clicksPerDay': 917.1041,

                        'impressionsPerDay': 10531.483,

                        'totalCost': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 148186880

                        }

                    }

                },

                {

                    'platform': {

                        'id': 30002,

                        'type': None,

                        'Criterion.Type': 'Platform',

                        'platformName': 'Tablet'

                    },

                    'minEstimate': {

                        'averageCpc': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 315255

                        },

                        'averagePosition': 1.192718113600363,

                        'clickThroughRate': 0.11574698528986538,

                        'clicksPerDay': 8.093489,

                        'impressionsPerDay': 62.93157,

                        'totalCost': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 2835013

                        }

                    },

                    'maxEstimate': {

                        'averageCpc': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 385311

                        },

                        'averagePosition': 1.0,

                        'clickThroughRate': 0.1414685443903867,

                        'clicksPerDay': 9.892042,

                        'impressionsPerDay': 76.91637,

                        'totalCost': {

                            'ComparableValue.Type': 'Money',

                            'microAmount': 3465016

                        }

                    }

                }

            ]

        }

    ]

[Google Ads API Forum Advisor Prod]

Hi Hammad,

The TrafficEstimatorService from the AdWords API and Google Ads UI don't match because what is getting called on the back-end are not the same. The data is put together differently. You will need to use one of the idea services from Google Ads API.

Regards,
Anthony
Google Ads API Team 

ref:_00D1U1174p._5001UXUAzi:ref