Reporting can become difficult before the first campaign launches if each person chooses a different name for the same source. A naming convention needs an owner, an approved vocabulary and a way to check the finished link.
We recommend treating HubSpot UTM tracking as a small operating contract. The contract should explain what each value means and how the team verifies that a link reaches the right destination with the intended parameters intact.
TLDR: Agree on source, medium, campaign and optional variation values before building links. Keep the campaign key stable, review generated tracking parameters and test the complete destination path. Do not edit a connector's tracking template merely to impose a naming preference without checking its requirements.
HubSpot UTM tracking uses parameters on a distributed URL to help describe where a visit came from and which campaign or variation it belongs to. UTM stands for Urchin Tracking Module. The useful part for your team is the shared meaning of the values, not the acronym.
A tracking URL is still a destination URL. The parameters add campaign context; they do not create the landing page, install the HubSpot tracking code or prove that every visit will be measured. Review those dependencies separately when testing the complete path.
Use the source to describe the sending platform or publication, the medium to describe the channel and the campaign value to identify the initiative. Where appropriate, content can distinguish a creative or link variation and term can carry an agreed keyword-related distinction. Do not use every field as another copy of the campaign name.
The naming policy should explain allowed values and missing values. A simple convention might use lowercase labels and one separator consistently. That is a proposed operating choice, not a HubSpot requirement. The important result is that two people describing the same campaign produce the same approved values.
Do not infer that Google Analytics and HubSpot will classify every tagged visit identically. Each reporting system applies its own rules and has its own tracking evidence. UTM data helps describe the link, but it does not eliminate differences between the systems.
HubSpot provides a tracking URL builder for eligible subscriptions. Its documentation describes choosing the destination and campaign context when creating tracking URLs. Confirm the current account access and available fields before following menu instructions from an older tutorial. HubSpot tracking URL creation
Before using the URL builder, have the final destination and approved values ready. After creation, inspect the resulting URL instead of assuming the builder supplied the values you intended. Check the actual campaign key, encoding and any parameters already present on the destination.
Store the completed tracking URL with a short description of where it will be used. A campaign may have several links for email, social media or paid ads. A shared register makes it easier to find the correct version and avoids someone recreating it with a slightly different spelling.
Test the version that will reach the visitor, including any email redirect, shortener or ad-platform tracking layer. A manually pasted URL may behave differently from the link generated by the distribution tool. Record both the sent link and the final destination observed in the approved test.
Check that the URL reaches the intended page, carries the expected parameters and does not accidentally expose private data. Then inspect the relevant analytics evidence. A page that loads successfully has passed a delivery check, but it has not yet passed the tracking check.
Use a small test matrix when multiple platforms are involved. Include a destination with an existing query string, a link that redirects, an encoded campaign value and the actual email or ad link format. These cases can expose malformed URLs before the marketing campaign reaches its audience.
Google Ads auto-tagging and the HubSpot ads integration may add identifiers or tracking values that serve different purposes from your manual campaign labels. Do not remove them just to make the URL look cleaner. First identify which system supplies each value and which reporting or matching process depends on it.
If the paid-search team maintains a tracking template, coordinate changes with that owner. A campaign taxonomy document should explain the relationship between manual UTMs and connector-generated parameters, including any values the team must not override. HubSpot Google Ads tracking requirements
If a report shows several spellings of the same source, determine whether they represent different campaigns or an inconsistent label. Preserve the original evidence while deciding how the reporting layer should group the values. Do not silently rewrite historical contact properties to clean up a chart.
UTM tracking supports analysis of marketing channels and campaign traffic. It does not prove incremental lift, revenue or marketing ROI on its own. Use consistent naming to make the evidence easier to interpret, then apply the appropriate report definitions to the business question.
Start with the questions you want the report to answer: where the visit came from, what channel carried it, which campaign it belongs to and which approved variation was used.
Write the allowed values and examples in a short register. Specify spelling, separators and capitalization conventions so the team does not have to improvise them. Record who can add a new value and how existing reports will treat it.
We recommend limiting UTM values to approved campaign labels. Do not put personal details, email addresses, credentials or sensitive record information in those values. Make this a link-review rule; it is not a claim that HubSpot automatically prevents those entries or that the rule establishes legal compliance.
HubSpot describes a tracking URL as a URL with parameters and explains how those parameters are used in its tracking tools. The tracking-URL documentation also lists subscription requirements. Verify account eligibility before prescribing the exact creation workflow.
For broader reporting context, see the HubSpot KPI marketing gap analysis. Keep the naming contract focused on the inputs your team controls.
A display name can help a person recognize a project. The value used for tracking needs a stable definition that survives a change in the visible campaign title.
HubSpot documents an automatically generated campaign UTM value when a campaign is created, with controls for managing those values. Its campaign UTM guide lists the relevant Marketing Hub requirements.
Review the value actually used in the account before introducing a separate spreadsheet convention. If the team changes or adds a campaign value, record the reason and the effect on the reports that use it. Do not assume every campaign name and tracking value remain identical over time.
Hypothetical example: A fictional email newsletter promotes an audit resource. The team chooses an example source, channel and campaign key. These values demonstrate the convention; they are not an approved Selworthy campaign.
| Parameter | Example value | Intended meaning |
|---|---|---|
| utm_source | example_newsletter | The fictional publication sending the visit. |
| utm_medium | The selected channel label. | |
| utm_campaign | example_audit_review | The fictional campaign key. |
| utm_content | example_intro_link | The link variation being compared. |
The illustrative URL is:
https://example.com/resources/audit?utm_source=example_newsletter&utm_medium=email&utm_campaign=example_audit_review&utm_content=example_intro_link
The example.com address is a placeholder, not a live resource or a citation. In production, use the verified destination and the account's approved values. The table makes the intended interpretation inspectable before a link is distributed.
Check that the link reaches the intended page, preserves the required parameters through redirects and does not produce an error. Review the final URL as well as the original link text.
Query-string test example: Start with the fictional destination https://example.com/resources/audit?view=summary and add the same approved example parameters. The expected test URL is:
https://example.com/resources/audit?view=summary&utm_source=example_newsletter&utm_medium=email&utm_campaign=example_audit_review&utm_content=example_intro_link
Verify that the existing view=summary parameter remains, the campaign values match the register and the URL has only one question mark. Do not blindly append another question mark to a destination that already has a query string. A tool may order the parameters differently; compare their parsed names and values rather than requiring an identical text order.
Then use an approved test to inspect how the visit is classified in the relevant reporting surface. Record the time, test conditions and observed result. Do not infer success solely because the landing page loaded.
Also inspect variations created by different team members or tools. A copied link with a changed campaign value may be valid technically while violating the naming contract. Keep those cases in the review rather than correcting historical data without a decision.
HubSpot's Google Ads tracking documentation describes its tracking parameters and restrictions on custom tracking settings at different levels. Read the Google Ads tracking requirements before changing that configuration.
Manual UTMs, connector-generated values and ad-platform tagging need to be assessed together for the actual setup. Do not delete or overwrite a parameter because it looks redundant. Determine which system owns it and what depends on it.
If your team is comparing CRM and ad reporting, use the context in HubSpot paid-search reporting. Naming consistency supports interpretation, but it does not make different attribution definitions identical.
Before distribution, compare the generated link with the approved campaign record. HubSpot tracking URLs should carry the intended source, medium and campaign value for that specific campaign. Test optional parameters only when they serve a real reporting question.
It can reach the same page, but reusing identical source and medium values may remove a distinction you intended to measure. Create the appropriate tracking URL for each approved use rather than editing a shared link informally.
Each campaign key should identify the intended initiative under your naming policy. That does not mean inventing a new source or medium for every link. Reuse the approved vocabulary so website traffic from different campaigns remains comparable.
No. It improves the interpretation of measured traffic sources. Campaign effectiveness, lead quality and revenue require additional evidence and report definitions. Keep those conclusions separate from the technical check that a tracking URL retained its parameters.
For each tracking URL, retain the destination, approved UTM parameters, campaign owner, distribution channel and verification date. Add a brief note explaining any exception. A unique identifier for the link can help the team find the exact version without confusing it with the campaign key.
If marketers use custom reports to compare traffic, include the source and medium definitions in the reporting notes. The same website traffic should not be grouped differently merely because one analyst recognizes an abbreviation and another does not.
Review the register before reusing links in a later campaign. Retired UTM codes may still be valid historical evidence even when they should no longer appear in new marketing efforts. Preserve them and explain the current replacement rather than rewriting the past.
Retain the approved vocabulary, campaign keys, generated links, test evidence and change history. Identify retired values and explain whether historical reporting should preserve them or group them under an approved rule.
We recommend reviewing a new value when it is requested, rather than waiting for a dashboard cleanup. The review should ask whether the value represents a real reporting distinction or only a spelling variation.
Discuss the media workflow through paid search and social services and the data dependencies through HubSpot operations. A useful taxonomy lets the next analyst explain a link without asking who created it.
Product documentation checked September 6, 2026. The URL and campaign values are synthetic, and no tracking settings or campaigns were changed.