Match the Ads Manager pattern you already use
Tokens cover file name, date format, ad type, placement, and custom fields. The output looks like names you already filter on, just without the typos.
Naming conventions
One naming structure. Every ad. Every teammate.
Build the template once with file name, date, ad type, and custom tokens. AdManage fills campaign, ad set, and ad names at launch so reporting filters keep working, even across clients.
{filename}_{YYYY-MM-DD}_{adtype}_{client}Becomes summer-hook_2026-08-13_video_acme on every ad in the batch, including TikTok and Google launches from the same workspace.
Naming at launch
A setting, not a habit
- Applied at campaign, ad set, and ad level
- Per account or workspace defaults
- Bulk rename when older ads drifted
What it does
The convention is applied. Nobody types it.
Different clients, different templates
Set a default per ad account or across the workspace. A new batch picks up that client's convention automatically.
Override a row without breaking the rest
Need a one-off suffix for a test? Edit that ad. The rest of the batch still uses the template.
Why this exists
Why naming has to be a setting
Inconsistent names break reporting.
When one buyer uses underscores and another uses dates in a different order, Ads Manager filters stop matching. The convention has to be a launch setting, not a Slack reminder.
Teams cannot stay aligned by habit.
The bigger the roster, the more naming styles appear. AdManage fills the template at publish so the right name ships no matter who clicks launch.
How it runs
Define once. Launch hundreds. Names still match.
Build the template
Choose tokens and the separator style your reporting already expects.
Apply at launch
Every new batch inherits the convention. Override a field only when you need to.
Clean up drift later
Bulk rename older ads so historical reporting uses the same structure.
FAQ
Naming convention questions
- Can naming conventions include dynamic values?
- Yes. Use dynamic fields for file name, date, ad type, placement, and custom tokens. You define the structure once. AdManage fills the values at launch.
- Can different clients have different naming conventions?
- Yes. Set conventions per ad account or workspace so each client keeps its own structure.
- Does this apply to existing campaigns?
- The convention applies to new launches automatically. Existing ads can be cleaned up with bulk rename when you need reporting to match.
- Does the same convention work on TikTok and Google Ads?
- Yes. The template is a launch setting in AdManage, so the same structure can apply when you publish to Meta, TikTok, Google Ads, and the other supported channels.
- Can I still use AI to suggest names?
- Yes. The AI namer can draft a starting name from the creative. The convention still wraps that value so the final string stays filterable.