PROCLOUDLABS

Best practices · Best practice

Campaign naming that doesn’t drift.

Seven practices that keep campaign names, IDs and reports in agreement as your team and your platforms grow.

Best practice

Why naming drifts

Campaign names start as a convention in a spreadsheet. Then a new team joins, an agency improvises, a product line is renamed, and the names in your platforms stop matching the names in your reports. Reporting drifts from reality one campaign at a time.

These seven practices keep a naming standard intact as you grow.

01

Separate the ID from the name

Give every campaign a short permanent ID that never changes, and let the readable name carry the description. Reports join on the ID, so a renamed campaign doesn't break history.

02

Build names from managed lists, not free text

Each segment of a name (brand, region, channel, audience, purpose) comes from a controlled list. Free text is where spelling variants and one-off abbreviations creep in.

03

Fix the order and the separator

Decide the order of segments and one separator, write them down, and validate names against them before anything goes live, not after.

04

Never reuse or rename a code once it's been used

A code that has appeared in a live campaign is part of your reporting history. Retire old values instead of renaming them, and keep them resolvable for old records.

05

Map the aliases

Partners and platforms will use their own labels. Keep a list of known aliases and old spellings, and translate them to your standard on import instead of fixing them by hand.

06

Approve changes to the standard

Adding a value can be quick. Renaming or retiring one changes your history, so route it through an owner who approves it.

07

Measure adherence

Check live campaign names against the standard every month and track the percentage that pass. What isn't measured drifts back.