Google Ads + Datagrid integration

Overview

What is Google Ads: Google Ads is Google's online advertising platform for Search, Display, YouTube, Shopping, Demand Gen, and Performance Max campaigns. Its Smart Bidding system uses Google AI to optimize for conversions or conversion value in every auction, and its Customer Match feature reaches customers using online and offline data across Search, the Shopping tab, Gmail, YouTube, and Display.

How to integrate Google Ads with Datagrid

Datagrid connects to Google Ads through the Google Ads API. Agents run GAQL queries against campaign, ad group, keyword, and metrics resources, then process results alongside CRM, analytics, and warehouse data. Datagrid reads campaigns, ad groups, ads, keywords, Performance Max asset groups, and performance metrics; it writes offline conversions and Customer Match list memberships, but does not write campaign structures such as campaigns, ad groups, ads, keywords, or asset groups. Set up the integration by selecting Google Ads in Datagrid, authorizing API access, and configuring the data sync details.

Select Google Ads in Datagrid

Start by choosing the Google Ads integration and defining which account and campaign data agents can access.

1. In Datagrid, go to Settings > Integrations > Add New and select Google Ads.

2. Sign in with a Google account that has access to the target Google Ads account.

3. Grant Datagrid the requested OAuth permissions.

4. If you manage accounts through a manager account (MCC), select the client account to sync.

5. Choose the campaigns and report types agents should access, then save the connection.

A typical integration setup keeps selected scopes explicit:

google_ads_integration:
  account_access: "Google Ads account or manager account (MCC)"
  campaign_scope: "selected campaigns"
  report_scope: "selected report types"
  write_scope:
    - "offline conversions"
    - "Customer Match user lists"

Authorize Google Ads API access

Google Ads API authentication requires two credentials: an OAuth scope of https://www.googleapis.com/auth/adwords, and a developer token that grants API access. Account-level access is configured through OAuth 2.0, and calls made through a manager account include the login-customer-id header.

Use this authorization checklist when connecting through a manager account:

google_ads_auth:
  oauth_scope: "https://www.googleapis.com/auth/adwords"
  developer_token: "required"
  account_access: "configured through OAuth 2.0"
  manager_account_header: "login-customer-id"

Configure data sync details

Configure the sync direction by object type so that reporting reads remain separate from conversion and audience writes.

• Campaigns, ad groups, ads, keywords: Read-only, GAQL read via GoogleAdsService

• Performance metrics and segments: Read-only, GAQL via Search or SearchStream

• Offline conversions: Upload-only, ConversionUploadService with ClickConversion objects

• Customer Match user lists: Upload-only membership, OfflineUserDataJobService with OfflineUserDataJobOperation objects. As of April 1, 2026, Google requires a developer token to have prior Customer Match usage before these calls succeed; new integrations should use the Data Manager API instead.

• Asset groups (Performance Max): Read-only, GAQL read via GoogleAdsService

Configure sync frequency by workflow. A common pattern syncs campaign metrics every 15 to 30 minutes during business hours, syncs conversions in near real time, and syncs historical trends daily or weekly.

A scheduled metrics sync can use the same fields agents use for recurring reporting:

SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.clicks,
  metrics.cost_micros,
  metrics.all_conversions
FROM campaign

An offline conversion upload keeps the click identifier explicit. Each ClickConversion must use exactly one click identifier field:

{
  "ConversionUploadService": {
    "ClickConversion": {
      "gclid": "stored-click-id",
      "gbraid": null,
      "wbraid": null
    }
  }
}

A Customer Match membership upload keeps the user list and membership action separate from reporting reads:

{
  "OfflineUserDataJobService": {
    "OfflineUserDataJob": {
      "user_list": "Customer Match user list"
    },
    "OfflineUserDataJobOperation": {
      "create": {
        "user_identifiers": ["customer identifier"]
      }
    }
  }
}

Why use Google Ads with Datagrid

Datagrid turns Google Ads data into repeatable reporting, attribution, conversion, and audience workflows that agents execute on a schedule.

