Google AdWords Report API mapping required with Google Ads new version.

115 views
Skip to first unread message

Qaiser Javed

unread,
Jun 28, 2019, 11:10:29 AM6/28/19
to AdWords API and Google Ads API Forum
Hi Members,

Please help to map following Report APIs with new version of Google Ads.

  1. Not able to fine any info for  criteria_performance_report
  2. Mapping for Geo_Performance_Report
  3. Mapping for CAMPAIGN_SHARED_SET_REPORT & SHARED_SET_REPORT
  4. Mapping for Landing_Page_Report
  5. Mapping for "Status" attribute in Keyword_Performance_Report
Thanks,
Qaiser Javed

Google Ads API Forum Advisor Prod

unread,
Jun 28, 2019, 5:14:07 PM6/28/19
to qasj...@gmail.com, adwor...@googlegroups.com
Hello Qaiser, 

Please find my response below:
  1. Not able to fine any info for  criteria_performance_report: You may use the individual criteria report types (age, gender, audience) or ad_group_criterion and campaign_criterion resources. 
  2. Mapping for Geo_Performance_Report: You may use the UserLocationView resource to pull the country level data. 
  3. Mapping for CAMPAIGN_SHARED_SET_REPORT & SHARED_SET_REPORT: You may use the shared_set report for this.
  4. Mapping for Landing_Page_Report: You may use the LandingPageView and ExpandedLandingPageView resources to pull the data at the Final URL level. The equivalent of Landing Page Report should be available in the upcoming releases.
  5. Mapping for "Status" attribute in Keyword_Performance_Report: You may use the Keyword View and get the status by selecting the ad_group_criterion.status
The migration guide should be helpful identifying the resources with the report types. Let me know if you have any questions.

Regards,
Bharani, Google Ads API Team

ref:_00D1U1174p._5001UCa0v8:ref

Qaiser Javed

unread,
Jul 5, 2019, 8:26:16 AM7/5/19
to AdWords API and Google Ads API Forum
Hello Bharani,

Following issues are facing.

1. SearchExactImpressionShare can not use with Device in new Google Ads API while It was functioning with Google AdWords API.
Error:

Cannot select the following segments because at least one unsupported metric is found in SELECT or WHERE clause: 'segments.device'(unsupported metrics: 'search_exact_match_impression_share').


2. + can not be used with Like and Not Like operator.
Error:

Status(StatusCode=Internal, Detail="Internal error encountered.") Query:  SELECT metrics.average_cpc,metrics.average_position,metrics.clicks,metrics.conversions,metrics.cost_micros,metrics.cost_per_conversion,metrics.ctr,metrics.impressions,ad_group_criterion.keyword.match_type,metrics.search_impression_share,metrics.search_rank_lost_impression_share,customer.id,ad_group_criterion.status,segments.ad_network_type,ad_group_criterion.keyword.text,ad_group_criterion.keyword.match_type FROM keyword_view WHERE customer.id IN (##########)  AND ad_group_criterion.status IN (ENABLED,PAUSED)  AND segments.ad_network_type IN (SEARCH,SEARCH_PARTNERS)  AND ad_group_criterion.keyword.text  NOT LIKE '%+%'  AND ad_group_criterion.keyword.match_type IN (BROAD)  AND segments.date >= '2019-05-09' AND segments.date <= '2019-06-05'


These both functionality was running with old API but new API generating error.

Please help.

Thanks & Regards,
Qaiser Javed

Google Ads API Forum Advisor Prod

unread,
Jul 8, 2019, 11:05:28 AM7/8/19
to qasj...@gmail.com, adwor...@googlegroups.com
Hello Qaiser, 

That's right. The field metrics.search_exact_match_impression_share currently supports segmentation based on the fields listed in the drop-down. I have shared this with the team. Please keep an eye on our blog for more updates. 

Thanks,

Qaiser Javed

unread,
Jul 9, 2019, 8:44:02 AM7/9/19
to AdWords API and Google Ads API Forum
Hello Team,

Please provide the guidance for the following point as well.

+ can not be used with Like and Not Like operator.
Error:

Status(StatusCode=Internal, Detail="Internal error encountered.") Query:  SELECT metrics.average_cpc,metrics.average_position,metrics.clicks,metrics.conversions,metrics.cost_micros,metrics.cost_per_conversion,metrics.ctr,metrics.impressions,ad_group_criterion.keyword.match_type,metrics.search_impression_share,metrics.search_rank_lost_impression_share,customer.id,ad_group_criterion.status,segments.ad_network_type,ad_group_criterion.keyword.text,ad_group_criterion.keyword.match_type FROM keyword_view WHERE customer.id IN (##########)  AND ad_group_criterion.status IN (ENABLED,PAUSED)  AND segments.ad_network_type IN (SEARCH,SEARCH_PARTNERS)  AND ad_group_criterion.keyword.text  NOT LIKE '%+%'  AND ad_group_criterion.keyword.match_type IN (BROAD)  AND segments.date >= '2019-05-09' AND segments.date <= '2019-06-05'




This functionality was running with old API but new API generating error.

Please suggest.


Thanks

Google Ads API Forum Advisor Prod

unread,
Jul 10, 2019, 5:21:52 PM7/10/19
to qasj...@gmail.com, adwor...@googlegroups.com
Hi Qaiser,

Thanks for the question - I'm looking into this for you and will get back to you with more information as soon as possible.

Thanks,
Ben Karl, Google Ads API Team

ref:_00D1U1174p._5001UCa0v8:ref

Google Ads API Forum Advisor Prod

unread,
Jul 10, 2019, 5:46:25 PM7/10/19
to qasj...@gmail.com, adwor...@googlegroups.com
Hi Qaiser,

This appears to be a bug. While the team works on getting it fixed, I think you can successfully use this filter with a different regex, can you try:

WHERE ad_group_criterion.keyword.text  NOT LIKE '.^+.^'

This is assuming you intended "%" to be a wildcard operator.

Let me know if that helps or if you have any further questions.

Best,

Google Ads API Forum Advisor Prod

unread,
Jul 11, 2019, 11:02:55 AM7/11/19
to qasj...@gmail.com, adwor...@googlegroups.com
Hi Qaiser,

One more thought - based on the structure of your query I'm assuming you intended the "+" to be interpreted literally. Looking at the documentation for GAQL the "+" is an operator used to represent one of more of a specific character. In order to have it interpreted literally you will need to escape it with two backslashes, so the below should also work for you:

"%\\+%"

Hope this helps!

Best,
Ben, Google Ads API Team

ref:_00D1U1174p._5001UCa0v8:ref
Reply all
Reply to author
Forward
0 new messages