Google Ads Ingestion Source
See the Connector Marketplace topic. Please request your administrator to start a trial or subscribe to the Premium Google Ads connector.
In Gathr, it can be added as a channel to help in fetching customers’ and prospects’ data and transform it as needed before storing it in a desired data warehouse to run further analytics.
Data Source Configuration
Configure the data source parameters as explained below.
Fetch From Source/Upload Data File
To design the application, you can either fetch the sample data from the Google Ads source by providing the data source connection details or upload a sample data file in one of the supported formats to see the schema details during the application design phase.
Upload Data File
To design the application, please upload a data file containing sample records in a format supported by Gathr.
The sample data provided for application design should match the data source schema from which data will be fetched during runtime.
If Upload Data File method is selected to design the application, provide the below details.
File Format
Select the format of the sample file depending on the file type.
Gathr-supported file formats for Google Ads data sources are CSV, JSON, TEXT, Parquet and ORC.
For CSV file format, select its corresponding delimiter.
Header Included
Enable this option to read the first row as a header if your Google Ads sample data file is in CSV format.
Upload
Please upload the sample file as per the file format selected above.
Fetch From Source
If Fetch From Source method is selected to design the application, then the data source connection details will be used to get sample data.
Continue to configure the data source.
Connection Name
Connections are the service identifiers. A connection name can be selected from the list if you have created and saved connection details for Google Ads earlier. Or create one as explained in the topic - Google Ads Connection →
Use the Test Connection option to ensure that the connection with the Google Ads channel is established successfully.
A success message states that the connection is available. In case of any error in test connection, edit the connection to resolve the issue before proceeding further.
Entity
Tables in Google Ads are statically defined to model Google Ads entities.
If you selected the Fetch From Source method to design the application, the Entities will list as per the configured connection. Select the entity to be read from Google Ads.
If you selected the Upload Data File method to design the application, the exact name of the entity should be provided to read the data from Google Ads.
If you selected the Fetch From Source method to design the application, the Fields would list as per the Entity chosen in the previous configuration parameter. Select the fields or provide a custom query to read the desired records from Google Ads.
Fields
The conditions to fetch source data from a Google Ads table can be specified using this option.
Select Fields: Select the column(s) of the entity that should be read.
Custom Query: Provide an SQL query specifying the read conditions for the source data.
If Client Customer ID is specified in query, it will take precedence over the Client Customer ID specified in connection configuration.
Example:
SELECT * FROM AdGroupAd WHERE CustomerId='3333333333'
SELECT * FROM AdGroupAd WHERE CustomerId IN ('1111111111', '2222222222')
If you selected the Upload Data File method to design the application, provide a custom query to fetch records from the Google Ads entity specified in the previous configuration.
Query
The conditions to fetch source data from a Google Ads table can be specified using this option.
Provide an SQL query specifying the read conditions for the source data.
If Client Customer ID is specified in query, it will take precedence over the Client Customer ID specified in connection configuration.
Example:
SELECT * FROM AdGroupAd WHERE CustomerId='3333333333'
SELECT * FROM AdGroupAd WHERE CustomerId IN ('1111111111', '2222222222')
Add Configuration: Additional properties can be added using this option as key-value pairs.
More Configurations
This section contains additional configuration parameters.
Enable Partitioning
This enables parallel reading of the data from the entity.
Partitioning is disabled by default.
If enabled, an additional option will appear to configure the partitioning conditions.
Column
The selected column will be used to partition the data.
Max Rows per Partition: Enter the maximum number of rows to be read in a single request.
Example: 10,000
It implies that a maximum number of 10,000 rows can be read in one partition.
Advanced Configurations
This section contains advanced configuration parameters.
Fetch Size
The fetch size determines the number of rows to be fetched per round trip. The default value is 1000.
Support Enhanced SQL
When enabled, the system offloads as much of the SELECT statement processing as possible to Google Ads and then processes the rest of the query in memory.
In this way, the connector can execute unsupported predicates, joins, and aggregation.
When disabled, the system limits SQL execution to what is supported by the Google Ads API.
Query Passthrough
This option passes the query to the Google Ads server as is.
Recurse Children
Set this to false if you want to avoid recursing over customer client ids to get the full hierarchy for CustomerClientLink table.
Schema
Check the populated schema details. For more details, see Schema Preview →
If you have any feedback on Gathr documentation, please email us!