• Automated report assembly: Agents run GAQL queries on a schedule and deliver campaign-level and keyword/search term reports without manual exports.

• Cross-channel attribution: Agents combine Google Ads spend with GA4 data, normalize event names and map UTM parameters to campaign objectives.

• Closed-loop conversion tracking: Agents detect closed deals in your CRM and upload offline conversions with the stored GCLID, so bidding optimizes for revenue events.

• Warehouse-driven audiences: Agents push modeled segments from BigQuery or Snowflake into Customer Match for targeting, including suppression and retargeting.

• Extended reporting history: Agents archive older Google Ads reporting data in your warehouse for long-term trend analysis beyond Google Ads' retention limits.

• One credential setup, many workflows: A single authorized connection feeds multiple agents at once.

What you can build with Google Ads Datagrid integration

Teams responsible for paid acquisition and revenue operations can assemble cross-channel datasets, upload CRM revenue events, keep exclusion audiences up to date, and prepare keyword changes for review.

• Cross-channel performance dashboard: Agents pull Google Ads metrics alongside other paid media and GA4 data, standardize metric definitions, then push a blended dataset with cost per acquisition per channel to your BI tool on a recurring schedule.

• CRM-to-ads conversion pipeline: When a lead converts in HubSpot, an agent matches the stored click ID, formats a ClickConversion record, and uploads it via ConversionUploadService so bid strategies can optimize against actual revenue events.

• Audience suppression workflow: An agent queries your warehouse for the current customer list and uploads it to Customer Match. A marketer then attaches the list as an exclusion in Google Ads, protecting spend and keeping audiences current across platforms.

• Search term mining agent: An agent queries search_term_view weekly, flags high-cost terms with zero conversions, and drafts a negative keyword list for review before applying any changes.

Resources and documentation

• Google Analytics integration: Pair GA4 data with Google Ads campaign performance.

• Google Ads API introduction: Review before selecting the report and account scope.

• OAuth 2.0 overview: Review when planning authorization.

• GAQL query overview: Structure reporting queries.

• Offline conversion guide: Review when preparing conversion uploads.

• Customer Match integration guide: Review before uploading audience list memberships.

• Reporting overview: Confirm reporting resources and metrics.

Frequently asked questions

What credentials does the Google Ads integration require?

Datagrid authenticates through the Google Ads API using OAuth 2.0 credentials and a developer token. The 22-character developer token is obtained from the API Center of a Google Ads manager account; account access is granted via OAuth 2.0.

How does Datagrid keep Google Ads data up to date without webhooks?

The Google Ads API has no webhook or push notification mechanism, so Datagrid handles this with scheduled polling and incremental syncs on a configurable schedule.

How do offline conversion uploads work?

Google Ads assigns a Google Click ID (GCLID) to each ad click. Store it with the lead, then upload the conversion through ConversionUploadService after the sale closes. Each ClickConversion must use exactly one of gclid, gbraid, or wbraid. GCLIDs expire after 90 days.

How do I query Performance Max reporting data?

Performance Max campaigns use AssetGroup resources instead of AdGroup and AdGroupAd. Querying ad_group or ad_group_ad returns no data for these campaigns; query asset_group instead.

Similar integrations

• Google Analytics: Combine Google Ads performance data with GA4 metrics for unified attribution and cross-channel reporting with campaign-to-session linking.

• Facebook Ads: Include Facebook Ads data for cross-channel ad spend and performance comparisons, with multi-platform attribution and consolidated reporting.

• LinkedIn Pages: Import LinkedIn Pages engagement and audience data to merge B2B lead signals with Google Ads performance for better targeting.

• Mixpanel: Combine Mixpanel product analytics with Google Ads spend data to connect ad performance to actual in-product engagement and conversion events.

• HubSpot: Send CRM conversions from HubSpot to Google Ads for offline conversion uploads and improved bid optimization and audience creation.

• BigQuery: Export Google Ads reports into BigQuery for long-term storage and advanced SQL analysis, with warehouse-driven reverse-ETL audience modeling.

Browse by category

• Marketing