What an item ID does
Every row in a product feed needs a value that belongs to that row and to nothing else. That value is the item ID. Google uses it as the key for the product: it decides which row is being updated on the next fetch, which product an ad is promoting, which line in the reporting belongs to which item, and which product a visitor looked at when a remarketing tag fires.
The value itself is arbitrary. Shops usually send the SKU, the database record number or the platform’s internal product reference. What matters is that it is unique inside the feed, that it stays exactly the same from one upload to the next, and that the same value is sent by every system that talks about the product — the feed, the tag on the product page, and the catalogue used for dynamic ads. Variants are separate products in Google’s eyes, so each colour and size combination carries its own ID.
Why the item ID matters
All of a product’s history hangs on this one field. Clicks, conversions, learning inside automated bidding and the eligibility a product has built up are attached to the ID, not to the title or the URL. Keep the ID and you keep the record. Change it and Google sees a brand new product with no past, which usually means a quiet dip in performance while the item earns its place again.
It is also the join between systems. If the ID in your feed and the ID sent by your remarketing tag differ by so much as a prefix or a change of letter case, dynamic remarketing has nothing to match and the visitor sees generic ads instead of the product they viewed.
Where item IDs go wrong
Migrations cause the most damage. Moving to a new shop platform typically regenerates every internal reference, so the feed arrives with a full set of new IDs and every product starts again from nothing. Re-using an old ID for a different product is the mirror image of that problem: the new item inherits history that does not describe it.
Smaller faults are common too. Duplicate IDs make Google drop or overwrite rows unpredictably. Trailing spaces, inconsistent capitalisation, and IDs built from the title or price mean the value changes whenever the product does. Characters that a spreadsheet reinterprets, or an ID long enough to be truncated, produce the same result.
How to get it right
Pick a value that has no reason to change, ideally the same stock keeping unit your warehouse already uses, and treat it as permanent. Write the mapping down so whoever rebuilds the export later knows the IDs must be preserved.
Before a replatform, export the current feed and plan how each old ID will carry across; if some genuinely cannot, expect the affected items to relearn and stagger the change rather than doing it at your busiest time. Check that the tag on your product pages sends the identical string, and confirm it in the product report of your Shopping campaigns, where an ID that never appears is usually one that never matched.
