Skip to main content
← Back to the blog

Guides

UTM tracking: tag campaigns so the source reaches your CRM

Published November 7, 2026 · 8 min read

FFlowgrationGUIDESUTM tracking: tagcampaigns so the sourcereaches your CRM

You run an Instagram campaign, a newsletter and some Google ads, and at the end of the month someone asks which channel brought the customers. If the links were not tagged, the answer is usually "direct" or "we don't know". UTM parameters fix that part, as long as you use them consistently and the data reaches the CRM, where your contacts, deals and sales live.

This guide covers how to name your UTMs, which mistakes break reports and how the source of a visit moves onto the contact record.

Key takeaways

  • UTMs are five parameters added to the end of a link: utm_source, utm_medium, utm_campaign, utm_term and utm_content.
  • What breaks reports most is inconsistency: "Facebook", "facebook" and "fb" end up as three sources. Use lowercase and a shared naming table.
  • Flowgration's tracker reads the UTMs from the landing page and stores them with the session. The URL itself is stored without parameters: path only.
  • When a visitor who has consented identifies themselves (for example by submitting a form), their first touch is copied to the contact's empty fields.
  • With that data, CRM reports can answer which channel brings contacts, deals and revenue, not just visits.

What are UTM parameters and what are they for?

They are tags you add to a URL to record where the click came from. For example:

https://yourshop.com/sale?utm_source=newsletter&utm_medium=email&utm_campaign=winter-sale

The page is the same with or without them. The difference is that your analytics tool knows the visit came from the winter sale newsletter. Without a tag, a visit from an email app or a social app can show up as direct traffic, because many apps do not pass on the referring page.

What does each parameter mean?

ParameterAnswersExamples
utm_sourceWho sends the traffic?google, instagram, newsletter, partner-x
utm_mediumWhat type of channel?cpc, email, social, paid-social, referral
utm_campaignWhich campaign or push?winter-sale, march-webinar, bundle-launch
utm_termWhich keyword or audience? (optional)ecommerce-crm, lookalike-customers
utm_contentWhich ad or link version? (optional)blue-banner, footer-button, video-15s

The first three are the ones you need on every link. utm_term and utm_content help compare variants within one campaign.

How should you name UTMs so reports stay clean?

The rules that work for a small team are few and simple:

  1. Everything lowercase. Many tools are case-sensitive, so Email and email count as different mediums.
  2. Hyphens instead of spaces. winter-sale, not Winter Sale. Spaces get encoded differently depending on where the link is pasted.
  3. A closed list of mediums. Agree on five or six values up front (cpc, email, social, paid-social, referral, qr) and don't add new ones without agreement.
  4. The source is the site, not the format. instagram is the source; paid or organic goes in the medium.
  5. Campaign names you will understand in six months. Add the month or season if the campaign repeats.
  6. Never tag internal links. A UTM on a link inside your own site restarts the visit's source and spoils attribution.

Keep the naming table in a shared document and build links from it, not from memory.

Common UTM mistakes

  • Mixing case and abbreviations (FB, facebook, Facebook). The fix is the closed list.
  • Tagging internal links, such as the menu button that leads to the pricing page.
  • Forgetting to tag the newsletter. Email is one of the channels that produces the most "direct" traffic when links carry no parameters.
  • Putting personal data in the URL, such as the subscriber's email. URLs end up in logs, browser history and third-party tools. Never do it.
  • Renaming a campaign halfway through. The data splits into two rows.

What happens to UTMs when they reach your site?

In Flowgration the path looks like this:

  1. The tracker reads utm_source, utm_medium, utm_campaign, utm_term and utm_content from the URL of the page viewed and sends them with the visit, together with the referring page.
  2. The server stores the URL without parameters. For each page only the path is kept (/sale), with no query string or fragment. The UTMs are extracted first and stored separately, so nothing else that travels in the URL ends up in your data.
  3. The session keeps its source. In consent mode, each session stores its landing page, referring domain and UTMs. The sources report uses the UTM source or, if there is none, the referring domain; with neither, the session counts as direct.
  4. The visitor keeps their first touch. The first landing page, the first referring domain and the first utm_source, utm_medium and utm_campaign stay attached to the visitor.
  5. On identification, the first touch moves to the contact. When that visitor submits a form that reaches Flowgration, or you identify them with identify, their first touch is copied to the record: landing page, referrer, source, medium and campaign. Only empty fields are filled; nothing you already had is overwritten.

Identification only happens for visitors who accepted analytics in consent mode. In cookieless mode there are no sessions or visitors, so you can count visits per campaign in aggregate but cannot link them to contacts. The cookieless web analytics guide explains the trade-off.

What if the lead arrives through a form?

Flowgration's native forms support hidden fields that the browser fills with utm_source, utm_medium, utm_campaign, utm_term, utm_content, the Google Ads gclid, the page URL or the referring page. Each hidden field is saved to the matching attribution field on the contact. This helps when the visitor has not accepted analytics: the form still sends the campaign source because it is part of what the visitor submits to you.

If you use a different form tool, see the guide to connecting web forms to your CRM and add the same hidden fields.

Why keep the source in the CRM and not only in analytics?

An analytics tool tells you a campaign brought visits. The CRM can tell you whether those visits became contacts, deals and sales. With the first touch saved on each contact you can:

  • Segment contacts by the campaign that brought them.
  • Show deals and revenue by first-touch channel on a dashboard.
  • Use the revenue attribution report, which splits credit across touchpoints with several models (first touch, last touch, linear, U-shaped and time decay).

Your analytics tool and your CRM will not always show the same figures, and that is normal; we explain why in why GA4 and CRM numbers differ.

Checklist before launching a campaign

  • Source, medium and campaign taken from the naming table.
  • Everything lowercase, with hyphens.
  • Link tested: it opens the right page and the parameters show in the address bar.
  • No personal data in the URL.
  • Landing page forms carry hidden UTM fields, if you use them.
  • A test visit in a private window, accepting cookies, to see the source in the dashboard (data is processed every 5 minutes).

Frequently asked questions

Do UTMs affect SEO?

They shouldn't, as long as you only tag external links (ads, emails, social posts) and your page has a canonical URL. What you should avoid is tagging internal links.

Which UTMs are required?

None technically, but in practice always use utm_source, utm_medium and utm_campaign. Without all three, channel reports are incomplete.

Is the Google Ads gclid stored?

The web tracker does not store it on visits, because URLs are stored without parameters. Native forms can capture it in a hidden field and save it on the contact, and the attribution report uses it to recognise a Google Ads click when there are no other UTMs.

Which source is kept if someone returns from another campaign?

Each session keeps its own source. The contact gets the first touch, and only if those fields were empty. To see every touchpoint of a customer, use the attribution report.

How Flowgration does it

Flowgration has its own tracker that reads UTMs from the landing page, stores the source per session and the first touch per visitor, and copies it to the contact record when a consenting visitor identifies themselves. Native forms can carry hidden UTM and gclid fields. With that data you get source and campaign reports in web analytics, dashboards with deals by channel and the revenue attribution report.

Limits worth knowing: without consent there are no sessions and no link to contacts; cookieless mode gives aggregate data only; the contact receives the first-touch source, medium and campaign, but not utm_term or utm_content (those are visible on the sessions). Page analytics is available from the Essential plan and visitor identification from Growth; see the plans.

Build your WooCommerce CRM in 60 seconds

Flowgration turns your store's orders into a living CRM and runs email, SMS and WhatsApp on autopilot. Free up to 500 contacts.

Start free