# Google Merchant Center integration for paid acquisition

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?

## Illustrative example

### Check declining eligible offers

Same completed 7-day windows; no monetary figures are used.

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

- Eligible offers (Google Merchant Center): 8,420 → 6,970
- Offers with price issues (Google Merchant Center): 18 → 1,102
- Shopping impressions (Google Ads): 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.

### What Hendrik sees

Eligible offers and Shopping impressions fell as price issues increased.

### What to do next

Fix the price issue and recheck eligibility before increasing bids.

**Limit:** The temporal association does not establish that the issue caused the impression decline.

## What Google Merchant Center contributes

Use Merchant Center with Google Ads and store data to identify whether an offer issue, feed problem, or campaign change needs attention first.

## Data Hendrik reads

- **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:** 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.
- **Accounts:** One Merchant Center account.
- **History:** The current product configuration defaults to 90 days. Hendrik shows the actual coverage after the first sync.
- **Refresh:** Configured data streams run from every 6 hours to daily. Hendrik shows the published freshness for each source after sync.
- **Setup timing:** Google Merchant Center 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 edit products, feeds, or policies.
- **Availability:** Your workspace shows Connect or Request access for your account.

## What you need to connect

- 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.

## Important limits

- 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.

## Provider documentation

- [Merchant Center product issues](https://support.google.com/merchants/answer/12409964)

## Start with Google Merchant Center

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