6 min readTutorials

Short-Link Clicks vs GA4 Sessions: Why They Never Match

Your shortener counts 1,000 clicks and GA4 shows far fewer sessions. What each tool counts, why they diverge, and how to build your own baseline.

Marius Voß
DevRel · edge infra

A shortener counts a request. Google Analytics counts a session that a browser reported after its tag loaded. Those are different events, measured at different layers under different rules, so the totals won't agree and no setting will make them agree.

The useful question isn't "why aren't they equal" but "is the gap stable". This post walks the path from click to session, names each place the count changes, and ends with a reconciliation you can run in an afternoon. If you haven't wired the tagging yet, track UTM parameters end to end comes first. If the gap is caused by campaign data disappearing, read browsers that strip UTM parameters next.

The Two Numbers Count Different Events

A click is recorded when a request arrives at the redirect, and the response is a 301 or 302 with a Location header, finished in milliseconds. Nothing in that exchange requires a human, a rendered page or JavaScript.

A GA4 session starts when a session_start event reaches Google from a browser that loaded your tag. Google defines a session as a period of user interaction that ends after 30 minutes of inactivity by default (accessed 2026-10-24). It's a client-side construct, not a count of arrivals. Between the redirect and that event sit the DNS lookup, the TLS handshake, the HTML response, the tag manager, the consent check and the visitor's patience.

Every one of those is a place where a click exists and a session doesn't. That's the gap.

What Inflates the Click Side

Automated traffic is the biggest contributor, and it's uneven across channels.

Mail security scanners. Corporate filters open links in a message before it reaches the inbox, and some rewrite them first. The fingerprint is a burst of clicks on every link in a campaign within seconds of delivery. Outlook Safe Links rewriting covers what that scanner does to the URL.

Link preview fetchers. Paste a link into Slack, Teams, WhatsApp or a social composer and the platform fetches it to build a card. Post one link in five channels and you may have five requests before anyone reads it.

Uptime and security monitors. Anything you added to a monitoring check keeps requesting the link on its schedule.

Crawlers. Search crawlers have always followed redirects, and so do AI agents. What AI crawlers do with short links goes through which ones follow a redirect.

What Elido does about it, checked against the edge-redirect source: the redirect compares the request's User-Agent with a fixed list of substrings (generic bot, crawler and spider, named preview fetchers such as slackbot, whatsapp and facebookexternalhit, monitors such as uptimerobot and pingdom, and HTTP clients such as curl/ and python-requests). A match still gets the redirect, so previews work, but no click event is written. That means the dashboard number is filtered before storage, and there is no stored "raw" count to compare it against.

The limit matters for you: a scanner that sends an ordinary browser User-Agent isn't on that list. Treat the filtered count as "known bots removed", not "humans only". What to measure in short-link analytics covers the difference.

The path from a click on a short link through the redirect and the destination page to a GA4 session, with bot traffic, abandonment and consent removing volume at each stage

What Deflates the Session Side

Now the other direction: a real person clicked and GA4 recorded nothing.

Consent is the largest cause for a European audience. When analytics consent is denied, the tag either doesn't run or sends cookieless pings that standard reports don't treat as sessions, depending on how you configured Consent Mode. Consent Mode v2 for tracking covers what survives a denial.

Then the mechanical losses. Ad blockers and tracking protection stop the tag from loading. A slow destination page loses people during the load, and a click that never reaches session_start isn't a session. Add container misconfiguration on one template, in-app browsers behaving oddly, and landing pages that redirect again before the tag fires.

Sessions Merge, Clicks Do Not

This one is structural, and it's why exact reconciliation is impossible.

Send a newsletter with four links. One reader clicks three of them within ten minutes. That's three clicks and one session, and both numbers are correct. The more links a campaign contains, the wider the ratio, with no fault anywhere. The same shape is why per-touch credit under different attribution models needs click-level rows, not session totals.

The 30-minute inactivity window works the same way. Someone who clicks, reads, and returns two hours later produces two sessions from two clicks. Someone who clicks twice in five minutes produces one.

If your ratio moves after a campaign redesign and nothing else changed, count the links per message before you hunt for a bug.

When the Query String Does Not Survive

