Collecting data from (Beta) Google Search Ads 360#
This guide explains how to collect data from (Beta) Google Search Ads 360. To learn how to collect data from a different data source, go back to the Available data sources in Adverity overview.
Introduction#
For a list of the fields that you can collect from (Beta) Google Search Ads 360, see Google Search Ads 360 Reports.
This connector uses the new Google Search Ads 360 Reporting API. It will replace the previous Google Search Ads 360 (Legacy) connector. For more information, see the Google announcement.
Note
You can use filters to narrow down the data you collect from (Beta) Google Search Ads 360. For more information, see Using filters with (Beta) Google Search Ads 360.
Limitations#
Collecting data from (Beta) Google Search Ads 360 comes with the following limitations:
Entity IDs (
agencyId
,advertiserId
,engineAccountId
) used in the legacy API are currently not available.Some combinations of custom floodlight variables and other fields result in errors when fetching data. It is currently not possible to use the API to determine valid combinations.
To avoid errors, use the (Beta) Google Search Ads 360 UI to find a valid combination of fields, then use this combination of fields in Adverity.
Creating a datastream to collect data from (Beta) Google Search Ads 360#
The basics of creating a datastream to collect data from any data source are explained in our guide to Collecting data in Adverity. This guide contains information about the specific steps to create a datastream to fetch data from (Beta) Google Search Ads 360.
Configuration: Choose the data you want to collect from (Beta) Google Search Ads 360#
To choose what data to collect and customize the (Beta) Google Search Ads 360 datastream configuration, follow these steps:
(Optional) Rename your datastream.
In Report type, select the type of data to collect from (Beta) Google Search Ads 360.
In Managers, Sub managers and Client accounts, select the managers, sub managers, and client accounts for which to collect data.
In Resource, select the resource on which to collect data.
In Segments, Metrics, Attributes, Custom columns, and Custom floodlight variables, change the list of fields that you want to see in your data extract.
(Optional) In the Advanced section, in Filter, enter expressions to filter your data before fetching the data. For example:
metrics.clicks > 7 campaign.name LIKE '%Retirement%' campaign.advertising_channel_type = 'PERFORMANCE_MAX'
For more information, see Using filters with (Beta) Google Search Ads 360.
What’s next?#
Apply Data Mapping to your collected data to harmonize data collected from different sources in Adverity.
Transform your data to meet your needs by creating and applying transformations to your datastream.
Load your data into Explore & Present to visualize your data in Adverity.
Load your data into an external destination of your choice.
Advanced (Beta) Google Search Ads 360 tips#
Using filters with (Beta) Google Search Ads 360#
When configuring a (Beta) Google Search Ads 360 datastream, you can use the Filter field in the Advanced section to filter your data before fetching results. This allows you to apply specific conditions to your queries, such as retrieving only certain campaign types or filtering by performance metrics.
The filter expressions support a number of operators, including:
Equality operators:
=
,!=
Comparison operators:
>
,>=
,<
,<=
String matching:
LIKE
,NOT LIKE
,CONTAINS ANY
,CONTAINS ALL
,CONTAINS NONE
Set operators:
IN
,NOT IN
Null checks:
IS NULL
,IS NOT NULL
Date ranges:
DURING
,BETWEEN
Regular expressions:
REGEXP_MATCH
,NOT REGEXP_MATCH
Example filter expressions:
metrics.clicks > 7
campaign.id IN (918735746)
campaign.name LIKE '%Retirement%'
metrics.impressions > 0 AND metrics.clicks > 10
campaign.advertising_channel_type = 'PERFORMANCE_MAX'
You can combine multiple conditions using AND
operators.
If your filter syntax is incorrect, you’ll see a validation error.
For more complex queries, refer to the full query grammar reference in the Google Search Ads 360 documentation.