Google Ads integration
Connect Google Ads to Hendrik.
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?
Google Ads + Google Merchant Center example
Validate a Shopping slowdown
The same 14-day windows and USD are used
| Metric | Previous | Current |
|---|---|---|
| Google AdsShopping spend | US$18,000 | US$13,000 |
| Google AdsShopping clicks | 36,000 | 25,000 |
| Google Merchant CenterDisapproved offers | 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.
About this example Synthetic data · Illustrative analysis · Changes require your approval.
How Hendrik handles your dataWant Hendrik to answer this with your data?
Your connected data
What Hendrik reads from Google Ads
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.
- 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 and access for Google Ads
- 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.
- Supported accounts
- A selected customer account and, where used, its login customer ID.
- Available history
- The current product configuration defaults to 90 days. Hendrik shows the actual coverage after the first sync.
- Data refresh
- Configured data streams run from hourly to every 6 hours. Hendrik shows the published freshness for each source after sync.
- Setup time
- Google Ads starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- Can Hendrik make changes?
- 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.
- Integration availability
- Your workspace shows Connect or Request access for your account.
Requirements and data limits
What you need
- 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.
Keep these differences in mind
- 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.
- Merchant issues and delivery move together here; the example does not prove causation.
Your data. Your next step.
Put Hendrik to work on your stack.
Create your account, choose your workspace and connect your data.
See plans and pricing