If a catalog ad shows the wrong item, do not start by rewriting ad copy. Follow the item from the store catalog through the feed, product set, ad and landing page. A mismatch can come from an identifier, stale update, eligibility rule or product-set selection.
Trace one affected item
Record its store SKU or stable ID, feed ID, title, image, variant, price, availability and landing URL. Compare the record shown in Commerce Manager with the live product page. Do this for one affected item and one healthy control item so a broad claim of a broken feed becomes a testable difference.
Check selection and eligibility
Inspect whether the ad is drawing from the intended catalog and product set. Look for rejected items, missing images, outdated availability, variant confusion and a page that resolves to the wrong selection. Fix the source feed or integration first; repeatedly resubmitting an incorrect record does not make it accurate.
Validate after correction
Wait for the catalog update to process, then inspect the affected item and preview the ad where available. Record old and new states and confirm the landing page on a phone. Use purchase data only after the correct products are eligible and the event signal is trustworthy. A catalog diagnosis and a creative test answer different questions.
Worked decision example
Illustrative case: a red bag ad opens a black bag product URL because both variants share one generic link in the feed. Correct the variant-to-URL mapping, verify the selected option and price on the landing page, then recheck product eligibility. This is an example workflow, not a documented Megvi result.
Practical review checklist
- Do feed ID and store SKU identify the same item?
- Does the ad use the intended product set?
- Does the landing page show the advertised variant?
Where to go next
Meta Ads service · creative testing guide · Flower Center case