
Changing Cloudinary campaign tags does not create a new file-backup version. The backup documentation says metadata or tag changes alone do not trigger a backup. Keep an explicit classification-change record when you need to explain who approved a media-library state or recover an earlier campaign assignment.
Key Takeaways
- File revision history and classification history answer different questions.
- A tag-only edit does not create the documented file-backup checkpoint.
- Retaining the image does not document every approval decision attached to it.
Name the state you need to recover
Cloudinary's backup reference distinguishes replacement with a new file version from metadata-only changes. It explicitly states that changes to metadata or tags alone do not trigger a backup.
The custom-metadata documentation describes tags, contextual fields and structured metadata as asset records used for searching or application behavior. A campaign change can therefore affect what an integration selects even when the photograph's pixels remain identical.
Do not infer how a restore handles every historical metadata field from the existence of an image backup. That field-level restore behavior requires its own evidence.
Keep a classification-change receipt
- Identify the asset and the campaign or approval field being changed.
- Record the previous value, proposed value and reason in an appropriate private project ledger.
- Note the person or process responsible for the decision.
- Apply the authorized change through the library's supported workflow.
- Read the resulting field and inspect the receiving selection.
- Keep the confirmed value with its time and source-asset identity.
This is a suggested editorial record, not a claim that the provider automatically creates that ledger or that a spreadsheet constitutes a complete security audit.
A hypothetical campaign reassignment
A team changes a portrait from campaign-A to campaign-B without uploading new pixels. Later, another editor wants to know whether that reassignment was approved.
The file's available image versions do not establish that a new backup checkpoint was created for the tag edit. The proposed ledger supplies the missing decision context, while the library shows the currently stored classification.
If the wrong field value is identified, correct only the authorized affected record or reviewed set. Do not restore or re-upload the image merely to manufacture a history entry; that changes another part of the asset lifecycle.
Separate conflict resolution from history capture
The catalog-versus-file metadata guide addresses choosing between competing existing records. This task concerns preserving evidence of a database classification decision before that history is needed.
Accept when the current classification is correct, the receiving workflow selects the intended assets and the approval trail says what was actually recorded. If a provider audit-log feature is required, confirm its documented plan and event coverage separately. No tag change, restore operation or audit-log test is claimed.
Related tasks
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
- How Do I Keep AI Product Images Matched to the Correct SKU?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Cloudinary: Backups and version management: New-upload versus existing-asset backup setup, job scope and original-only coverage; tag-only changes do not create a backup; own-storage availability, migration guidance and restrictions on managed backup objects and policies.
- Cloudinary: Custom metadata: Tags and contextual values are unvalidated text; structured fields have global definitions, types and optional validation; field-definition and asset-value permissions differ.
Documentation-based editorial synthesis with AI-assisted research and drafting. Scenarios, ledgers and acceptance checks are hypothetical or proposed. No hands-on test, account change, measured demand, AI-citation rate, benchmark or client acceptance is claimed. Availability and plan limits remain within each cited source's scope.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.