“New campaign final 2” makes sense to somebody for a short time. Six months later, it tells the next analyst very little.
A campaign name is a small piece of shared documentation. It appears in reports, exports and conversations that may outlive the project team. A readable convention can save repeated detective work without turning each name into a complicated code.
Choose a few durable dimensions
Include the attributes people regularly need to distinguish. Purpose, market, product group and phase are common candidates. Use the business's actual reporting needs rather than every setting available in the account.
For an illustrative workshop launch, a name such as workshops | north | autumn-intake | enquiry gives a colleague a useful starting point. The precise separator matters less than consistent meaning.
Avoid a name that includes a value likely to change every few days. If the campaign budget changes, its historical purpose should not become impossible to recognise. Put changeable settings in the appropriate report or working record.
Publish the vocabulary beside the convention
Short labels need shared definitions. Does “north” mean a service region, an internal sales territory or a group of locations selected for this launch? What separates an introductory phase from an ongoing one?
Keep a compact reference with examples and the person responsible for maintaining it. If two teams use different labels for the same product group, settle the mapping before combining their reports.
The convention should be easy enough for someone preparing a campaign under time pressure. A long sequence of unexplained abbreviations invites inconsistency.
Keep customer information out of names and links
Campaign identifiers describe the marketing activity, not the individual receiving it. Do not insert email addresses, names or other personal details into campaign labels or tracking parameters.
Review generated links as well as the account screen. A name copied into a shared URL can travel further than the original internal report.
Rename with a record of the change
If an inherited convention needs improvement, retain a mapping between old and new labels and record when the change occurred. Otherwise, a report can make a renamed activity look like a newly launched one.
Good names do not replace campaign documentation. They provide a reliable handle for finding it. The useful test is whether a colleague can identify the activity's purpose later without having attended the meeting where it was created.
A thought worth keeping?
