ETL: Google Ads Source

​

Connection Setup

​

To create a Google Ads connection in Integrate.io ETL

1

Click the Connections icon (lightning bolt) on the top left menu.

2

To create a connection, click New connection.

3

Select Google Ads.

4

Click Authenticate.

5

In the Google account window, choose an existing Google account or click Add account to create a new Google account.

6

In the next Google window click Accept to authorize Integrate.io ETL access.

7

In the new Google Ads connection window, name the connection and click Create connection.

​

To modify a Google Ads connection in Integrate.io ETL

1

Click the Connections icon (lightning bolt) on the top left menu.

2

Click a connection to open and modify it. Make any necessary changes, then click Reconnect, and Save changes. To exit the Google Ads connection window without changes, click Back to connections (grey tab on the left side) on the Google Ads connection window.

3

To delete a Google Ads connection, click the three vertical dots on the far right of the connection listing and select the Delete connection option.

​

Connection

​

Source Properties

• API Version - Select AdsV25, AdsV24, AdsV23, or AdsV22. New Google Ads source components, and components saved without a version, default to AdsV25. Integrate.io ETL runs packages saved with AdsV19 to AdsV23 on Google Ads API v23, so you don’t need to edit packages saved with a retired version. Packages saved with AdsV24 run on v24. Packages saved with AdsV25, Latest, or Default run on v25. If you open a component saved with AdsV19, AdsV20, or AdsV21, the editor switches it to AdsV25 and loads the v25 report types. Your selected report type is kept. Saving the component stores AdsV25. If you cancel, the component keeps its saved version. Google sunsets older versions of the API every few months.
• Report type - Select a report type from the dropdown list of reports. See this article to map reports to Google AdWords UI. Note: For structure reports, select “All time” in date range. We are using report types from the old version of Google Adwords.
• Date range - Select a date range from the dropdown list of ranges. If you select custom date range..., you will be prompted to enter From date and To date. Click either inputs and select the dates from the calendar. You can also use variables as values for the custom date range in the format yyyyMMdd.
• customer ids - Leave empty to read data for all Ads customer account ids accessible to the connection or use a comma separated list of Ads customer account ids. The account ids appear in the top right corner of your Ads page or are managed by Ads Manager (MCC). If you provide an MCC account’s customer id, the report will be executed for all the Ads accounts it has access to. Customer ids appear in the format nnn-nnn-nnnn (e.g. 123-456-7890)

​

Source Schema

​

Changes in Google Ads API v23

• Call ad fields return empty values. Google removed call ads in v23. The following AD_PERFORMANCE_REPORT fields stay in the schema, but their columns are always empty: AdCallAdBusinessName, AdCallAdConversionAction, AdCallAdConversionReportingState, AdCallAdCountryCode, AdCallAdHeadline1, AdCallAdHeadline2, AdCallAdPath1, AdCallAdPath2, CallOnlyPhoneNumber, Description1CallAd, and Description2CallAd. The AdsV23, AdsV24, and AdsV25 field lists don’t offer these fields. Components saved with AdsV22 still list them, so existing selections stay valid. If your package uses these fields, remove them or make sure downstream steps accept empty values.
• Campaign start and end dates keep their format. StartDate and EndDate in CAMPAIGN_PERFORMANCE_REPORT, and CampaignStartDate and CampaignEndDate in the ASSET_GROUP report, now come from the v23 date-time fields. Integrate.io ETL trims the value to the date, so the column format doesn’t change.

​

Changes in Google Ads API v24 and v25

• Video brand safety field returns empty values. Google removed campaign.video_brand_safety_suitability in v24. The CampaignVideoBrandSafetySuitability field in the ASSET_GROUP report stays in the schema, but its column is always empty on v24 and v25. The AdsV24 and AdsV25 field lists don’t offer this field. Components saved with AdsV22 or AdsV23 still list it. If the editor switches a component to AdsV25 and the component selects this field, the editor shows a schema warning. After you save, the column is empty.
• v25 changes no report fields. v25 uses the same fields as v24.

​

Related