Audience signal UI - AudienceSearchV2Service equivalent?

[Jarrod Mosen]

Hi, we're trying to recreate this component in our own UI:

We're having an issue with the "Interests & detailed demographics" section. We aren't getting all the results we'd expect. When we search for "football equipment", we only get about 6 results back - while in the official UI, we get many more.

When a user enters a query, we search across the following with GAQL:

• detailed_demographic
• user_interest
• user_list
• custom_audience

Are there any tables/reports that we're missing?

The official UI uses AudienceSearchV2Service - is this available to end users, or do we have to stitch our own queries together?

In the official UI, searching for "football" also returns results that don't necessarily have "football" in their name - (for example "NFL Information"). Is this searching across all sub/parent segments as well? How can we replicate this with GAQL?

Thank you!

An example query:

SELECT

user_interest.user_interest_id,

user_interest.name,

user_interest.resource_name,

user_interest.user_interest_parent,

user_interest.taxonomy_type,

user_interest.availabilities

FROM

user_interest

WHERE user_interest.name LIKE '%{searchTerm}%'"

[Google Ads API Forum Advisor]

Hi,

Thank you for raising this concern to the Google Ads API support team.

Regarding this concern, kindly note that Google Ads API mirrors the Google Ads UI. Meaning the data available in the Google Ads UI should be retrieved or managed via the Google Ads API. That being said, can you please provide the uncropped screenshot of the Google Ads UI showing the data that you want to retrieve via the Google Ads API and the complete API logs below for investigation. Also since this is specifically about Audiences data, then you may check our Audience Management (https://developers.google.com/google-ads/api/docs/remarketing/overview) guide for more details and information about this.

• request - https://developers.google.com/google-ads/api/docs/concepts/field-service#request
• response - https://developers.google.com/google-ads/api/docs/concepts/field-service#response
• request ID - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id
• request header - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers

Note that these logs can be requested or provided to the developer handling the Google Ads API transactions when logging of the API requests has been enabled. You may check here (https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging) and click your client library for the specific guideline to enable it.

For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include HTTP response headers in the output.

In addition, I would like to specify first the following when comparing the value of the UI and API:

• Comparing the API and UI on the same level as much as possible
• The segments and fields of the API and UI should be the same
• The date range is also the same

You may then send the requested logs via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.
 

This message is in relation to case "ref:_00D1U1174p._5004Q2mV7hA:ref"

Thanks,
 

Google Ads API Team