Skip to content
Ad operations

Campaign naming conventions that survive a real ad-ops workflow

A naming convention rarely fails because it was badly designed. It fails on the third person who types a name by hand, on a date written three ways, on a stray space nobody saw. Here is a field order that nests from campaign to creative file, the separator, case and UTM rules that keep reports clean, and how to keep a whole team on one pattern.

18 November 2026 10 min read Examples run through our Campaign Name Generator

1. Where names break

A campaign name has two readers. A person scanning a trafficking sheet needs to know what a line is. A spreadsheet, a pivot table or a reporting connector needs to split the name back into fields — brand, campaign, audience, size — so spend and results can be grouped. Most conventions are written for the first reader and broken by the second. The failures are almost always the same six:

  1. Spaces. “Winter Sale” looks fine on screen. In a URL it has to be encoded, in a file name it trips up scripts, and once a tool swaps spaces for the separator it becomes two fields.
  2. Case drift. Acme, acme and ACME are the same brand to a person and three different values to a report.
  3. Free text. One planner writes Retargeting, another Remarketing, a third RT. Each is reasonable; together they split one audience into three rows.
  4. Dates in several formats. 01/12/26, 1-Dec and Dec2026 do not sort, and 01/12 is a different day in Delhi and in New York.
  5. Names that are too long. Platforms and reports cut long names off in table columns and dropdowns. The cut falls at the end, which is where size and version usually sit.
  6. The separator inside a value. If the separator is a hyphen and a campaign is called Back-to-School, no formula can tell where the campaign field ends.

None of these is a design problem. They are input problems, and that decides the fix: fewer places where anyone types a name freehand.

2. One pattern, three levels

Ad platforms nest things — a campaign holds lines or ad sets, and those hold creatives. Exports flatten that nesting. A row in a CSV, a file in a downloads folder or a line in an analytics report arrives with no parent attached. So each level should carry enough of its parent's name to be identified on its own, and the shared part should come first so that sorting groups related rows together.

A field order that nests. Each level starts with the same prefix, broad fields first and the fields that change most often last.
LevelFields, in orderExample
CampaignBrand · Campaign · Geo · Start dateAcme_WinterSale_IN_20261201
Line / ad setBrand · Campaign · Geo · Channel · Audience · PlacementAcme_WinterSale_IN_Display_Prospecting_GDN
Creative / fileBrand · Campaign · Size · VersionAcme_WinterSale_300x250_v02

A few decisions are packed into that table:

  • Broad to narrow. Sort a list of these names alphabetically and they group by brand, then campaign, then everything below it. That is the order people look for things in.
  • The date sits on the campaign only. Every line under a campaign shares its start date, so repeating it lower down adds length without adding information.
  • Version goes last. It changes most often, and putting it last keeps v01 and v02 of the same file next to each other in any sorted list.
  • Every field has a fixed position. A field that is not needed for a name is left out entirely. It is never replaced with a placeholder like NA that then has to be filtered out of every report.

3. Separator and case

The separator divides the fields. The only hard rule is that it must never appear inside a value, and the choice of character follows from that. Here is the same creative name with each separator our generator offers:

Brand Acme, campaign WinterSale, size 300x250, version v02 — output from the generator with each separator.
SeparatorResultVerdict
Underscore _Acme_WinterSale_300x250_v02Default Safe in file names and URLs, and rarely typed inside a value.
Hyphen -Acme-WinterSale-300x250-v02Workable Fine in URLs, but people type hyphens inside values (Back-to-School, dates).
Dot .Acme.WinterSale.300x250.v02Avoid for files Collides with the dot before the file extension.
NoneAcmeWinterSale300x250v02Avoid Readable, but no formula can split it back into fields.

Case is the second decision, and the generator's four options show why it needs one:

The same inputs with each case option, as the generator outputs them.
CaseResultUse it for
As-isAcme_WinterSale_300x250_v02Platform and file names, with values kept in CamelCase in your list.
loweracme_wintersale_300x250_v02UTM values, and any system where case is unreliable.
UPPERACME_WINTERSALE_300X250_V02Rarely. The size becomes 300X250, which some sheets will not match against 300x250.
TitleAcme_Wintersale_300x250_V02Rarely. It capitalises the first letter of each word and lowers the rest, so CamelCase is lost.

