Skip to main content
Naming patterns (also called naming conventions) let you define a template for how campaigns, ad sets, and ads are named when published to Meta. Instead of typing names manually, use tokens — placeholders wrapped in curly braces that get replaced with real values at publish time. This keeps your naming conventions consistent across every launch.

How It Works

Write a pattern using any combination of plain text and tokens:
At publish time, this becomes:
Tokens resolve to actual values from your draft — targeting, creatives, campaign settings, and more. Any token that has no value is removed automatically, and leftover separators are cleaned up so you never get names like CBO | | 2025-03-15.

Where to Set Naming Patterns

You configure naming patterns at three levels in the launch wizard:

Preset Templates

AdStellar includes two built-in presets so you can get started without building a pattern from scratch:

Basic

Quick identification with essential info.
  • Campaign: {campaign_objective} | {launch_date}
  • Ad Set: {audience_template_name} | {locations} | {custom_audiences}
  • Ad: {creative_template_name} | {headline} | {primary_text_preview} | {media_filename}

Advanced

Comprehensive naming with full details.
  • Campaign: {budget_type} | {campaign_objective} | {conversion_event} | {launch_date}
  • Ad Set: {audience_template_name} | {locations} | {age} | {gender} | {custom_audiences}
  • Ad: {creative_template_name} | {headline} | {primary_text_preview} | {media_filename} | {cta} | {creative_type}
Select a preset from the template dropdown on any naming field, or choose Custom to build your own.

Available Tokens

Campaign Tokens

Ad Set Tokens

Ad Tokens

Creative Testing Mode Tokens (Ad Set Level)

When Creative Testing Mode is enabled, each ad set corresponds to a single creative. This unlocks creative-related tokens at the ad set level so you can identify which creative each ad set contains:
In Creative Testing Mode, a pattern like {audience_template_name} | {creative_template_name} | {media_filename} makes it easy to see both the audience and creative for each ad set at a glance in Meta Ads Manager.

Saving Custom Templates

Once you’ve built a naming pattern you like, save it as a reusable template:
1

Build your pattern

Type your pattern using tokens and plain text, or start from a preset and modify it.
2

Save the template

Click Save as Template and give it a name. The template saves the patterns for all three levels (campaign, ad set, and ad).
3

Reuse across launches

Select your saved template from the dropdown on any future launch. Templates are available to everyone on your team.
You can rename or delete saved templates from the same dropdown menu.

Tips for Effective Naming

Consistent naming makes campaigns dramatically easier to find, filter, and analyze in Meta Ads Manager. Pick a convention and stick with it.
  • Start ad set names with {audience_template_name} — makes it easy to filter by audience in Ads Manager.
  • Include {creative_template_name} or {media_filename} in ad names — quickly see which creative is performing best.
  • Add {launch_date} to campaign names — essential when running similar campaigns over time.
  • Use {variant_index} for deduplication — if multiple ad sets use the same audience, the variant index keeps names unique.
  • Use separators consistently — pick |, -, or _ and stick with one style. Pipes (|) are popular because they’re visually distinct.
  • Keep patterns concise — Meta truncates names longer than 400 characters in some views. AdStellar enforces this limit automatically.

Examples

E-Commerce Brand

Agency Managing Multiple Clients

Creative Testing Setup

How Token Resolution Works

When you publish a campaign, AdStellar resolves tokens in order:
  1. Campaign name is generated first using campaign-level tokens.
  2. Ad set names are generated next — the {campaign_name} token is available here because the campaign name was already resolved.
  3. Ad names are generated last — both {campaign_name} and {adset_name} tokens are available because both were already resolved.
If a token has no value (for example, {custom_audiences} when no custom audiences are used), it’s removed from the name and any surrounding separators are cleaned up automatically.