A product can exist in OpenCart, in a Merchant Center feed and in a GA4 event under three different identifiers. Each individual system may appear to work, while remarketing and reconciliation become difficult because they are describing the same item differently. Start by writing down the identity contract between your catalog, feed and tracking.
Google Marketing Tools includes product-feed and ecommerce-tracking functionality. That gives you a practical place to review both outputs, but you still need to select and verify the identifier strategy that fits your products, variants and advertising destinations.
Distinguish the product from the purchasable variant
A T-shirt page may represent a parent product while “blue, medium” is the item a customer buys. Decide which level each integration exports and records. A parent ID, variant ID, SKU and manufacturer part number are different concepts; similar-looking values do not make them interchangeable.
| Catalog object | Illustrative identifier | Use to investigate |
|---|---|---|
| Parent shirt | TS100 | Product family and storefront page |
| Blue, medium shirt | TS100-BLU-M | Purchasable variant identity |
| Blue, large shirt | TS100-BLU-L | A different stock-keeping item |
These are examples, not a required naming format. Check the destination’s current specification before changing live identifiers. Existing item history and campaign configuration can depend on them, so a migration needs more planning than renaming a spreadsheet column.
Choose a stable identifier and keep a mapping
Select an identifier that will remain stable across feed refreshes and product edits. Product titles, translated descriptions and prices should not change identity. If your internal database ID differs from the external ID, maintain an explicit mapping that your feed and event implementation can use.
For each destination, record the exported item ID, the relevant event parameter and any required prefix or variant convention. Validate against the destination-specific requirements; matching a GA4 item_id alone does not configure every advertising tag. The Merchant Center ID attribute documentation is the reference for Google’s feed identifier.
Compare a feed row with a real browser event
- Choose a product with a simple, known identifier and export or preview its feed row.
- Open that product and inspect its product-view event in GTM Preview or the browser tools.
- Select a variant, add it to the cart and inspect the item identity again.
- Compare the destination feed and the destination’s event parameters character by character.
- Repeat with another language, store and variant type that your installation supports.
Check case, spaces, zero padding and prefixes. Spreadsheet software may silently turn 000123 into 123. Preserve identifiers as text throughout your import and export process. Our CSV import guide covers the same risk at the source.
Check availability and price alongside identity
A matching identifier is necessary for a coherent integration, but it is not the whole feed audit. Open the landing page and compare the advertised variant, current price, currency and availability. Review whether prices include the same tax treatment expected for that destination and market.
Schedule feed generation after a validated supplier update, not while it is halfway through. Otherwise a feed can contain a mixture of old and new stock or prices. Use a named generation workflow and keep enough history to investigate which source was active when an issue appeared.
Plan identifier changes as a migration
Before changing IDs, export the current mapping and record affected destinations. Test a small representative selection in a non-production environment where possible. Confirm that discontinued IDs, replacement rows and parent/variant relationships will be handled deliberately. Avoid changing all identifiers merely to make them look tidier.
If you use Options combinations, include the combination SKU and its stock in that review. A parent product can be available while the exact advertised combination is unavailable. The size-and-color stock checklist gives concrete cases to test.
Keep a small integration reference
Save a few representative feed rows and corresponding event examples with your implementation notes. Include the store, language, destination and variant selections used. That reference makes future import, theme and tracking changes easier to verify without relying on a large catalog export or a campaign report to reveal the mistake later.