Codes in use
PS / Li / NA / RL / SD / PL / Q2
The abbreviation dictionary keeps a short campaign name readable to the people governing it.
live // transparent output
Campaign Name Generator
Generate canonical campaign names that hold up across paid media, reporting, spreadsheet workflows, and cross-platform operations.
Taxonomy rules shell
Turn naming discipline into a repeatable generator instead of a style guide nobody follows.
The real workflow here is defining a ruleset that can survive paid media, spreadsheet operations, handoffs, and reporting joins. The tool should make canonical naming visible before anyone exports a single row.
Ruleset review
Lock the required tokens and delimiters before the company improvises
Advanced dictionary
Define up to 15 readable values and unique abbreviations
Codes are matched without regard to capitalization. No two values may use the same abbreviation.
Name or value Abbreviation Action
Pre-export checks
- Required tokens are present for the canonical name.
- Every selected value resolves to a short code.
- Every abbreviation is unique.
- The canonical name is readable enough for platform and spreadsheet use.
token generated code role
channel
PS
canonical anchor
source
Li
attribution clue
geo
NA
reporting segment
audience
RL
target grouping
offer
SD
launch token
objective
PL
decision target
date
Q2
time anchor
Generated output
Return a short canonical name and the dictionary that makes it readable
Canonical output
The primary name should survive dashboards, joins, and spreadsheet review without cleanup.
PS_Li_NA_RL_SD_PL_Q2
Rules posture
Ready for worksheet exports and governance rollout
Use the same naming logic across templates, bulk spreadsheets, and campaign QA instead of relying on memory.
Length check
68 characters
Keep an eye on readability so long campaign strings do not become the next reporting problem.
What the generator does
Campaign names are often treated like labels, but they affect reporting joins, dashboard readability, QA effort, and downstream operations. The generator converts selected values into short, unique codes and combines them into one canonical name without losing the dictionary needed to read it later.
R. Garcia’s recommendation: Include the source in the campaign name. I have seen the
utm_campaignvalue survive while source or medium information was stripped somewhere in the journey. A short source code inside the canonical name preserves one more useful clue without making the name unwieldy.
Decide the pattern first
Choose a stable order for channel, market, audience, offer, date, and objective. Not every organization needs every token. The useful pattern is the shortest one that remains unique, readable, and enforceable.
Before adopting a generated name, confirm:
- which tokens are required
- which abbreviations are approved
- whether every abbreviation is unique across the dictionary
- whether values may contain the delimiter
- how legacy campaigns and exceptions will be handled
- which platforms require shorter variants
Review before publishing
The generator cannot know whether a token is meaningful to your reporting model. Treat its output as a structured draft, then test the pattern against real campaigns before making it mandatory.
Use the campaign naming worksheet to document the approved pattern and the campaign taxonomy hub for rollout guidance.
What this connects to
Turn the output into a rule your team can repeat.
Use the related hub, implementation notes, and templates to document the decisions behind the generated output.
Topic hubs