What is Naming convention?

A naming convention is the agreed pattern for naming campaigns, ad groups or ad sets, and ads.

It is usually filed under tidiness, which undersells it. Names are queryable. Anything encoded in a name can be filtered, grouped and reported on, which means the convention decides what dimensions an account can analyse without changing its structure.

That is more consequential than it used to be. Under automated bidding, splitting a campaign to see its numbers separately costs real performance, because conversion data divides and the models get less to learn from. A convention that carries the dimensions in the name lets an account stay consolidated and still produce the segmented view somebody asked for.

Naming is the cheap substitute for structural fragmentation, and it is the one that does not cost delivery.

The dimensions the account actually reports on, in a fixed order, separated consistently.

A common and serviceable shape runs from broadest to narrowest:

Market or region, where the account spans more than one.

Funnel stage — prospecting, retargeting, retention, brand.

Objective or optimisation event, where it varies.

Audience or theme, naming what the container is about.

Offer or promotion, where one applies.

Period or version, usually a quarter or a month.

Two rules make the whole thing work.

Fixed order. Names that sort alphabetically into a sensible hierarchy are worth more than names that read well, because sorting is how anybody navigates a long list.

Fixed separators and case. One separator, used consistently, and a single case. Reporting tools treat differing capitalisation as different values, so one theme spelled three ways becomes three rows to be summed by hand forever.

Anything the platform already reports as a field. Objective, budget, bid strategy and status are columns. Duplicating them makes names long and creates a second source of truth that drifts when somebody changes the setting and not the name.

Values that change. A name containing a bid or a budget is wrong within a month.

Values nobody will filter on. A precise creation timestamp, an internal ticket reference, the initials of whoever built it. Each is length without a dimension.

Free text. The moment a field permits anything, it contains everything, and the dimension stops aggregating.

The cost of no convention is not aesthetic. It is a report with eleven variants of one campaign name, which nobody trusts, which somebody reconciles by hand each month, and which is eventually abandoned in favour of a spreadsheet maintained separately.

The cost compounds with people. An account built by one person is legible to that person; the convention is what makes it legible to the second, and to whoever inherits it after both have gone.

It also compounds with automation. Rules, scripts, alerts and imports that key on names break when names are inconsistent, and they break silently.

The same discipline applies to the parameters appended to destination URLs, and the two should share a vocabulary.

Where a campaign is named for a market and a stage, the link tagging should use the same tokens for the same things. Otherwise the platform's report and the analytics report describe the same activity in two languages, and joining them becomes manual work that recurs.

One list of permitted values, used in both places, is the whole of the fix.

Agree it in writing, as a short document with the permitted values enumerated. Not a principle people remember — a list people copy from.

Apply it forward. Everything created from now on follows it.

Rename what is live and spending. Those are the entities that appear in reports, and the effort is bounded.

Leave the archive alone. Renaming entities that stopped spending months ago is work with no return, and bulk renaming risks breaking rules, scripts and saved reports that reference the old names.

Check what references names before any bulk change: automated rules, scripts, imports, dashboards and alerts all key on them, and all fail quietly.

It should be possible to answer, from the names alone and without opening anything: what market is this, what is it for, who is it aimed at, what is it offering, and when was it made.

If any of those needs the entity to be opened, the convention is missing a field. If the names are long enough that the list is hard to read, it has too many.

Names are not the only place to carry a dimension, and using the right container saves length.

Most platforms support labels, which attach a value to an entity without appearing in its name. Labels are better than names for dimensions that change — a test status, an owner, a review flag — because updating a label does not rename anything that a rule or a report might key on.

Custom columns and saved segments cover the reporting need directly where the dimension can be derived from existing fields.

The division that works: names carry the dimensions that are fixed for the entity's life and that determine how the list sorts; labels carry the ones that change; and nothing carries what the platform already reports.

The convention usually stops at the campaign level, and the level where it is most useful is the one below it.

Creative is where the remaining variance in an account sits, and an ad named for its angle — the problem it names, the objection it answers, the format it uses — turns the ad report into a record of which arguments work. Named by file name or by date, the same report is a list nobody can learn from.

A short creative convention pays for itself the first time somebody asks which angle to make more of. Typically it needs the theme or angle, the format, and a version, and nothing else.

A convention decays unless somebody owns it, and the decay is gradual: an exception here, an abbreviation there, a new person who was never shown the document.

Two habits hold it. A short written list, kept somewhere people actually look, with the permitted values enumerated rather than described. And a periodic scan of the account sorted by name, which makes every deviation visible in the first screen.