The practical rule: keep values in CamelCase and use As-is for anything a person reads, and use lowercase for anything that goes into a URL. Choose once per surface and write the choice down.

4. Values come from a list

Fields and separators are the easy part. Most drift comes from the values typed into them. The fix is a short list of allowed values per field — brands, campaign codes, channels, audiences, geos — each written as a single token in its final form. The left column below is what turns up in real sheets. The right column is what belongs in the list.

Do and don't for field values. The “what happens” column is what our generator outputs from the left-hand value with an underscore separator.
Don'tDoWhat happens otherwise
Acme ShoesAcmeShoesThe space becomes the separator: Acme_Shoes reads as two fields.
2026-12-01, 01/12/2620261201The hyphens become separators: 2026_12_01. YYYYMMDD sorts by date as plain text.
300×250300x250The × sign is not a letter: 300_250.
Acme, acme, ACMEAcmeThree rows in any case-sensitive report.
v1, v2 … v10v01, v02 … v10Unpadded, v10 sorts before v2.
Retargeting / RT / RemarketingRetargetingOne audience reported as three.
दिवालीDiwaliNon-Latin characters are removed, so the whole field disappears from the name.
Final, New, Latestv03Words that stop being true the next time the file changes.
The rule behind the table

Cleaning can make a value safe. It cannot make it right. A tool that strips spaces will turn “Acme Shoes” into something that works in a URL, but only a list can say that the brand is spelt AcmeShoes and nothing else.

5. Creative file names

Creative files travel further than any campaign name. They are emailed, zipped, uploaded to ad servers and re-downloaded months later for a resize. The file name is often the only label that survives the trip, so it should carry what a trafficker needs to place it:

// brand _ campaign _ size _ version . extension
Acme_WinterSale_300x250_v02.zip
Acme_WinterSale_728x90_v02.zip
Acme_WinterSale_1080x1920_v01.mp4

// a creative variant is not a revision — give it its own code
Acme_WinterSale_300x250_PriceLed_v01.zip
Acme_WinterSale_300x250_GiftLed_v01.zip

Size as pixels with a lowercase x. Variant before version, so a new idea and a corrected file can never be mistaken for each other.

  • Size in pixels, not placement names. On social, several named placements share one set of pixels, so 1080x1920 is more precise than “Story”. The display side of the same question is in banner sizes that actually get trafficked.
  • Variant and version are different fields. A version is the same creative corrected. A variant is a different creative being tested. Mix them in one number and nobody can tell which v03 was the price-led one.
  • Rename the file and its contents together. An HTML5 ZIP references its own images and scripts by file name. Renaming the assets inside without updating those references breaks the ad.

For dynamic creative, where components are assembled at serve time, naming also has to cover the components themselves. Our DCO production guide has a short section on that asset taxonomy. This page deals with the campaign and file layer around it.

6. UTM values

UTM parameters are where naming problems become reporting problems. Each value becomes a dimension in analytics, and GA4 treats these values as case-sensitive. These are the five classic parameters and what GA4 does with each:

The five classic UTM parameters with their standard GA4 meaning, and a value that follows the convention above.
ParameterWhat it identifiesExample value
utm_sourceWhere the visit came from: the site, platform or newsletter.google
utm_mediumThe type of traffic: paid search, display, email.display
utm_campaignThe campaign the link belongs to.acme_wintersale_in_20261201
utm_contentWhich ad or link, when several point to the same page.300x250_v02
utm_termThe paid search keyword. Leave it out elsewhere.—
https://example.com/winter-sale
  ?utm_source=google
  &utm_medium=display
  &utm_campaign=acme_wintersale_in_20261201
  &utm_content=300x250_v02

