Campaign names should preserve meaning across teams and months
Use names that make objective, audience and offer identifiable across reports. Inconsistent campaign labels force reviewers to reconstruct strategy from scattered platform details.
A naming system should distinguish the offer, market, channel and relevant test without becoming unreadable. Stable identifiers are useful when a display name changes. Preserve a register so reports do not depend on one person remembering abbreviations.
A worked example
A hypothetical team renames every campaign each month. Trend reports split a continuous effort into disconnected rows. Another uses one generic name for several markets, hiding local differences. Both can be improved with a deliberate identity and grouping rule.
How to apply it
- Choose fields that support actual reporting decisions.
- Document names and stable IDs with dates and scope changes.
- Coordinate advertising names with external link tags where relevant.
What the result can establish
Avoid personal data in campaign names and URLs. A convention improves interpretability; it does not fix incorrect conversion definitions. Review legacy names before consolidating rows that may represent different audiences or offers.
Reference: Google Analytics: campaign URL parameters.
Supporting documentation
Google Analytics: campaign URL parametersGoogle Ads: conversion measurementGoogle Ads: conversion tracking