Your product feed and order tracking do different jobs. A tracking extension reports events; it does not create a Merchant Center feed or resolve product disapprovals.
Confirm your edition and store view
Magento Open Source, Adobe Commerce on-premises, and Adobe Commerce on cloud infrastructure use different deployment processes. Adobe Commerce as a Cloud Service is a separate SaaS product. Confirm your edition before choosing an integration. For each store view, check the destination country, language, currency, and shipping settings.
Four checks for your product feed
- Variants: give each submitted variant a unique product ID. Use a shared item_group_id for variants of the same product, with accurate size, color, and other variant attributes.
- Identifiers: submit genuine manufacturer GTINs when available. Your internal SKU is not a substitute for a GTIN.
- Prices: match the feed to the landing page and checkout, including currency and sale prices. Check a configurable product with its advertised option selected.
- Availability: keep the feed aligned with stock and purchasable variants. Review Merchant Center diagnostics after catalog updates.
Agree campaign ownership before launch
Keep your existing agency involved. Agree which products RetailerBoost may advertise and who owns feed changes. RetailerBoost funds and runs its Google Shopping ads; you pay the agreed commission on attributed orders. Feed approval and tracking verification come before launch. Attribution does not prove that an order was an additional sale.





