Search Term View for shopping campaigns

[Todd de Quincey]

Hi all,

Like many, we are in the process of migrating from Adwords to Ads, but we have hit a snag with one of the reports. 

In Adwords, we generated a SEARCH_QUERY_PERFORMANCE_REPORT with the following Adwords Query Language statement (excl. WHERE clause).

SELECT 
    Date,
    Device,
    ExternalCustomerId,
    AdGroupId,
    CampaignId,
    CampaignName,
    KeywordTextMatchingQuery,
    Query,
    Clicks,
    Cost,
    Impressions
FROM

    SEARCH_QUERY_PERFORMANCE_REPORT

In the above, we received shopping campaign data (which is what we are most interested in).

However, when I port this query to the Ads API, we do NOT get any shopping campaign data at all. The Ads query which we are using is below. Note, this is the query automatically generated by the Google Adwords to Ads migration tool.

SELECT
    segments.date,
    segments.device,
    customer.id,
    ad_group.id,
    campaign.id,
    campaign.name,
    segments.keyword.info.text,
    search_term_view.search_term,
    metrics.clicks,
    metrics.cost_micros,
    metrics.impressions
FROM
    search_term_view

I have not been able to find any documentation which states that shopping campaign data is not available from the search_term_view.

With that background in mind, I have three specific questions:

1. Is shopping campaign data available at all in the Ads search_term_view?
2. Presuming it is not available, can someone point me to some documentation for this?
3. Again presuming is it not available, is there a way of getting the search terms for shopping campaigns?

Hopefully that paints the full picture, but if not, please let me know and happy to provide more details. 

Many thanks in advance

Todd

[Todd de Quincey]

I think I found the answer at the following link. 

It appears that the segments.keyword.info.text field is not available on the search_term_view for shopping campaigns. 

Although, the text says that a keyword will not be returned, it should probably read, no shopping campaign data will be returned at all if this field is selected. Or is this a bug?

Is there any way around this?

[Google Ads API Forum Advisor]

Hi Todd,

Thank you for reaching out to our team and providing your observation.

Could you provide the complete request and response logs with request ID generated on your end for search_term_view with and without segments.keyword.info.text?

If you haven't enabled the logging of the API transactions for the specific client library that you are using, then please refer to the specific guide below:

• Java - https://developers.google.com/google-ads/api/docs/client-libs/java/logging
• .Net - https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging
• PHP - https://developers.google.com/google-ads/api/docs/client-libs/php/logging
• Python - https://developers.google.com/google-ads/api/docs/client-libs/python/logging
• Ruby - https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging
• Perl - https://developers.google.com/google-ads/api/docs/client-libs/perl/logging

You can provide the requested details via Reply privately to author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2Mkz8S:ref

[GregT]

Hi,

We've been upgrading to the Google Ads API as well and have run into the same issue. In the AdWords API, running the SEARCH_QUERY_PERFORMANCE_REPORT and asking for fields like Todd mentioned would return data for shopping campaigns, with the KeywordTextMatchingQuery field returning info about the product partition - for example, if it was a product partition that was advertising a single product (by its id), we'd get something like "id==myproductid" for the value in this column.  However, when running it as a Google Ads query on the search_term_view and asking for segments.keyword.info.text like Todd demonstrated (which appears to be the only thing roughly equivalent, as you cannot pull fields from ad_group_criterion or anything like that), we instead get 0 rows back for shopping campaigns. If we leave out the segments.keyword.info.text segment, then we get search data back for shopping campaigns, but without that field, it's not possible to match up the search query with specific products or product partitions/groups, which is important for us (and which we've been doing in the AdWords API for many years without issue).

It's possible to get this information in the Google Ads UI if you go into the Reports section where you can build your own report. I can add the ad group, search term, keyword/placement, device, cost, clicks, etc. to the report, and I get back the same kind of data we get with the SEARCH_QUERY_PERFORMANCE_REPORT in the AdWords API, with the keyword/placement field showing something like "id==myproductid", so this data is still available in your system.  Interestingly, though, if I add Keyword ID as an attribute to show in the report in the UI, it will come back with no data, like the search_term_view report does.

Is there some way to get per product or per product partition search query data in the new API? If so, could you please tell me how, and if not, could you *please* add this asap, as that's pretty important functionality to have disappear during this forced upgrade?

Thanks,

Greg

[GregT]

I meant to mention that the same thing happens with trying to ask for segments.keyword.ad_group_criterion. When querying for shopping campaigns, if you don't ask for it, you can get data back, but if you ask for it, you get 0 rows back (just like with the segments.keyword.info.text).

FYI,

Greg

[Google Ads API Forum Advisor]

Hello,

I apologize that the final solution here never made it back into the public thread. The removal of link from search term view to criteria is intentional. Here's a snippet from the resolution we had in the private portion of this thread:

It is an anti-pattern to associate search term directly with a shopping product. We are intentionally removing that link.

If you want to report on offer ID independent of the search term it's related to, you can use the shopping_performance_view. Specifically, the product_item_id field.

I have already raised this as a feature request and received this explanation. This one one of a few changes to reporting made in the Google Ads API to remove potentially misleading results.

Regards,
Mike, Google Ads API Team

ref:_00D1U1174p._5004Q2Mkz8S:ref

[GregT]

Thanks for the quick response, Mike.

That's odd reasoning to me.  When someone searches on Google, Google shows a specific product from the advertiser in the shopping search results.  I don't really see how it's an antipattern to show that that product's ad was served for that search query, any more than it would be an antipattern to show that a particular keyword's ad was shown in the search results for that query (which Google does still support via the API)?  And, as I mentioned, you can get this data from the Reports UI in Google Ads still, so why not provide it via the API?

Thanks,

Greg

[Google Ads API Forum Advisor]

Hello,

To follow up here, I'm investigating the UI version of this report that you mentioned, and comparing it to what we have in the API. I will get back to you once I have more information I can share.

[Google Ads API Forum Advisor]

Hello,

I have looked into this and learned a bit more. While I can't comment on the UI or its functionality, the API team has confirmed that this removal was intentional and we have no plans to bring it back in the API going forward. I apologize for the inconvenience.

[Ngon Nguyen]

Chào mừng bạn đến với bảng nhớ tạm của Gboard, bất kỳ văn bản nào bạn sao chép sẽ được lưu tại đây.Sử dụng biểu tượng chỉnh sửa để ghim, thêm hoặc xóa đoạn.Nhấn vào một đoạn để dán vào hộp văn bản.Chạm và giữ một đoạn để ghim đoạn đó. Các đoạn đã bỏ ghim sẽ bị xóa sau 1 giờ.

Vào 19:53, Th 3, 15 thg 3, 2022 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum <adwor...@googlegroups.com> đã viết:

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/_cdfH000000000000000000000000000000000000000000000R8SEH300NbCguvbfRbGjfpP0q_Bc8A%40sfdc.net.