The key idea
Names help people recognize an asset; stable identifiers help systems associate it correctly. Keep versions, destinations and usage records together so that creative reuse preserves its source context.
Do not make a filename carry every association
Files get renamed, translated and compressed. Two files with the same name can contain different edits. Using the filename as the only identifier makes handovers and repeated uploads harder to reconcile.
Keep the stable asset identifier alongside a readable name, source and intended use. When a name changes, retain the relationship between the old and new names so existing reports remain understandable.
Choose a small set of useful naming fields
A naming convention should help the team find a version quickly. Brand, market, language, creative concept and version are useful starting points; choose their order based on how the team actually searches. A filename does not need to hold every business field.
For example, brand_us_en_demo_v03 illustrates five separate fields. It is an organizational example, not an instruction to rename an approved campaign, and it does not replace a stable asset identifier.
- Agree on language and market abbreviations in a shared glossary.
- Give version changes a clear meaning, such as a revised caption or end card.
- Define when assets are archived so outdated versions do not enter new work.
Review destinations and tracking when reusing assets
Reusing a video does not automatically justify reusing its previous destination. The creative, page language and promoted object should agree. If a business association is unclear, inspect the source record before continuing.
UTM parameters can describe traffic source, medium and campaign. Define the purpose and owner of each field, then check copied links for values that no longer apply. The Google Analytics reference below explains manual tagging and its relationship with automatic tagging.
Connect each use to an ad object
For each use, retain the asset identifier, version, destination, target account and resulting ad object. When an ad needs investigation, that record leads back to the actual file and its publishing context instead of forcing a guess from a thumbnail.
Separate the same asset from the same test conditions. Even an identical file can appear with different copy, markets, time ranges or landing pages. Preserving that context is more useful than treating all spend against a filename as one comparable test.
- An ad object can be traced to the version used at publication.
- The association between an asset and its destination is explainable.
- Outstanding task references are checked before deletion or archiving.
Frequently asked questions
Can one file be reused in multiple markets?
Check language, content, usage permission and destination suitability for each market, and keep the context of each use.
Should asset renaming change historical campaign names?
Do not overwrite an approved historical campaign name just to make names match. Preserve identifiers and name mappings to maintain traceability.