Case: a naming convention rollout that recovered $2,100/mo in hidden losers

Case: a naming convention rollout that recovered $2,100/mo in hidden losers

The account: Voluum, 6 buyers, 340 active campaigns, free-text campaign names. Nobody could group by angle, geo, or lander because the names were inconsistent (Campaign 7 final FINAL).

The procedure we ran over 3 days:
1. Defined a fixed token order: {geo}_{vertical}_{source}_{angle}_{lander}_{date}
2. Built a lookup sheet mapping every old name to the new one (340 rows)
3. Renamed in bulk via the Voluum API, kept campaign IDs intact so stats stayed attached
4. Added the same tokens as Voluum custom variables so reports could pivot on them

What the new grouping exposed:
— Pivoting by angle, one angle ran across 22 campaigns at a combined -31% ROI, invisible before because it was spread across 6 buyers
— Pivoting by lander, one lander template underperformed its sibling by 19% CR everywhere it ran

Actions taken:
— Paused the losing angle across all 22 campaigns in one filtered view
— Retired the weak lander

Outcome: ~$2,100/month of spend reallocated from confirmed losers, found only because grouping became possible.

Naming is not cosmetic. It is the index your reports query against.

Save this SOP. Run this before every launch.