A separate failure: the session is recorded but the campaign isn't, so your shortener says 800 clicks from the newsletter and GA4 shows 800 sessions of direct traffic.

The cause is usually on the destination side. A redirect from /page to /page/ that drops the query string, a hosting rule that strips unknown parameters, or a link that never carried UTM parameters at all. Some browsers remove specific tracking parameters too, a different mechanism with the same symptom. The catch: Firefox's documented strip list is mostly ad and email identifiers rather than utm_ tags, which the browsers post goes through.

Diagnosis takes two minutes. Open the short link and watch the final address bar. If the parameters are gone, the fix is on the destination host, not in the shortener. Why UTM parameters don't show in GA4 walks the full decision tree.

Four sizes of gap between clicks and sessions mapped to their most likely cause and the check that confirms it

A Reconciliation You Can Run in an Afternoon

Work in this order. Each step removes one class of cause.

  1. Click your own link once from a phone on mobile data and confirm a matching session appears in GA4 DebugView with the campaign attached. If that fails, nothing downstream is measurable.
  2. Export the click log for one link (the link detail page has a CSV download) and scan the User-Agent and country columns for bursts of identical clients seconds apart. That's your estimate of scanner traffic that got past the bot list.
  3. Segment by referrer. Email usually shows the widest ratio, your own website the narrowest, chat platforms in between.
  4. Check your consent acceptance rate for the period and see how much of the gap it explains on its own.
  5. Count links per campaign. If the ratio moved when the template changed, you have your answer.

What Ratio Is Actually Normal

I'm not going to give you a benchmark, because any single figure ignores channel mix, mail infrastructure, consent rate and links per message. So build your own. Record clicks and sessions per campaign for a month, calculate the ratio, and write down what normal looks like per channel. A newsletter that always runs at 1.4 clicks per session and suddenly reads 3.2 has a scanner problem or a broken landing page, and you'll see it within a day.

Once you accept that, the job is putting both numbers in one report without either looking wrong, which is what a Looker Studio dashboard on a shared join key is for. To see the click side with known bots already removed, Elido's link analytics is where to start.

Read the Cornerstone Series

This post sits in the tutorials cluster. The full chain from link creation to a report you can defend is in track UTM parameters end to end.

Frequently asked questions

Why does my link shortener show more clicks than Google Analytics?

Because the two systems count different events at different points. A shortener counts a request that reaches the redirect. GA4 counts a session only after its tag loads in a browser and consent allows it. Link scanners, visitors who leave before the page renders, ad blockers and denied consent all sit in the gap between those two points.

What is a normal difference between clicks and sessions?

There is no universal figure, and I won't quote one. The ratio depends on channel, audience, consent rate and links per message. Measure clicks and sessions per campaign for a month, write down the ratio for each channel, and treat a sudden move in it as the signal.

Do bots inflate short link click counts?

They can, depending on the tool. Elido's edge redirect matches the User-Agent against a list of known crawlers, preview fetchers, uptime monitors and HTTP clients, and still serves the redirect but records no click. Scanners that present an ordinary browser User-Agent are not caught by a list like that, so some automated clicks can still be counted.

Does a redirect create a new GA4 session?

No. A redirect is a server response, not a page view, so GA4 counts nothing until the destination page loads and the tag sends session_start. The redirect only matters if it loses the campaign parameters on the way.

Why do my clicks show up as direct or none in GA4?

Usually the query string didn't survive. If the destination URL has no UTM parameters, or a redirect on the destination host drops them, GA4 has no campaign to attribute the visit to. The tag fired correctly; the campaign data never arrived.

Can I make clicks and sessions match exactly?

No. One person clicking three links in one newsletter is three clicks and one session by design. Aim for a stable ratio you understand, so you notice the day it moves.

Try Elido

Paste a URL, get a working short link

No signup. Link lives for 30 days. Sign up to keep it forever.

Free account required. The free plan includes 25 links in total. Already have an account? Log in

Try Elido

EU-hosted URL shortener with custom domains, deep analytics, and an open API. Free tier - no credit card.

Tags
clicks vs sessions
ga4 sessions
click tracking discrepancy
bot clicks
utm parameters
link analytics

Continue reading