# Google Ads integration for paid acquisition

Hendrik reads Google Ads campaigns, ad groups, ads, spend, delivery, search terms, Shopping reports, conversions, and account change history alongside your commerce data.

## Questions Hendrik can help answer

- What changed in delivery before performance moved?
- Did search terms or Shopping results need a business check?
- Did the campaign change, or did orders and payments change later?

## Illustrative example

### Validate a Shopping slowdown

The same 14-day windows and USD are used

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- Shopping spend (Google Ads): US$18,000 → US$13,000
- Shopping clicks (Google Ads): 36,000 → 25,000
- Disapproved offers (Google Merchant Center): 12 → 460

### What Hendrik checks

- **Confirm account scope:** Verify the Merchant account and Google Ads customer cover the same market.
- **Review change events:** Check for campaign, budget, or targeting changes.
- **Check eligibility:** Separate offer disapprovals from bidding or demand changes.

### What Hendrik sees

Shopping spend and clicks fell while disapproved offers increased sharply.

### What to do next

Resolve eligibility issues before increasing Shopping bids.

**Limit:** Merchant issues and delivery move together here; the example does not prove causation.

## What Google Ads contributes

Use Google Ads with commerce, payments, analytics, or Merchant Center data to see whether a performance change began in the campaign or later in the funnel.

## Data Hendrik reads

- **Campaign performance:** Daily and hourly spend, delivery, and platform metrics.
- **Conversion reporting:** Conversions reported by conversion date.
- **Search demand:** Keyword and search-term performance.
- **Shopping performance:** Product-level Shopping performance.
- **Changes:** Recorded account change events.

## Setup and access

- **Setup:** Sign in with Google, grant access, then select the Google Ads customer account. You can use an MCC: select the client account and, where needed, its manager account.
- **Permissions:** Google Ads OAuth `adwords` scope. This scope can read and manage Google Ads; Hendrik starts by reading account data.
- **Accounts:** A selected customer account and, where used, its login customer ID.
- **History:** The current product configuration defaults to 90 days. Hendrik shows the actual coverage after the first sync.
- **Refresh:** Configured data streams run from hourly to every 6 hours. Hendrik shows the published freshness for each source after sync.
- **Setup timing:** Google Ads starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- **Actions:** Connecting reads account data and does not change campaigns. If Hendrik later proposes a supported campaign change, a person must approve it before it runs.
- **Availability:** Your workspace shows Connect or Request access for your account.

## What you need to connect

- Confirm the selected customer account and reporting currency.
- Define conversion actions and attribution window before comparing values.
- Use a completed or explicitly labeled partial window.

## Important limits

- Platform conversion value is Google Ads reporting, not incremental value.
- It does not prove a sale, refund, margin, or stock outcome outside the platform.
- Cross-source campaign matching needs a verified relationship.

## Provider documentation

- [Google Ads reporting](https://developers.google.com/google-ads/api/docs/reporting/overview)

## Start with Google Ads

[Create a workspace and connect Google Ads](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=integration-google-ads&integration=google-ads)