Click Tracking

Click tracking captures data at the moment of every link interaction — before the redirect completes — recording who clicked, from where, on what device and at what time.

---

Definition

Click tracking is the process of recording contextual data about every interaction with a link at the moment the click occurs. In URL shorteners, click tracking happens server-side: when a visitor's browser requests the short link, the server captures data from the HTTP request headers before issuing the redirect response.

Because tracking occurs at the server during the redirect, it is independent of anything that happens at the destination page — no JavaScript tag required on the destination, no cookie consent interaction needed. The click is recorded whether or not the visitor has an ad blocker, whether or not the destination page loads correctly, and whether or not the visitor takes any action after arriving.

How Click Tracking Works Technically

Every HTTP request contains header fields that identify the requesting client. When a short link is clicked, the shortener's server reads:

• User-Agent header. A string identifying the browser, browser version, rendering engine, operating system and OS version. Parsed to determine device type (mobile/desktop/tablet), OS (iOS, Android, Windows, macOS) and browser (Chrome, Safari, Firefox, Edge).
• Referer header. The URL of the page from which the click originated — the referrer. Used to identify traffic source: direct (no referer), email platform, social media, search engine or specific referring URL.
• Accept-Language header. The visitor's browser language preference — used as a proxy for interface language and locale.
• IP address. The connecting IP is used for geographic lookup (country determination via geo-IP database), then discarded in GDPR-compliant implementations. Only the country result is retained.

This data is assembled into a click event record and stored associated with the link. The redirect response is then issued. Total processing time: under 10 milliseconds in normal operation.

What Click Tracking Does Not Capture

Click tracking at the URL shortener level captures the click event and its context. It does not capture:

• What the visitor did after arriving at the destination (page scroll, form submission, purchase) — that requires destination-side analytics
• Whether the visitor converted — that requires conversion tracking at the destination
• The visitor's identity — no name, email or account association is made
• Click-to-open rate in email — that requires the email platform's own tracking

For downstream behaviour, click tracking at the link level is complemented by passing UTM parameters through to the destination URL, connecting link-level click data to page-level behaviour data in GA4 or similar platforms.

Server-Side vs Client-Side Tracking

URL shortener click tracking is server-side — it operates at the HTTP redirect step before the destination page is loaded. This gives it several advantages over client-side (JavaScript) tracking:

• Ad blocker resistant. Ad blockers block JavaScript tracking tags on pages; they cannot block server-side redirect tracking because the request hits the shortener's server before any page-side code runs.
• No destination page dependency. The click is recorded even if the destination page fails to load, has a broken analytics tag or is slow to render.
• No cookie required. Server-side redirect tracking does not set or read cookies — relevant for GDPR compliance and cookieless tracking environments.

Privacy and GDPR Compliance

GDPR-compliant click tracking stores aggregate, anonymised data. The IP address used for geographic lookup is not retained — only the derived country value is stored. No personally identifiable information is associated with individual click records. Cuttly's click tracking operates on this basis: data collected is aggregate and anonymised, not individually identifiable.

Related Terms

• Link Analytics
• Unique Clicks
• Bot Click Detection
• Referrers
• UTM Parameters
• GDPR & Analytics