Ad Campaign Naming Conventions: Make the Test Readable

A useful ad campaign name tells a colleague which offer and test they are reviewing. An ad name identifies the concept and approved revision. Keep those labels short enough to scan, then connect them to the actual entity IDs, settings and assets in a register.
We build the convention around retrieval: someone should be able to find the right work without opening several items called “New image.” The label helps them navigate; the saved configuration establishes what the item actually does.

Choose the minimum information for each level
Use the account label for the business and operational scope, the campaign name for the initiative, a subordinate audience group for the audience hypothesis and test, and the ad label for the creative concept, format and revision. Adapt those roles to the entities in the advertising system you use; platforms do not all share identical structures.
Keep billing and access details in the operational record. Avoid “best,” “winning” and “new” as identifiers: they describe an opinion or a moment. “Installation quote” remains interpretable after launch week.
Use a small dictionary with stable meanings
Choose one term for each recurring offer, audience approach and format. Add a short code only when its meaning is available to the next person. Separate a concept from its revision: C12 can identify the tool-requirement message, while V03 identifies its third approved revision.
A copy correction can remain a revision of C12. A different message needs its own concept reference, even if the designer reuses the layout. Include a date where it identifies an actual initiative or review period; do not rename an ongoing campaign simply because the month changed.
Fill the convention for an installation offer
Fictional example: Alder Displays runs an installation-quote initiative. These are illustrative team labels and reference codes, not platform requirements or real entity IDs.
Account: Alder Displays | Main business.
Campaign: LEADS | Installation quote | Launch 2026-11.
Audience group: T07 | Broad brief | AUD-B.
Ad: C12 | Tool requirement | Image | V03.
Dictionary: T07 = audience comparison; AUD-B = broad-approach brief; C12 = tool-requirement message; V03 = third approved revision.
Register references: actual account and entity IDs, saved audience settings, approved asset, destination and change history.
“Broad brief” records an intention; it does not prove that the saved audience settings match. V03 needs to point to the approved V03 file, rather than an older export renamed during upload. The register supplies that evidence without making every name longer.
Keep names, IDs and URL labels distinct
The readable name can be corrected. The entity ID identifies the campaign or ad in the register. A tracking value in a URL labels observable traffic in analytics. These references may be mapped together, but they have different jobs.
Our UTM naming and QA guide covers the URL layer. If the team aligns campaign names and tracking labels, write down that mapping. Correcting an account label does not establish that every saved URL or historical report has changed with it.
Use offer or project codes rather than personal information or confidential customer details. Names can appear in exports and screenshots beyond the immediate working view.
Resolve “New image” without losing the reference
Suppose two fictional ads share that label. The register and actual files identify one as retired C12 V02 and the other as approved C12 V03. Compare the entity IDs before changing either label.
A completed correction record can read: “Existing entity linked to retired export: label corrected to C12 | Tool requirement | Image | V02. Existing entity linked to approved export: label corrected to C12 | Tool requirement | Image | V03. Both entity IDs retained; correction date recorded.”
Historical results remain associated with the entity that produced them. There is no need to recreate an ad solely to tidy its name. The creative master-file handover guide covers the separate task of making the approved asset references usable by another designer.
Test whether someone else can find the work
Ask a colleague to find the installation initiative, explain T07 and retrieve C12 V03's approved file, saved settings and destination. If they can read the labels but cannot retrieve those references, fix the register before adding more codes.
Bring an export and the dictionary to DigitalThrob's advertising services for a review of the actual handover. A naming system has earned its place when it makes that work quicker to identify and verify.
Comments