Meta Ads Campaign Name Examples for Real Accounts

Most campaign naming advice gives you a template and no rule. The template then fails on the first account that does not look like the author’s.

The rule is simpler and it travels: a campaign name carries what was decided at campaign level, and nothing else.

Why that rule works

Meta’s hierarchy assigns decisions to levels. The campaign decides the objective and, under CBO, the budget. The ad set decides who sees the ad and where. The ad decides what they see.

A name that mirrors that hierarchy stays readable as the account grows, because each level answers only the questions it actually controls. A name that mixes levels stops being filterable the moment you have more than one of anything.

E-commerce

Conversion_US_March2026
Conversion_UK_Evergreen
Conversion_FR_BlackFriday2026

Objective, market, period. That is the base pattern used across this site, and it holds for most accounts without modification.

The period earns its slot on seasonal accounts and is dead weight on evergreen ones, which is why the second example carries Evergreen rather than a month. If every campaign in your account would carry the same value for a variable, that variable is not telling you anything.

Lead generation

Lead_US_InstantForm
Lead_US_Website
Lead_DE_Evergreen

Here the destination takes the period slot, because instant form leads and website leads differ enough in cost and in quality that mixing them under one campaign produces an average describing neither. The pattern is unchanged, the third variable is simply the one that matters on this account.

Agency accounts

ClientA_Conversion_US_March2026
ClientB_Lead_FR_Evergreen
ClientA_Conversion_US_Testing

The client is added in front of the base pattern rather than replacing part of it. It survives truncation in interfaces that cut long names, and it is the filter an agency reaches for before any other.

The third line shows an extension worth adopting: a separate testing campaign, marked as such, so exploratory spend never contaminates the numbers you report as performance.

The rule applied to hard cases

Should the name repeat the objective, when Meta stores it as a field?

Yes. It makes a list scannable without opening filters, and scanning is what you actually do twenty times a day.

Should it carry the creation date?

No. Meta stores it and shows it as a sortable column. A date in the name adds characters you cannot spend twice and gets misparsed by tools looking for identifiers.

Should it carry the audience?

No. That belongs to the ad set, and putting it at campaign level usually means the account has one campaign per audience, which is a structural problem a name cannot fix.

What a good convention looks like written down

The convention is not the examples. It is the specification, and it fits in five lines:

Pattern:    [Client_][Objective]_[Market]_[Month]
Separator:  underscore between variables, hyphen inside a variable
Objective:  Conversion | Lead | Traffic | Awareness
Market:     ISO country code, uppercase
Optional:   budget mode, only if the account runs CBO and ABO side by side

Written down, it can be handed to a new hire. Held in one person’s head, it degrades the week that person is on holiday.

What this does not solve

Naming makes an account legible. It does not make it well structured. Twelve campaigns with immaculate names, all chasing the same audience, still bid against each other in the same auction and still cost you the difference.

A convention also only holds while everyone applies it. The moment one person types a name by hand at the end of a long day, the grouping breaks for that campaign and for every report that includes it, silently, until someone notices the totals no longer add up.