Google Ads data source

Learn how to set up a Google Ads data source and then move this data to one of the data destinations supported by Coupler.io 

2 steps to complete the setup

  1. Set up your data source
  2. Set up your data destination

1. Set up your data source

1.1. Select an application: Google Ads

1.2. Connect your Google Ads account

  • Click "Sign in with Google".
  • Log in to the Google account. 
  • Provide needed consent: 

1.3. Select Data Entity

Select a data category to import. Coupler.io supports 22 data categories like Ads, Campaigns, etc., and also 23 reports - including "Ad performance", "Search query performance" and others. 

1.4. Choose Ad account (-s) from the multi-select drop-down 

1.5. Set up reports' advanced settings

Start date - Define the start date of the period that should be covered in your report. By default, the start date is set to 30 days ago. Supported date format YYYY-MM-DD (e.g. 2023-06-01). This field supports macros. Learn more.

End date - Define the end date of the period that should be covered in your report. The default end date is today. Supported date format YYYY-MM-DD (e.g. 2023-06-30). This field supports macros. Learn more.

Conversion window - Specify the conversion window for your report. It can equal 60 or 90, or any number from 1 to 30 inclusive. The default conversion window is 30 days. Learn more.

Split data by periods - Specify the periods to split your report data. You can select several options: 

  • Date
  • Day of week
  • Month
  • Quarter
  • Week
  • Year

Metric values in your report will be split by all combinations of selected periods - e.g. for Quarter + Year - each row in the report will contain metrics for Q1 2023, Q2 2023, Q3 2023, etc.

2. Set up your data destination

Continue setting up the integration depending on the system you want to import data to. Select your tool from the list of supported data destinations and follow the relevant setup guide.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.