Re: No SearchBudgetLostImpressionShare in ad group performance report

Hi, According to the doc in help center http://support.google.com/adwords/bin/answer.py?hl=en&answer=2497703 Originally that column (BudgetLostImpressionShare) is not available in adgroup level. quote *Lost IS (budget): *The percentage of time that your ads weren't shown due

Re: No SearchBudgetLostImpressionShare in ad group performance report

But why is BudgetLostImpressionShare available on ad group level, just not the new search / content variants ? Also , you can quantify how many impressions an ad group could have had after the campaign ran out of money. Am 17.01.2013 08:45 schrieb "Takeshi Hagikura (AdWords API Team)" < adwordsapi

Re: No SearchBudgetLostImpressionShare in ad group performance report

Hi pete, ContentBudgetLostImpressionShare, SearchBudgetLostImpressionShare are not available for AdGroup Performance Report as Budgets can not be set ad AdGroup level. Those columns are only available for Account Performance Report, and Campaign Performance Report. Will correct the blog post.

Re: No SearchBudgetLostImpressionShare in ad group performance report

Hi Paul As you pointed out, the API documentation does not mention "SearchBudgetLostImpressionShare" nor whereas the blog post http://googleadsdeveloper.blogspot.co.uk/2012/12/impression-share-reporting-changes.html specifically mentions all the new IS columns (including 2 columns relating t

Re: No SearchBudgetLostImpressionShare in ad group performance report

Hi Arthur, The report type definitionslists all the data we have available, if a column doesn't exist, it's because we don't store that data. If you include columns that don't exist in the report, it responds with an error. Reg

No SearchBudgetLostImpressionShare in ad group performance report

Asking for this column results in an error of the api and also https://developers.google.com/adwords/api/docs/appendix/reports?hl=en#ad-group doesn't contain it. Is there any reason for this? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group