A naming convention is a fixed, documented pattern for naming every entity in a media-buying operation — campaigns, ad sets, ads, tracking links and creatives — so that the important attributes of each are readable from the name alone: the GEO, the offer, the traffic source, the creative batch, the funnel variant and the launch date.
Definition
A naming convention is a fixed, documented pattern for naming every entity in a media-buying operation — campaigns, ad sets, ads, tracking links and creatives — so that the important attributes of each are readable from the name alone: the GEO, the offer, the traffic source, the creative batch, the funnel variant and the launch date. It is unglamorous infrastructure, but it is the difference between a portfolio that stays analysable at scale and one that becomes an unreadable list of "Campaign 47 – copy (final)(2)".
The convention works by using consistent delimiters and an agreed field order, for example GEO_offer_source_creative_date rendered as br_casinoX_push_v03_0912. Because the order and separators never change, a tracker, a spreadsheet or a script can parse the name into columns and group results by any field — total spend by source across all campaigns, cost per FTD by GEO, performance by creative batch — automatically, without anyone tagging entities by hand.
In context
The payoff scales with the operation. For one buyer with five campaigns, naming is a minor convenience.
For a team with two hundred live campaigns across a dozen GEOs and six sources, it is the only thing that makes weekly review possible: the analyst runs one pivot and sees that push is beating native everywhere except Mexico, that the v03 creative batch outperforms v02 by 20%, and that everything launched after the 9th is underperforming because of an offer payout cut — none of which is visible without structured names.
The rules that make it work are boring but strict. Decide the fields and order before the first campaign.
Use separators that will not appear inside a field value. Keep field vocabularies controlled ("push" always, never "Push" or "push-traffic").
Never change the scheme midway, because a mix of old and new names fragments historical data and defeats the purpose. Teams write the convention into onboarding docs and audit adherence, because one person freelancing their own names pollutes everyone's reports.
Worked example
A team fixes the pattern GEO_offer_source_creativeBatch_date. Six months in, the weekly pivot shows push outperforming native in every GEO except Mexico, creative batch v05 beating v04 by 18%, and a dip in everything launched after a payout cut on the 14th — all read from names, with no manual tagging.
Related terms
Frequently asked questions
Browse the full iGaming & affiliate glossary — hundreds of EN/RU terms with examples.
← Back to glossary