Skip to main content
A naming convention gives every campaign, ad set, and ad a predictable, structured name. Consistent names let you filter and group performance data in a report, compare campaigns across channels, and keep an ad account readable as the number of campaigns grows. It covers every channel you run: Google, Meta, Pinterest, Display, SMS, email, and anything you add later. This document explains the thinking behind the framework and previews what each level covers.

What a naming convention does for you

  • Creates a manageable ad environment. Anyone on the team can scan a name and understand what’s running.
  • Supports analysis. Consistent identifiers let you filter and compare ads by the variables that actually matter: offer, creative type, customer profile, funnel stage, and so on.

How a name is built

Every name in this framework is built from two kinds of identifiers. Standard identifiers describe the permanent facts about a campaign, ad set, or ad: its channel, objective, customer profile, offer, and so on. Every campaign, ad set, and ad carries its full set of standard identifiers, in the same order, every time. Testing identifiers describe a hypothesis you’re currently running, for example a creative format test. They’re optional, and only appended to the ads that are part of that test, for as long as the test runs.

Delimiter, case, and missing values

Every level joins its values with the same delimiter. The default is a hyphen with no spaces, and a value keeps the exact casing its dictionary row records. Never use the delimiter inside a value; register a short form instead, so a report can split any name back into its fields. Record a different separator or casing once, wherever your team keeps its naming rules, and apply it at every level. Every short form is unique across all the dictionaries, not only within its own table. CA can mean Canada in the geo table or something else in another table, never both, because a report filtering for CA cannot tell which field it came from. Geo and language codes are the most common collision, so no other category may use a two-letter country or language code. Some categories hold a pattern rather than a fixed list. A percent-off offer is OFFXX, where XX is the number: a 34 percent sale is OFF34, with nothing to register first, because the pattern is the registered value. Use a pattern wherever a category carries a number (a discount, a lookalike size, a day count) so a dictionary records the rule once instead of every amount you might ever run. When a name needs a value the dictionary doesn’t hold yet, such as a new product short form, ad type, or CTA, register it in that category’s table first, then use it. Don’t type a one-off value straight into a platform. The same rule applies to any tool or AI assistant assembling names from these conventions: a value missing from your filled-in dictionary is a question for the team, not something to invent. Ask, then record the answer in the table.

What each level covers

Campaign

Channel, marketing campaign name, placement type, objective, budget type, bid type, product, and funnel position. These describe a campaign’s strategy: which platform it runs on, which initiative and product it belongs to, what it’s optimizing for, and where it sits in the funnel. Not every channel or campaign uses every category; a Google Search campaign leans on bid type, while a Meta campaign with budget optimization turned on leans on budget type instead, and an always-on brand campaign has neither a marketing campaign nor a product to name. If the campaign is part of an active test, append the testing identifier here too. See Campaign naming conventions. The product identifier comes from your product pages, which hold the list of valid values. The naming page is where a value becomes part of a name.

Ad set / ad group / variant

These fields describe who the ads reach and where the customer profile came from. Include date, customer profile type, customer profile seed, geo, language, and device. For accounts that use list-based targeting, segment-based targeting, or separate email and SMS sends, include list or segment type as well. If the set / ad group / variant is part of an active test, append the testing identifier here to. See Ad set / ad group / variant naming conventions. These fields describe the creative itself: what it looks like, what it offers, and where it sends someone. Include creative name, ad type, offer, CTA, and destination. For channels with fixed creative dimensions, mainly display, include the ad format or size as well. If the ad is part of an active test, append the testing identifier here too. See Ad naming conventions.

Name jamming (short identifiers)

Name jamming means packing as many identifiers as possible into a name using their short form. For example:
instead of:
Name jamming keeps names short enough for automated reporting and platform character limits, at the cost of being harder for a person to read at a glance. Some teams name-jam everything; others only jam the fields that push a name past a platform’s limit. Both work as long as the choice is applied the same way everywhere, or both names are accounted for in filters and analytics. If you name-jam any identifier, log its short form next to the long form in that category’s table, in the relevant SOP. That way anyone on the team can look up what a short code means, and reporting can map short and long forms back to each other.
Never rename or remove an identifier once it’s used in a live or historical campaign. Add new identifiers to the list instead. Renaming fragments your data, since reporting can no longer group the old and new names together. Removing loses the record entirely.
Campaign naming conventions Fill in this level’s categories and build its dictionary. Ad set / ad group / variant naming conventions Fill in this level’s categories and build its dictionary. Ad naming conventions Fill in this level’s categories, including testing identifiers, and build its dictionary. Experiment ID concepts How a hypothesis becomes a short experiment ID
Type: standard
Domains: naming, tracking
Provides: naming-rules, concept:naming-convention
Uses: concept:experiment-id, naming-convention, naming-dictionary, product-catalog

Get the complete Marketing OS

Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.

Have us run it for you

We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.
Last modified on October 30, 2026