Split across lines for reading. In use it is one unbroken URL.

  • Lowercase, always. Facebook and facebook arrive as two rows in the same report. Lowercase removes that whole class of error.
  • No spaces, no symbols. Letters, digits, underscores and hyphens need no encoding in a URL and look the same in every tool that shows them.
  • utm_campaign is the campaign name, lowercased. Same fields, same order. Then the ad platform's report and the analytics report can be matched on one column.
  • utm_medium comes from a short fixed list. GA4's default channel grouping reads it to decide which channel a visit belongs to. A made-up medium such as winter-push can end up under Unassigned.
  • utm_content carries the creative. The size and version from the file name are enough to trace a click back to the file that earned it.

7. Length and truncation

Every field you add makes the name longer, and long names get cut off — in platform tables, in dropdowns, in the narrow first column of an exported report. A cut name is worse than a short one, because the end it loses is usually the size or version that tells two rows apart.

  • Use codes in the list, not phrases. IN, not India. Prospecting is fine. ProspectingLookalikeOnePercent belongs in the platform's targeting settings, not in the name.
  • Don't repeat what the platform already records. If the platform already files every line under its advertiser, the advertiser field inside that platform adds length and nothing else. Keep it on files and links, which travel without that context.
  • Drop fields per level. That is what the three-level table is for. A creative file does not need the audience, and a campaign does not need the size.
  • Check the longest name, not a typical one. The largest combination of the longest values is the one that will be cut off.

8. What the generator does with all this

Our free Campaign Name Generator builds names from a convention rather than from free typing. Here is what it does, based on the code that runs it:

  • Ten fields. Advertiser, Brand, Campaign, Channel, Audience, Placement, Size / Format, Geo / Language, Date and Version. You switch each one on or off and change the order with up and down arrows. A fresh start has Brand, Campaign, Size and Version on, with an underscore and as-is case.
  • Four presets. CM360, DV360, Meta / Social and Simple each set a field order, separator and case in one click. They are starting points to adjust, not the platforms' own required formats.
  • Separator and case. Underscore, hyphen, dot or none, and As-is, lower, UPPER or Title — the options in the tables above.
  • Cleaning. Case is applied first. Then every run of characters other than A–Z, a–z and 0–9 becomes one separator, and separators left at either end of a value are trimmed. Every example in section 4 is real output from that rule.
  • Every combination at once. Type several values in a field, separated by commas or on new lines, and it builds every combination. Identical names are removed and the count is shown. A field left empty is left out of the name, with no double separator. An empty Date field fills in today's date as YYYYMMDD.
  • Copy or export. Copy one name or all of them. The CSV has a column for each field plus the finished name.
  • Save the convention. Fields, order, separator, case and the values you typed are saved in your browser and load automatically next time. An option saved with it names the files other studio tools export — banner sizes, HTML5 ZIPs, video formats — with the same convention.
  • Rename files to match. “Rename files with these” sends the names to the Rename files tab, where the files you add are renamed in that order. For an HTML5 ZIP, references inside its HTML, CSS, JS, JSON, SVG and XML files are updated to the new file names.

The worked example: Brand Acme, Campaign WinterSale, two audiences, two placements, three sizes and one version give twelve names:

// Audience: Prospecting, Retargeting   Placement: GDN, DV360
// Size: 300x250, 728x90, 160x600       Version: v01
Acme_WinterSale_Prospecting_GDN_300x250_v01
Acme_WinterSale_Prospecting_GDN_728x90_v01
Acme_WinterSale_Prospecting_GDN_160x600_v01
Acme_WinterSale_Prospecting_DV360_300x250_v01
…
Acme_WinterSale_Retargeting_DV360_160x600_v01   // 12 names

Very large runs are capped at the first 2,000 combinations, with a note saying how many were possible.

What it does not do

It does not check a value against your list. It will clean “Remarketing” just as happily as “Retargeting”. It does not shorten long names. It builds the values you put into UTM parameters but not the tracking URL itself. And the saved convention lives in one browser on one device, so it is not a shared team setting. The list in the next section is still the source of truth. The generator is how you apply it without retyping.

The generator runs in your browser, and the names you type are not uploaded.

