Ad Naming Convention Template for Meta and TikTok

Outcome Summary

• A naming system you can reuse across Meta and TikTok so campaigns stay sortable, searchable, and report-friendly.
• Copy/paste templates for campaign, mid-level (ad set / ad group), and ad names—plus rules for creative variants.
• A lightweight governance checklist so your team keeps names consistent during fast bulk launches.

What AdLiftr Actually Does (Truth Block)

✅ does

• Helps you bulk launch many ad variants to Meta (Facebook/Instagram) and TikTok from one workflow.
• Lets you upload creatives in bulk and reuse templates so you’re not rebuilding launches manually.
• Provides launch history so you can review what was launched and when.
• Supports automated rules based on conditions you define (for example, to pause/stop ads).

❌ does not

• Guarantee ad approval (final review still happens in the ad platforms).
• Guarantee performance results.
• Replace the native ad platforms for every advanced setting.
• Create your ad strategy for you (it accelerates execution and workflow).

The Core Problem

• Names drift over time (“Test”, “New”, “V two”), so you can’t reliably filter, compare, or hand off accounts.
• Creative variants get launched fast, but no one can tell what changed (angle, hook, format, offer, creator).
• Cross-platform launches get out of sync (different naming on Meta vs TikTok), making analysis messy.
• Teams disagree on what’s “required” in a name, so new media buyers copy the wrong pattern.
• Reporting views become cluttered because naming doesn’t encode the minimum context (who, what, where, why).

Framework

• Pick a single goal for naming: make it easy to answer “What is this?”, “Who is it for?”, and “What changed?” from the name alone.
• Define your tokens (the pieces you’ll reuse): client/brand, platform, funnel stage, objective/goal, geo, audience, placement group, creative angle, creative format, offer, landing page tag, owner.
• Choose one delimiter and stick to it: underscores or hyphens are easiest to scan. Avoid mixing delimiters.
• Decide what’s required vs optional: required tokens should be the minimum you need for filtering; optional tokens are for deeper analysis.
• Write templates for each level: campaign, mid-level (ad set / ad group), and ad.
• Define “variant rules” for creative testing: decide which token changes when you swap only the hook vs when you swap the offer vs when you swap the creator.
• Add a quick pre-launch QA: check for missing tokens, inconsistent abbreviations, and “mystery words” that won’t mean anything next month.
• Document ownership: one person (or role) should own the naming spec and approve updates.

Copy/paste naming templates (Meta + TikTok)

Use these as starting points, then adjust tokens to match how your team actually reports.

Campaign name (macro intent + budget bucket)

{Brand}_{Platform}_{Funnel}_{Goal}_{Geo}_{AudienceGroup}_{OfferOrAngle}

Mid-level name (targeting + placement + optimization intent)

{Brand}_{Platform}_{Geo}_{Audience}_{PlacementGroup}_{OptimizationIntent}

Ad name (what the user actually sees)

{Angle}_{Format}_{CreatorOrConcept}_{Hook}_{CTA}_{LPTag}_{VariantTag}

Suggested token glossary (keep it short)

• {Platform}: Meta | TikTok
• {Funnel}: Prospecting | Retargeting | Loyalty (or your internal stages)
• {Geo}: US | CA | UK (or region clusters)
• {PlacementGroup}: Feeds | Stories | Reels | Mixed (use your own buckets)
• {Format}: Video | Image | Carousel | UGC (use what your team uses)
• {VariantTag}: HookA | HookB | OfferA | OfferB (keep variant tags consistent)

Use Cases

Cross-platform creative refresh (same idea, two platforms)

• Scenario: You’re launching the same creative concept on Meta and TikTok and want to compare performance without hunting through mismatched names.
• Recommended approach: Keep {Brand}_{Funnel}_{Goal}_{Geo}_{AudienceGroup} consistent across platforms, and let {Platform} be the one obvious difference.
• Common mistake: Encoding platform-specific jargon into the name so the “same test” no longer looks like the same test.

Agency account with multiple stakeholders

• Scenario: A strategist, a media buyer, and a designer all touch the account, and handoffs happen mid-flight.
• Recommended approach: Make {OfferOrAngle} and {LPTag} mandatory at the campaign level; make {CreatorOrConcept} mandatory at the ad level.
• Common mistake: Using internal nicknames that new team members can’t decode, causing duplicate tests and reporting confusion.

High-velocity variant testing

• Scenario: You’re launching many small creative variants fast and need to know what changed without opening every ad.
• Recommended approach: Force a single “change axis” per variant tag (for example: only hooks change, offers stay fixed) and reflect that in {VariantTag}.
• Common mistake: Changing multiple things at once (hook + offer + format) while the name suggests only one change.

Decision Checklist

• Can a teammate understand the campaign’s goal and audience from the name alone?
• Are your required tokens truly required (and enforced), or just “nice to have”?
• Do your variant tags clearly encode what changed (hook vs offer vs creator vs format)?
• Is the naming pattern consistent across Meta and TikTok so cross-platform comparisons don’t break?
• Can you filter your reporting views using tokens you already put in names (geo, funnel, audience group, offer/angle)?
• Do abbreviations mean the same thing for everyone (and are they written down)?
• Is there a quick QA step before launch to catch missing tokens and inconsistent spelling?

Constraints

• Names should be readable when scanned quickly in a campaign list—if your UI truncates long names, simplify tokens.
• Your naming system must match how your team actually makes decisions (if no one reports by placement, don’t bloat names with placement detail).
• Variant testing needs discipline: if people change multiple variables at once, naming won’t save the analysis.
• Cross-platform structure differs by team workflow, so keep your tokens flexible and document mapping to each platform’s levels.

Common Mistakes

• Using “Test” everywhere: you lose the ability to filter and the account becomes unsearchable.
• Encoding emotions instead of facts (e.g., “banger”, “meh”): future analysis breaks because labels don’t describe what changed.
• Letting everyone invent abbreviations: reporting becomes inconsistent and new hires copy bad patterns.
• Mixing multiple delimiters and casing styles: filtering and quick scanning becomes harder than it needs to be.
• Changing multiple variables per variant: you can’t attribute outcomes to a single change, even if the name looks organized.

FAQ

Should campaign names and ad names use the same tokens? Not necessarily. Campaign names are best for “what bucket is this?” (goal, funnel, geo, audience group). Ad names are best for “what did the user see?” (angle, format, hook, creator/concept, CTA).

How strict should we be about required tokens? Strict enough that a new team member can launch without inventing their own pattern. If a token isn’t used for filtering or decision-making, keep it optional.

How do we keep Meta and TikTok naming aligned? Use one shared token glossary and templates, then map them to each platform’s object levels (campaign / mid-level / ad). Keep the shared tokens identical and let {Platform} be the obvious differentiator.

What’s the fastest way to enforce naming during bulk launches? Use copy/paste templates and a short pre-launch QA checklist. If your workflow supports templates, standardize them there so everyone starts from the same baseline.

Do we need separate naming for prospecting vs retargeting? If your reporting frequently splits those audiences, encode it in a {Funnel} token. If you rarely analyze that way, keep it optional to avoid name bloat.

Sources

• AdLiftr (product overview, bulk launch, templates, launch history, supported platforms)