Set a campaign UTM naming standard before a multi-channel launch

A naming standard that keeps campaign reporting readable when several channels launch at once.

Set a campaign UTM naming standard before a multi-channel launch

Decide what the taxonomy must answer

A UTM standard should answer a small set of reporting questions, such as which channel produced a demo request and which campaign influenced a pipeline stage. Write those questions down before choosing parameter values. The answers determine how granular the taxonomy needs to be. A standard built without questions tends to collect labels nobody uses.

Keep the first version narrow enough to remember. Most teams need source, medium, campaign, and occasionally content or term. Adding every conceivable field makes links long and inconsistent. Start with the questions the team reviews monthly, then extend only when a real gap appears.

Choose lowercase values and separate words with hyphens so links remain readable and comparable. Decide whether you will use the platform name or the channel category for source, and apply the choice everywhere. Inconsistent capitalization creates duplicate rows that look like separate channels. A short reference table prevents most of these errors.

Publish the allowed values in a shared document and link it from the campaign brief. People building links should not have to guess whether the value is linkedin or linked-in. Include examples for email, paid search, organic social, and partner placements. The standard is only useful if it is easier to follow than to improvise.

Keep source and medium distinct

Source identifies where the traffic came from, while medium describes how it arrived, such as email, paid-social, or referral. Mixing the two makes channel reports overlap and double count. Decide which field owns the platform and which owns the buying motion. Then apply the rule to every link in the launch.

Write a few examples that show the distinction clearly, such as source newsletter and medium email, or source partner-name and medium referral. Review the examples with the team that builds the links. A shared example is more effective than a definition that people interpret differently. Keep the examples beside the value table so a new campaign builder can copy the pattern instead of inventing one.

Name campaigns for the offer, not the channel

A campaign name should describe the initiative, such as fall-warehouse-audit, rather than the channel that carries it. When the campaign name includes the channel, the same initiative fragments across reports. Use the medium field to show the channel and keep the campaign name stable across placements. This makes cross-channel comparison possible without a lookup table.

Include a time marker only when the team genuinely runs the same offer more than once. Use a short quarter or wave label rather than a full date, and keep it consistent. Avoid embedding internal project codes that mean nothing to a future analyst. The name should still make sense six months after the launch.

Handle paid and organic traffic separately

Paid and organic traffic from the same platform often need different mediums so the team can compare cost and performance. Agree on those medium values before the launch and document them beside the budget. If both use the same value, the paid report will include organic clicks and the comparison will mislead. The separation should be visible in the link, not reconstructed later.

Check whether the ad platform appends its own parameters and whether they conflict with yours. Record which system owns the final URL and who approves changes. A launch with several agencies needs one owner for the taxonomy. Without that owner, each agency will follow its own conventions.

Store the standard in a shared reference

Put the standard where campaign builders already work, such as the campaign brief template or the project board. A separate wiki page that nobody opens will not prevent bad links. Include a copy-ready example and a link to the full value list. The reference should be short enough to scan during a busy launch.

Assign an owner to update the reference when a platform changes its parameter behavior. Record the date of the last review so users know whether the page is current. Old examples should be removed rather than left as traps. A reference with stale examples is worse than no reference because it looks authoritative.

Pull every live campaign URL into one list and check the parameters against the standard. Look for missing values, inconsistent capitalization, and campaign names that do not match the brief. Fix the links at the source rather than editing the reports later. A pre-launch audit takes less time than reconciling a month of data.

Test a sample of links end to end and confirm the landing page matches the campaign promise. A correct UTM on the wrong page still produces a confusing report. Record who approved the final list and when. The audit should be a required step in the launch checklist, not an optional review.

Review the taxonomy after the campaign

After the campaign, compare the reports you planned with the reports you can actually build. Look for values that created unexpected splits or merged distinct channels. Ask the people who read the reports which fields they used and which they ignored. Their answers show where the taxonomy is too complex or too thin.

Change one or two values for the next campaign and note the change in the reference. Keep historical links unchanged so old reports remain reproducible. A taxonomy evolves through small, documented adjustments. The goal is a consistent record, not a perfect naming system on the first attempt.

Sources

  1. Advertising and Marketing Basics, Federal Trade Commission. Provides a reference for truthful and non-deceptive marketing claims.
  2. CAN-SPAM Act: A Compliance Guide for Business, Federal Trade Commission. Outlines compliance considerations for commercial email campaigns.
  3. Business Trends and Outlook Survey, U.S. Census Bureau. Supplies business conditions context for campaign planning.

Related GTM guides