Should repeated campaign banners link to one product file or embed separate copies?

Work through the cause

1. List which banners must update together and which are already frozen for a campaign. Keep those groups separate.
2. Test a reversible source change in copies of the working files. Confirm which placements respond and which remain independent.
3. Before delivery, save the approved state and record its source version. Check external dependencies for the recipient.

A concrete case (illustrative)

Illustrative case: three working launch banners should share the same updated bottle photograph, while last month’s approved ad must remain unchanged. Link the active work deliberately and keep the archived delivery as a controlled snapshot.

Acceptance and next action

Pass when update behavior matches the campaign’s intended scope. A shared file can propagate a mistake as efficiently as a correction. Review all affected layouts after replacing a common product source, including layouts that were not open during the change.

Take this question’s manual review card

The worksheet contains this question’s steps and acceptance condition. Fill in your actual source, observations and decision; blank fields do not mean approval. It does not connect to a store, modify files or automatically approve a result.

Download this review card (CSV)

Source scope: the linked documentation explains relevant tool behavior or technical context. The merchant scenario, review choices and acceptance condition are CartVisual editorial guidance; citation does not imply endorsement.