Google Merchant Center integration
Connect Google Merchant Center to Hendrik.
Hendrik reads Google Merchant Center products, product status, product issues, account issues, and performance so you can separate Shopping eligibility from campaign delivery.
Questions Hendrik can help answer
- Are offer issues limiting eligible inventory?
- Did an account issue appear with a delivery change?
- Should a feed or policy fix happen before a bid change?
Google Merchant Center + Google Ads example
Check declining eligible offers
Same completed 7-day windows; no monetary figures are used.
| Metric | Previous | Current |
|---|---|---|
| Google Merchant CenterEligible offers | 8,420 | 6,970 |
| Google Merchant CenterOffers with price issues | 18 | 1,102 |
| Google AdsShopping impressions | 1,900,000 | 1,310,000 |
What Hendrik checks
Confirm country scope
Use the same target country in both integrations.
Review issue examples
Identify the specific pricing issue rather than treating all ineligible offers alike.
Check campaign changes
Rule out a concurrent budget or target change.
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 Merchant Center
Use Merchant Center with Google Ads and store data to identify whether an offer issue, feed problem, or campaign change needs attention first.
- Products
- Submitted product records.
- Product status
- Offer eligibility and status.
- Issues
- Product and account issues.
- Performance
- Daily Merchant Center performance reports.
Setup and access
Setup and access for Google Merchant Center
- Setup
- When enabled, sign in with Google and select the Merchant Center account.
- Permissions
- Google Merchant Center OAuth `content` scope. This scope can read and manage Merchant Center; Hendrik starts by reading account data.
- Supported accounts
- One Merchant Center account.
- 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 every 6 hours to daily. Hendrik shows the published freshness for each source after sync.
- Setup time
- Google Merchant Center 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 edit products, feeds, or policies.
- Integration availability
- Your workspace shows Connect or Request access for your account.
Requirements and data limits
What you need
- Confirm the Merchant account, country, and feed scope.
- Check that the ads and Merchant accounts refer to the same market before comparing.
- Use a consistent product and reporting date.
Keep these differences in mind
- Eligibility data does not prove a campaign delivery cause.
- Offer-to-store-product mapping must be established for product-level claims.
- Merchant performance is not a substitute for store financial outcomes.
- The temporal association does not establish that the issue caused the impression decline.
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