Skip to main content
The Google Ads live data source reads one Google Ads account, by day and by campaign or ad group. Each query is one report request, and Lightdash shows the results as they come back from Google. It’s a level 3 integration: its API returns reports.

Before you start

  • Live data sources enabled for your organization. See Live data sources.
  • Admin role in the Lightdash project.
  • A Google account that can read the Google Ads account. Read-only access is enough.

Connect Google Ads

  1. On the nav bar, click Browse → Semantic Layer.
  2. In the sidebar, select Live data sources, then click Add.
  3. Select Google Ads.
  4. Enter a Name, such as Google Ads.
  5. Click Continue to Google.
  6. Sign in with your Google account and allow access.
  7. Back in Lightdash, pick the account the source reads.
The list shows client accounts, including those under a manager account. Google only reports metrics for client accounts, so you can’t pick a manager account itself. Lightdash adds an Ad performance table to Explore. Queries run with the Google account that signed in. To change it, choose Sign in again from the source’s menu. Google’s consent screen asks for access to manage your Google Ads account, because Google has only one permission for its Ads API. Lightdash limits the source to the read-only report endpoint of the account you picked.

Dimensions

Ads, keywords, search terms and conversion actions aren’t available.

Metrics

Combination rules

Google Ads returns one row per campaign or ad group and doesn’t group across them, so a query has to identify the rows it returns:
  • Any campaign dimension needs Campaign name or Campaign ID in the query.
  • Any ad group dimension needs Ad group ID, or Ad group name with Campaign name or Campaign ID.
  • To filter by Day of week, Device or Network, also add that dimension to the query.
  • To filter by a campaign or ad group, include a dimension at that level or a finer one. For example, add Campaign name before you filter by it.
Lightdash checks these rules before calling Google and tells you which dimension to add. Google also rejects some combinations of metrics and dimensions. When it does, Lightdash shows Google’s error.

Supported features

Limits

When a query has more than 9,999 rows, Lightdash shows an error rather than a partial result. Narrow the date range, add a filter or remove a dimension. Google Ads also applies its own daily quota to the Google Cloud project behind the sign-in, shared by every source that uses it.

Example questions

  • “Cost and conversions by campaign over the last 30 days.”
  • “Top 10 ad groups by clicks last month, with their campaign.”
  • “Weekly cost per conversion by device since the start of the quarter.”

Troubleshooting

Numbers don’t match the Google Ads interface. Check the date range first. Relative dates such as last 7 days use the project’s time zone to decide what today is, so they can be a day off from the account’s. Google can also keep updating conversions for several days. Your query needs a dimension you didn’t pick. See Combination rules. The error names the dimension to add.