Vazante
Sign inStart

Metrics and analysis

Campaign naming conventions: the standard that writes your report

A campaign name is not internal tidiness, it is a reporting key. The five-field standard, how to migrate without breaking history, and the mistake that ruins comparison.

Also available in: Português · Español

A campaign name looks like a matter of personal tidiness. It is not. It is the key every report will group by — and a name that cannot be split into parts is a report that cannot be built.

The account where nobody can answer "how much did we spend on remarketing last month" without opening campaigns one by one does not have a tooling problem. It has a naming problem.

What the name has to carry

The test is simple: from the name alone, can you tell which slice it belongs to?

The fields that answer nearly every reporting question:

fieldexamplesanswers
Account or brandacme, clinicxwhose it is, in a shared account
Funnel stagetofu, mofu, bofu, rmktwhere the money sits
Objectiveleads, sales, trafficwhat the campaign is after
Offer or productannual-plan, consultwhat is being sold
Start date2026-10which cohort this is

Put together:

acme_bofu_sales_annual-plan_2026-10
acme_tofu_leads_consult_2026-09
acme_rmkt_sales_annual-plan_2026-10

Now "how much did we spend on bottom of funnel" is a text filter, not archaeology.

The three non-negotiable rules

1. Underscore separates fields, hyphen separates words inside a field. Without it, splitting the name becomes guesswork. annual-plan is one field; _ is the boundary.

2. No spaces, no accents, no capitals. Spaces break URLs and spreadsheets. Accents break text matching in half the tools out there. Capitals turn Sales and sales into two different groups in the report.

3. Fixed order. acme_bofu_sales and bofu_acme_sales destroy any grouping by position. The order is part of the standard.

Ad sets and ads follow the same logic

The campaign name answers "which strategy". The ad set answers "to whom". The ad answers "with what".

campaign  acme_bofu_sales_annual-plan_2026-10
ad set    lookalike-1pc_us-northeast_25-45
ad        video-testimonial-ana_15s_v2

The ad name matters most for creative analysis — it becomes utm_content, and it is how you will find out which piece brings sales. An ad called Ad 3 - copy erases that entire possibility.

Put in the ad name whatever you will want to compare later: format (video, static, carousel), angle (testimonial, price, pain) and version (v1, v2). Those three answer "what kind of piece works here", which is the expensive question.

The name and the UTM must tell the same story

The name organizes the platform. The UTM carries the information outward — to the site, to Analytics and to the CRM. If they diverge, you have two reports that never agree.

The safest route is to derive the UTM from the name, using the platform's dynamic parameters:

utm_source=facebook
utm_medium=cpc
utm_campaign={{campaign.name}}
utm_content={{ad.name}}
utm_term={{adset.name}}

That way the UTM can never go stale relative to the name, because it is the name.

If your CRM has a character limit on the source field — many do — use the ID instead of the name in utm_campaign and keep the ID-to-name map. Less readable, far more reliable.

How to migrate without breaking history

This is why most accounts never fix their naming: the fear of losing comparability.

Renaming does not affect delivery. On Meta and Google, the name is a label; the campaign keeps the same ID, the same learning and the same performance. Nothing resets.

What breaks is a report that groups by name. If your dashboard sums by text, renaming splits history in two. If it groups by ID — as Vazante and any serious tool do — nothing happens.

The procedure:

  1. Write the standard before touching anything. One page, with the fields, the order and the allowed values for each field.
  2. Export current names with spend for the last 12 months. That is your "old name → new name" map, and it is what saves you when someone asks about an earlier period.
  3. Rename only what is active. Paused campaigns can keep the old name; they will not show up in current-period reporting.
  4. Everything born after this is born in the standard. This is where the standard holds or dies.
  5. Record the switch date in your document. Six months from now, when a number looks odd, that date explains it.

The mistakes that kill a standard

Too many fields. Eight fields make a 90-character name nobody types correctly. Four to six.

A field with free values. An "objective" field holding leads, lead, acquisition and signup is not a field, it is free text wearing a field's clothes. Define the closed list.

A standard that lives in one person's head. Write it down. In a document the intern opens before creating their first campaign.

A standard with no policing. Once a month, list active names and look for the strays. It takes five minutes and it is the difference between a standard and a good intention.

The final test

Ask someone who does not work on the account to look at the campaign list and tell you which are bottom of funnel, which started this month, and which sell product X.

If they can, the standard works. If they have to open each one, the name is decorating the screen instead of working.

For the next step — carrying that structure through to the sale in the CRM — see connecting Meta Ads to your CRM. To audit an account that arrived with no standard at all, see auditing an inherited ad account.

Frequently asked questions

Can I rename a campaign that is running?

Yes. Renaming does not reset learning or affect delivery on Meta or Google. What breaks is your reporting history, if it groups by name instead of by ID.

How many fields should the standard have?

Between four and six. Fewer separates nothing; more and nobody fills it in properly, and the standard dies within two weeks.

Which separator should I use?

Underscore between fields and hyphen inside a field. That way the name splits on underscores unambiguously, and the hyphen stays free for compound values.

Does naming replace UTMs?

No. The name organizes the platform; the UTM carries the information to the site and the CRM. Both must tell the same story, and ideally the UTM is derived from the name.

Read next