On this page10 sections
Why campaign names need a review
Campaign names look like a small administrative detail until a report groups by them. A single campaign can appear as three different labels across the ad platform, the CRM, and analytics, and each system may treat those labels as separate campaigns. The result is a report that splits one campaign into pieces or merges two campaigns that only look similar. A short weekly review catches the drift before it reaches a dashboard. It does not need to rename everything, but it should make the mismatches visible while they are still cheap to fix.
Start from the systems that create names
List the systems where a campaign name is created or copied: the ad platform, the landing page builder, the CRM, and the analytics property. For each one, record who can create a name, whether a template is required, and where the value is stored. A naming convention only holds if the people creating names know about it and the tool makes it easy to follow. If the ad platform allows free text while the CRM expects a structured value, the mismatch starts at the source, not in the report.
Define the convention in one place
Write the convention down as a short pattern with named parts. For example, a name might include the channel, the audience, the offer, and the start month, in a fixed order and with a fixed separator. Keep the pattern short enough to type and specific enough that two people produce the same result. Store it where the team already looks for process documentation, and link to it from the campaign intake form. A convention that lives only in a slide deck will not survive the next busy launch.
Check new campaigns first
Spend most of the review on campaigns created since the last check. For each one, compare the name in the ad platform with the name in the CRM and the name used in analytics. Record the campaign, the start date, and the variation. New campaigns are where a fix is cheapest because the data has not spread into many reports yet. Reviewing old campaigns is still useful, but a long list of historical mismatches can bury the one new pattern that will repeat next week.
Distinguish a rename from a new campaign
A renamed campaign and a new campaign can look identical in a report if the old name disappears. Note whether a change was a label correction or a new launch, and record the date. If a platform keeps history under the old name, the report may show two rows that are really one campaign. If the old name is gone, the history may vanish from a grouped view. The review should record which behavior the system exhibits, because the repair differs: a mapping fix for a rename, and a new record for a launch.
Keep a small mapping table
Maintain a mapping table that links each campaign's canonical name to its variants across systems. Include the source system, the variant, the date it was observed, and the owner. This table is the practical bridge between a messy source and a clean report. Keep it small and current rather than trying to document every historical name. When the same variant appears twice, that is a signal that the source process needs a fix, not another row in the table.
Review the report output, not only the source
After checking the names, run the report the team actually uses and confirm the grouping. A campaign can have a consistent name and still be grouped incorrectly because a filter or a lookup table is stale. Compare the report totals with the source totals for one or two campaigns. If the numbers do not reconcile, the naming review has found a reporting issue rather than a naming issue. Both are worth fixing, but they belong to different owners.
Assign one owner for the convention
A naming review without an owner becomes a list of complaints. Name the person who can update the convention, approve an exception, and decide when a rename is worth the reporting cost. Give that person the authority to reject a new campaign that does not follow the pattern, or to require a mapping entry before launch. The owner does not need to create every name; they need to keep the rule and the exceptions coherent. Record the owner in the convention document.
Keep the review short and repeatable
The weekly review should take a few minutes and produce a short list: new mismatches, the owner, and the next action. Do not turn it into a full data audit. Keep the same fields and the same scope each week so the team can see whether the situation is improving. If the list grows for several weeks, the cause is probably a source process that allows free text. Fix that process rather than adding more cleanup to the review.
Use the review before the monthly close
Schedule the review a day or two before the monthly reporting close, when there is still time to fix a mapping or confirm a rename. At close, the team should not be discovering that two campaigns share a label. A short pre-close check protects the report and gives the owner a clear window to act. The weekly rhythm is the point: small corrections made consistently are cheaper than a quarterly reconstruction of what a campaign was called.
