Email campaign naming conventions should help the next person choose the right file or campaign without guessing. “Final,” “new final,” and “final approved” hide the actual difference between versions. Use a short pattern with the details that matter to your team, such as purpose and language, while keeping the evidence of approval separate from the name itself.
Include the details that help selection
Choose a consistent pattern for campaign purpose, date or period, audience, and language where relevant. Keep names readable rather than packing in every possible field. A colleague should understand the difference between two versions without opening both.
Use Sendvio campaign and template names consistently with the surrounding asset library. Avoid personal customer information in filenames, discount prefixes, or internal labels that might later appear in exports or shared screenshots.
Choose a pattern people can read without a key
A practical internal name could be “2026-11 | Restock | Linen shirt | Requested alerts | EN | v03.” The exact separators do not matter as much as consistent order and useful distinctions. Include the fields your team actually needs to choose the right item; omit those that add length without helping selection.
If several language versions live within one campaign, keep the campaign identity stable and distinguish the individual assets where needed. Do not create unrelated names that make the versions look like separate offers. The team should be able to trace an image, template, and language review back to the same campaign brief.
Use dates consistently and clarify whether they mean planned send date, creation date, or campaign period. Changing meanings between folders makes sorting unreliable. Keep customer names, phone numbers, and private details out of labels that may later appear in screenshots or exports.
Keep status separate from guesswork
Define what draft, reviewed, scheduled, and active mean in your workflow. Identify the owner responsible for approval. A file called “approved” is not enough if nobody knows which version was reviewed or what changed afterward.
When an asset is replaced, make the current choice clear and preserve history according to your normal process. Do not let an old image with an expired offer remain the easiest item to find.
Keep approval evidence separate from the label
A file named “approved” may have changed after review, and a campaign named “draft” may already be scheduled. Check the actual system state and retain a record of which version was approved. Naming helps navigation; it does not enforce the workflow by itself.
When a material change creates a new version, explain what changed and which checks need repeating. A new image crop may require a visual review, while a changed discount needs an offer test. Avoid copying an old approval note onto a revised package without checking its scope.
Make the current choice easy to find and distinguish retired assets from active ones. Preserve history according to the team's normal process, but do not leave an expired promotion beside the current asset with an equally plausible name. A clear archive decision reduces the chance of a rushed teammate choosing the wrong file.
Review the package before sending
Check that the campaign uses the intended image, template, language version, and destination. Naming reduces mistakes but does not replace the final preview. A correctly named file can still contain the wrong price.
Periodically archive or retire unused drafts so the working library remains manageable. The best system is small enough that people keep using it. Its value appears when a colleague can prepare a campaign confidently without relying on the original creator's memory.
Test the convention by asking someone unfamiliar with the campaign to locate the final template, intended language assets, and approval record. If they need the original creator to explain the names, simplify the system. The best convention is the one the whole team can use consistently during ordinary work and a busy launch.