Why visits from your UTM links show up as direct or unassigned

UTM-tagged visits show up as Direct or Unassigned when the tags never reach your analytics, or arrive in a form it cannot classify. Common causes are redirects that drop the query string, tags placed after a #, inconsistent or misspelled parameter names and values, and visitors whose analytics did not load. Test the final landing URL first.

1. The tags are lost on the way

• Redirects. http → https, non-www → www or a trailing-slash redirect should keep the query string, but misconfigured ones drop it. A link shortener or app redirect can do the same.
• Tags after a #. Parameters must come before any fragment: /page?utm_source=x#section, not /page#section?utm_source=x. Anything after # is not sent to the server and is usually not read as a campaign parameter.
• A second ? in the address. If the URL already had a query string, add tags with &, not another ?.
• Privacy tools. Some browsers, extensions and apps remove tracking parameters from links, and some email security services rewrite links. You cannot control these; expect some loss.

Test: click your tagged link from where people will click it — the email, the app, the QR code — and look at the address bar when the page has loaded. If the tags are gone, a redirect removed them. Paste the final URL into the URL Decoder to see each parameter separately.

2. The values do not match your channel rules

• Misspelled names. utm_soruce or utm-source is ignored. Only the exact parameter names work.
• Missing source or medium. Analytics tools need both to attribute a visit properly.
• Mediums your analytics does not recognise. Channel groups classify traffic by medium values such as email, social, cpc or referral. A medium like “newsletter-oct” or “Email” may fall into Unassigned. Check your analytics tool’s channel definitions and use matching values.
• Inconsistent case. “Facebook” and “facebook” are reported as different sources. Keep everything lower-case.

The UTM Link Builder fills in the exact parameter names, lower-cases values by default and encodes them properly, which removes most of these errors.

3. Analytics did not run

• Consent. Where analytics loads only after cookie consent, visitors who decline are not counted at all, or are counted without campaign data, depending on the setup.
• Blockers. Ad and tracker blockers stop many analytics scripts.
• Fast bounces. A visitor who leaves before the page and its scripts finish loading may not be recorded.

QR codes and printed links

For posters and leaflets, encode the full tagged URL in the QR code, or point the code at a short address on your own domain that redirects to the tagged URL. In both cases, scan the printed code and check the address bar on the phone before printing in bulk. Redirect services and some QR scanners alter links, so test with more than one phone.

4. Tags used where they should not be

Do not put UTM tags on links between pages of your own site. In many analytics setups a new campaign value starts a new session or overwrites the original source, so the visitor’s real origin is lost. Use UTMs only on links that bring people in from elsewhere: emails, social posts, adverts, partner sites and printed material.

Mistakes to avoid

• Testing the tagged link in a browser but never through the real redirect or app.
• Inventing new medium values for every campaign.
• Tagging internal links or navigation.

Checklist

• Tags visible in the address bar after the final redirect?
• Tags before any #, joined with & when a query already exists?
• Exact parameter names, lower-case values, source and medium both set?
• Medium values match your analytics’ channel rules?

For the basics of building tagged links, see UTM parameters explained.