Beyond the dashboardAI & Measurement · Independent guides
TrackingByAI Journal
← All guidesMeasurement foundations / Guide 04

Campaign labels need a naming plan

Tracking parameters help organize incoming visits only when names are stable, legible, and governed by a small shared vocabulary.

A contemporary workspace showcasing a laptop, tablet, and smartphones, ideal for tech and freelance use.

Start with a clear definition

A campaign URL can identify source, medium, and campaign name. Teams often create many near-duplicate labels through capitalization, abbreviations, and typos. The resulting dashboard splits one effort into several rows, making a simple comparison harder than it needs to be.

A measurement begins as a decision about what to observe. That decision belongs beside the resulting number, because a label alone cannot reveal the trigger, the exclusions, or the time window. The cleanest first step is a short specification written for someone who did not build the tag. It should allow that reader to reproduce the count from the same events.

A decision worth examining

Every reported total has a boundary. Browser settings, consent choices, offline actions, and technical failures can change which events arrive. A useful report describes the visible population rather than quietly calling it everyone. When the boundary changes, annotate the chart before interpreting the new level as a change in human behavior.

A naming sheet can specify allowed source and medium values, lowercase rules, separators, and a short campaign code. Validate a sample URL before distribution and keep ownership of the list clear. Fixing labels only after reports are built often requires a mapping that obscures the raw record.

A small test can reveal a large definition problem. Use a clean browser, perform one action, and follow the event from the page to the final report. Repeat with an error, a reload, and a second device where relevant. This checks whether the instrumentation answers the stated question rather than merely producing a plausible dashboard tile.

Test the edge case

Suppose three people share the same newsletter link with labels email, Email, and newsletter. Before reporting results, normalize the terms and document whether the original values remain available for audit.

Before comparing periods, ask whether the product, tag, report filter, or consent interface changed. A deployment can create a discontinuity that looks like demand. Save the earlier definition and the effective date of the new one. A careful comparison may need to start a new series instead of drawing an unbroken line through two incompatible measures.

Record the limitations

Parameters can travel in shared links and appear in logs. Avoid putting names, email addresses, or other personal data in a campaign label.

Do not overwrite the original campaign parameter when cleaning it. Store the normalized label alongside the received value, so a reviewer can trace a surprising category to the URL that produced it. That trail also helps find links that accidentally include private details.

Counts and rates ask different questions. The count tells how many observed events met a rule; a rate compares that count with a denominator that must also be defined. A striking percentage is difficult to judge without the two underlying numbers. For a narrow segment, small changes to either number may produce a large movement in the rate.

A review path for this question

The result should lead to a decision that someone can name. If the report cannot change a page, a process, or a question for further review, collecting more detail may not help. A compact measure with a clear owner is easier to maintain than an extensive list of events whose purposes have been forgotten.

Three things to record

  • The exact definition or decision behind “Campaign labels need a naming plan”.
  • The source and date for the information being compared.
  • At least one limitation or alternative explanation.

Write a brief interpretation in three parts: what the instrument recorded, the most plausible reading, and another explanation that remains possible. That discipline keeps an observation from becoming an unsupported claim about motive. It also makes a later correction more precise when a missing event or revised definition is found.

Use the guide as a starting point for reviewing a real service. Check the live configuration, current provider documentation, and applicable requirements before making a consequential change. If a page here is unclear or outdated, send its URL and the disputed passage through our contact route.

Continue reading

More perspectives