9. Keeping a team on one pattern

A convention lasts as long as the habits around it. These are the ones that matter:

  1. One sheet, one tab per field. Each tab lists the allowed values for that field in their final form, with a column for what each one means. The convention itself — field order per level, separator, case — goes on the first tab, with the date it last changed.
  2. One owner. Usually the ad-ops lead. Anyone can ask for a new value. Only the owner adds it, so Retargeting never gets a twin.
  3. Put it in the brief. The campaign code and the size list belong in the production brief, so design, build and trafficking all start from the same values.
  4. Generate, then paste. Names are built from the list and pasted into platforms and file names, never retyped. Retyping is where case drift and stray spaces come back in.
  5. Change the convention for new campaigns only. Renaming a live campaign or changing its utm_campaign mid-flight splits its history into two rows. Version the convention and apply the new version from the next launch.
  6. Audit once a month. Export the active names, split them on the separator and look for rows with the wrong number of fields or a value that is not on the list. Every one of them was typed by hand.

10. The checklist

  • Field order written down for campaign, line and creative, sharing one prefix.
  • One separator, and it never appears inside a value.
  • One case rule per surface: CamelCase as-is for names, lowercase for UTM.
  • Every value comes from a list, as a single token with no spaces.
  • Dates as YYYYMMDD. Versions zero-padded. Sizes with a lowercase x.
  • Variant and version kept as separate fields.
  • No placeholders for missing fields. The field is simply left out.
  • utm_campaign matches the campaign name, lowercased. utm_medium comes from a fixed list.
  • The longest possible name checked in the narrowest place it will appear.
  • One owner for the list, and a monthly audit of live names.
Build the names, don't type them

One convention, every combination, ready to paste.

Set the fields, order, separator and case once. Type your values and copy every name the set needs. Building and copying are free with no signup, and the CSV needs a free account.

Open the name generator

Frequently asked questions

What is a campaign naming convention?
It is an agreed pattern for every name your team types into an ad platform, an ad server, a file system and a tracking link: which fields appear, in what order, joined by which separator, in which case, and which values each field may hold. The point is that a name can be read by a person and split back into its fields by a spreadsheet, so reports group correctly without anyone cleaning them by hand.
Which separator should I use in campaign names?
Pick one and use it everywhere. The underscore is the common choice for campaign, line and creative names because it is safe in file names and URLs and rarely appears inside the values themselves. The rule that matters more than the character: the separator must never appear inside a value. If a campaign is called “Winter Sale” and your separator is an underscore, write it as WinterSale, or it will read as two fields.
Should UTM parameters be lowercase?
Yes. GA4 treats UTM values as case-sensitive, so Facebook and facebook arrive as two separate rows in the same report. Lowercase everything, use no spaces, and keep to letters, digits, underscores and hyphens. Keep utm_medium to a short fixed list, because GA4's default channel grouping reads it to decide which channel a visit belongs to.
How should I name ad creative files?
Brand, campaign, size and version, in that order: Acme_WinterSale_300x250_v02. Use a plain lowercase x in the size, never the × sign, and pad the version (v01, v02) so that v10 sorts after v09. If you run creative variants as well as revisions, give the variant its own short code before the version, so a new idea and a corrected file are never confused.
What does the Campaign Name Generator do with spaces and symbols?
It keeps only letters A–Z and a–z, digits and your chosen separator. Any run of other characters — a space, punctuation, a symbol — becomes one separator, and separators left at the start or end of a value are trimmed. So Winter Sale!! (Final) becomes Winter_Sale_Final. Characters outside that set, including non-Latin scripts, are removed, so type values in plain Latin letters.
Is the Campaign Name Generator free?
Yes. Building names, previewing every combination and copying them — one at a time or all at once — are free with no signup. Downloading the names as a CSV needs a free account, with no daily limit. Nothing in the generator needs PRO, and it runs in your browser, so the names you type are not uploaded.

One convention. Every name, every file.

Build campaign, line and creative names from one pattern in your browser, then rename the files to match without breaking the ads inside them.