Why does a published campaign still show an old image after replacement?

Define old and new with visible evidence

Choose a product detail that distinguishes the revisions. In an illustrative tea-tin update, the old front has a circular leaf mark and the new front has a narrow rectangular label. Keep the approved replacement file and a small old-version reference nearby. The filename alone is insufficient if the team reused a name such as hero-final.

Record the placement you are examining: product gallery, collection card, banner or campaign preview. They may have independent image settings even when they describe the same SKU. A correct gallery image cannot establish that the collection card changed. Describe the observed old detail and destination together before deciding where the replacement process stopped.

Follow the replacement chain in order

1. Open the local replacement and confirm the new label is really present.
2. Inspect the uploaded media record in the external publishing tool.
3. Check that the intended page or placement selects that media record.
4. Confirm the edit was saved or published through that tool.
5. Open the actual public placement and compare its visible product edition.

Do these checks sequentially. If the local file is wrong, a browser refresh cannot help. If the media record is correct but the banner still selects another image, waiting for a cache will not fix the reference. Itemlume supplies reviewed creative for download; it does not replace external store media or publish an ad on your behalf.

Separate a stale response from a wrong reference

A difference between browser sessions is a clue, not proof of one particular cache. Keep the destination and account conditions comparable. An editing preview may show an unpublished state while a public visitor sees the saved version. Check the public address directly rather than treating the administration screen as the customer's view.

Use the destination's own troubleshooting

Shopify documents image replacement problems when the new file type differs, and recommends checking the actual uploaded image address.

That is a platform-specific example of inspecting the delivered file. For your destination, follow its current media-replacement guidance and available preview tools. Do not assume that adding an arbitrary query parameter or renaming a file always clears every derived image. A store, an ad platform and a social preview can maintain different publication records.

For the tea tin, note which image address or media entry each affected placement uses, without recording private account tokens. If the correct entry is saved but the old version persists, send the publishing platform a concise report containing the placement, update time and visible mismatch. Generating a third tin image would add another version without identifying the delivery failure.

Confirm the replacement at the customer entry points

Inspect the page's ordinary view and the thumbnail or card through which a buyer reaches it. Change the selected variant where relevant, and check the image at a useful small size. The rectangular label may be correct in a large gallery but disappear in a cropped card. Separate an old-file problem from an accurate file that is poorly framed.

Finish with a destination record naming the new media version, observation time and any unresolved placement. Keep an old image marked retired rather than release-ready. The product-revision replacement plan determines which assets need changing; this check determines whether a specific change reached its audience. An unresolved external publication remains pending even when the replacement is safely stored in My assets.