How Short Links Work: Redirects, Clicks, Analytics and QR

You do not need to be an engineer to sell short links, but you do need to explain them without hand-waving — to a prospect on a demo call, and to a client who asks why their click numbers differ from another tool's. This lesson walks through the machine once, end to end, in plain language. After it, nothing in the product will feel like magic.

The life of one click

Take a real example. A client of yours — say, a boutique running an SMS campaign — sends the link go.boutique.com/vip to two thousand customers. One of them taps it. Here is everything that happens next, in order:

1. The phone asks DNS where go.boutique.com lives. The answer points at the platform's redirect servers, because the client's domain was connected once, during setup, with a CNAME record. The domain belongs to the boutique; the servers behind it are the product you resell.
2. The redirect server receives the request and sees two things: the domain it arrived on and the path /vip. Together they identify exactly one link in exactly one workspace — two different clients can both have a /vip link on their own domains without ever colliding.
3. The server looks up the destination and checks the link's settings: is it expired, is it password-protected, does it have rules like "visitors from Germany go to the German page"? Rules are evaluated right here, at redirect time.
4. The click is recorded — timestamp, country and city derived from the network address, device type, browser, operating system, referrer, and any UTM parameters. This happens in parallel with the redirect, not before it, so measurement never slows the visitor down.
5. The browser receives the redirect and loads the destination. Total elapsed time: a few tens of milliseconds. The visitor never notices a middleman existed.

That is the whole trick. Every feature in the product is a variation on one of these five steps: traffic rules and geo targeting extend step 3, analytics is step 4 made visible, A/B testing makes step 3 pick between destinations.

Where analytics numbers come from — and why they differ between tools

Every dashboard number a client sees is an aggregation of step 4 records. That has two practical consequences worth understanding now, because clients will ask about both.

First: a click is not a visit. The shortener counts requests that reached the redirect server. The destination site's analytics counts pages that finished loading with a tracking script. Between the two sit people who closed the tab mid-load, browsers with script blockers, and slow connections. The shortener's number is normally the higher one, and both are correct — they measure different lines of the same funnel.

Second: not every request is a human. Messengers and social networks fetch links to build previews; monitoring services probe them; crawlers follow everything they see. A good shortener classifies this traffic and separates it, so a link pasted into a chat with fifty people does not report three hundred "clicks" from preview bots. When a prospect compares tools, this filtering quality is one of the honest differentiators — see bot traffic and click quality for how it works.

Branded domains: the part clients actually see

Everything above runs on whatever domain the link uses. The difference between a generic shortener and yours is whose name is in that domain — and connecting one is a five-minute DNS task, not a technical project. A subdomain like go.boutique.com needs a single CNAME record; a bare domain like boutique.link needs an A record pointing at an issued address. TLS certificates are provisioned automatically once the record is verified. The step-by-step instructions your clients will follow live in the docs: connecting a subdomain with CNAME and connecting an apex domain by IP.

Why this matters commercially: the domain is what makes short links branded, and branding is what people pay for. It is also a switching cost in your favour — once a client's domain has thousands of printed QR codes and published links on it, the links keep working only while the domain stays connected to a service. That service is yours.

QR codes: the same link, drawn as a square

A QR code is not a separate system. It is a short link encoded as an image: scanning it opens the same URL, runs the same redirect, records the same click with the same analytics. Three things follow from that, and all three are selling points:

• A printed QR code is editable. The ink encodes the short link; the destination lives on the server. A restaurant that printed table stickers can replace its menu weekly without reprinting anything.
• Offline campaigns become measurable. A poster in one district and a flyer in another can carry different short links, and the dashboard shows scans per location, per day, per device — numbers print advertising never had.
• Design is safe to customise. Colours, a logo in the centre, styled corners — the QR feature handles error correction so a branded code still scans reliably.

What runs without anyone watching

A few mechanics work silently in the background, and knowing they exist saves you from awkward demo moments. Expired links and password-protected links are enforced at step 3 — a client can set a campaign to end on a date and it simply stops. Deep links route mobile visitors into apps instead of websites where configured. And every redirect happens on infrastructure built for it: the platform's uptime target for the redirector is 99.99%, because a shortener that drops clicks is worse than no shortener — the clicks it loses are precisely the ones someone paid to generate.

You resell all of this as-is. Your job is never to build or operate the machinery — it is to explain it confidently, which after this lesson you can.

Check yourself

• [ ] Close this page and write down the five steps of a click from memory, in order. If you lose one, reread that section — this sequence is your demo script.
• [ ] Explain in two sentences why the shortener's click count can be higher than the destination site's visit count, and why neither number is wrong.
• [ ] Explain what physically changes when a client "edits the destination" of a printed QR code — and what does not change.
• [ ] Open the QR code generator, make a code for any page, scan it with your phone, and trace which of the five steps just ran.

Next up: who owns which part of this machine — white-label and the reseller model, the lesson that turns a product into your business.