Integration
Google Merchant Integration
Prepare Google Merchant-ready records in LynkPIM with validation, mapping, and feed-quality controls before export.
Last updated: 2026-03-21
What syncs
- Required Google Merchant fields such as titles, images, pricing, and identifiers
- Channel-specific feed attributes and export-ready product sets
Directionality and supported entities
- Outbound feed publishing from LynkPIM to Google Merchant delivery workflows
- Products
- Images
- Pricing and availability fields
- Google-specific feed attributes
Mapping behavior and scheduling
- Map required feed fields by category
- Use validation to block incomplete or malformed feed rows before export
- Recurring feed export windows
- Manual re-export when urgent fixes are needed
Auth, setup, and retry handling
- Define target countries, feed scope, and category rules
- Pilot high-volume categories first to reduce issue volume
- Review validation failures before export
- Track recurring disapprovals to improve attribute rules and feed mapping
Related docs and commercial pages
Integration FAQs
Why validate before publishing a feed?
Because required-field and formatting issues are cheaper to fix upstream than after Google flags them.
Can Merchant feeds use a broader product model?
Yes. PIM should keep a rich product model and output only the feed-specific subset Google needs.
Need to scope the google merchant integration rollout?
We can help define mapping ownership, publish rules, retry handling, and the right pilot scope for your team.