Your website privacy choices

Essential storage supports sign-in and remembers your choice. Vercel Analytics and Speed Insights help us understand website use and performance. They stay off unless you allow analytics. Advertising consent is not requested here.

Cookie policy · Privacy policy. This choice does not change connected businesses’ server-side integrations.

Omesta
How it worksAd creationReviewsPricingCase studies
Log inGet started
How it worksAd creationReviewsPricingCase studiesLog inGet started
Attribution

A UTM Naming Convention for Cleaner Campaign Reports

Build a practical UTM naming convention for paid campaigns, prevent fragmented reports, and test links without putting customer information into URLs.

By Omesta team

May 31, 2026|4 min read

Color-coded blank tags form an orderly repeating naming pattern.

On this page

  • Define a small vocabulary
  • Keep an ID-to-name registry
  • Build and test the full customer path
  • Keep customer information out of campaign URLs
  • How Omesta helps with making campaign reviews easier to follow
  • Frequently asked questions
On this page
  • Define a small vocabulary
  • Keep an ID-to-name registry
  • Build and test the full customer path
  • Keep customer information out of campaign URLs
  • How Omesta helps with making campaign reviews easier to follow
  • Frequently asked questions

A useful UTM naming convention gives every campaign link consistent source, medium, campaign, and creative identifiers. The aim is a report that can be grouped reliably, not the longest possible tracking URL.

Google Analytics uses campaign parameters to identify referring campaigns, and parameter values are case-sensitive. A naming rule helps prevent one campaign from appearing under several spellings. Google Analytics URL builder guidance.

Define a small vocabulary

Start with the questions you need to answer: which channel brought the visit, which campaign it belonged to, and which creative generated the click. Agree on the allowed values before producing dozens of links.

Here is an illustrative internal convention, not a required Google standard:

FieldExample valueTeam rule
utm_sourcefacebookUse the actual publishing source
utm_mediumpaid_socialKeep one spelling for the channel
utm_campaignroofing_margin_checkDescribe the stable campaign concept
utm_contentroof_photo_aDistinguish the creative variant

Use lowercase consistently. Choose one separator, avoid casual abbreviations, and document changes. A new employee should be able to create a link without guessing what last month's campaign manager meant.

Keep an ID-to-name registry

A campaign can be renamed without becoming a new campaign. If your reporting depends on names alone, a cosmetic change can look like two different efforts.

Keep a registry containing the platform campaign ID, approved reporting name, destination, launch date, and owner. Where you use supported dynamic URL parameters, verify what they resolve to instead of assuming the editor's placeholder is the final value.

For a team running several platforms, decide whether your comparison should happen at the campaign-concept level or the individual platform-campaign level. Both can be useful, but they need separate identifiers rather than one overloaded name.

Two systems of modular campaign tags, one arranged by color and another linked as a fine code pattern.
Conceptual illustration: Keep stable campaign identifiers alongside readable labels, and preserve the tagging methods your reporting relies on.

Build and test the full customer path

A hypothetical link could look like this:

https://example.com/check?utm_source=facebook&utm_medium=paid_social&utm_campaign=roofing_margin_check&utm_content=roof_photo_a

Open the final link, follow any redirect, and confirm that the intended page loads. Then check the appropriate analytics view after allowing for processing. Confirm the source, medium, and campaign are represented as intended.

If the page already has query parameters, append correctly rather than adding a second question mark. Test links copied into real ads and emails, not just the clean version in your spreadsheet. A redirect or link wrapper can change the destination.

Keep Google Ads auto-tagging and platform click identifiers intact where your measurement setup uses them. A UTM convention should complement the existing setup, not accidentally replace it.

Keep customer information out of campaign URLs

Never use a person's email, phone number, or name as a campaign identifier. URLs can be recorded by analytics, browser history, logs, and other systems. Google's Analytics policy specifically warns against personal information in URLs and campaign parameters. Google's PII guidance.

Use non-personal campaign labels instead. Keep CRM identity matching inside an appropriately configured system, with the necessary permissions and safeguards, rather than improvising it through URL fields.

A plain smartphone displays a simple privacy lock symbol in soft architectural light.
Campaign URLs should describe the campaign, not identify the person visiting it.

How Omesta helps with making campaign reviews easier to follow

Use Omesta’s connected campaign reporting alongside your UTM naming registry. Consistent labels can make it easier for your team to explain which campaign a report refers to. Omesta does not automatically enforce the naming convention in this guide or repair every destination URL; keep ownership of the link registry explicit.

Explore the AI ad-management workflow for current capabilities and the pricing page for plan limits.

Frequently asked questions

Will UTMs make platform and analytics reports identical?

No. They label traffic; they do not remove differences in attribution, consent, event definitions, or reporting periods.

Should I tag links between pages on my own site?

Use ordinary internal navigation links. Treat UTMs as acquisition labels rather than a replacement for tracking internal navigation behavior.

Can the same creative name appear in different campaigns?

Yes, if your registry and reporting distinguish the campaign as well. What matters is an unambiguous combination, not a globally unique phrase for every field.

Audit a few existing links before changing the whole account. For a broader measurement-tool comparison, see our ad-tracking alternatives guide, or explore Omesta.

Put the guide into practice

See how this ad-management workflow fits your business.

AI ad management
All articles

Related articles

View all articles
Attribution

Brand vs Non-Brand Search: Separate Demand Before Comparing

Separate branded and non-brand search reporting so existing awareness does not hide acquisition performance, while keeping attribution distinct from causation.

Read more
Attribution

Conversions Arrive Late: Read Recent Ad Results Carefully

Separate customer decision time, reporting delays, and missing events before judging recent campaign CPA or comparing incomplete lead cohorts with mature ones.

Read more
Attribution

UTMs vs Auto-Tagging: What Each Adds to Your Ad Reports

Understand manual UTM labels and Google Ads auto-tagging, decide where each is needed, and test redirects without leaking customer information into URLs.

Read more

Put your next idea to work

Bring your ad decisions into one place.

Explore your advertising performance with a 14-day free trial.

Explore Omesta See pricing

Solutions

  • Local businesses
  • E-commerce
  • Marketing agencies

Product

  • How it works
  • AI ad management
  • Ad creation
  • Integrations
  • Pricing
  • Reviews
  • Changelog

Compare

  • Omesta vs Ad Agency
  • Omesta vs Media Buyer
  • Omesta vs DIY Ad Stack
  • Omesta vs Advantage+
  • Omesta vs Performance Max
  • Omesta vs OpenAI Ads Manager

Customers

  • Case studies

Learn

  • Blog
  • Glossary
  • Help center

Company

  • About
  • Partners
  • Press
  • Careers
  • Status

Follow us

  • X (opens in a new tab)
  • Instagram (opens in a new tab)
  • TikTok (opens in a new tab)
  • Facebook (opens in a new tab)

  • Privacy
  • Terms
  • Refund policy
  • Cookies
  • GDPR
  • Data disclosure
  • Data deletion
  • Security

© 2026 Omesta Systems.