The Complete Guide to Link Analytics Every Metric, Every Channel, Every Insight in 2026

Every click on every link you share tells you something. Something about who your audience is, where they are, what device they are holding, what time of day they engage, and which of your channels actually works.

Most marketers read only one number: the total click count. Then they wonder why their campaigns plateau, why their channel mix is guesswork and why they cannot explain to management which activity drove which result.

This guide covers everything. Every dimension of link analytics, how each metric is measured, what it means in practice, how to connect it to GA4, and how to use it to make decisions that actually improve performance.

---

What Is Link Analytics?

Link analytics is the measurement and analysis of engagement with a hyperlink — tracking who clicked it, when, from where, on which device, via which source, and how many times.

It works at the redirect layer. When a visitor clicks a Cuttly short link, their browser sends an HTTP request to Cuttly's server. Before the redirect is executed — before the visitor reaches the destination — Cuttly's server reads the request headers, derives analytics values from them, records the click event, and returns the redirect response. The entire tracking process completes in milliseconds, invisibly, before the visitor is forwarded.

This architecture has three significant implications:

• No destination page code required. Unlike Google Analytics, which requires a JavaScript tracking snippet on every page, link analytics tracks every click regardless of what the destination page contains or whose domain it is on. You can track clicks to third-party pages, PDF files, app store listings, WhatsApp click-to-chat links — anything with a URL. A URL shortener is all the setup required.
• Cookie-free by design. The tracking happens server-side at the HTTP request level. No cookie is set on the visitor's device. Link analytics is unaffected by cookie consent rejections, ad blockers, or the deprecation of third-party cookies that is reshaping the rest of digital analytics.
• Works for all channels. Email, SMS, QR Codes, social media, print — every channel that can carry a URL can be tracked with link analytics. Channels like email and SMS that produce no referrer data (and are therefore invisible to Google Analytics without UTM tags) are fully tracked at the click level.

The Eight Dimensions of Link Analytics

A single click event contains eight distinct analytics dimensions, each derived from the HTTP request at redirect time:

All stored values are aggregate and anonymised — raw data (IP addresses, full User-Agent strings) is used to derive these values and then discarded. No personally identifiable information about individual clickers is retained. Cuttly is GDPR compliant.

Total Clicks vs Unique Clicks — Why the Difference Matters

Every link in Cuttly tracks two click counts simultaneously: total clicks and unique clicks.

Total clicks counts every HTTP request to the short link URL — every click, including repeat clicks from the same visitor and automated requests from bots and security scanners.

Unique clicks deduplicates repeat visits from the same visitor within a time window — approximating the count of distinct people who clicked the link. Unique click deduplication in Cuttly uses a combination of IP address and User-Agent as a probabilistic identifier. This is less precise than cookie-based unique visitor identification, but it is privacy-preserving and works across all channels including email and SMS where cookies cannot be set before the page loads.

When to use each:

• Use total clicks to measure raw engagement volume — how many times the link was accessed. Relevant for understanding absolute traffic driven by a campaign.
• Use unique clicks to measure audience reach — how many distinct people engaged. Relevant for comparing campaign performance across campaigns with different distribution sizes and content types.
• Use the ratio (total ÷ unique) to measure re-engagement. A ratio above 1.5 suggests high-interest audience behaviour — people returning to the same link multiple times, which is common for navigation links, resource hubs and frequently referenced content.

Unique click counting must be explicitly enabled per link in Cuttly settings (Single plan and above). Once enabled, the link displays both total and unique click counts in analytics.

Device Analytics — Knowing Your Audience

Device analytics reveals the physical context in which your audience encounters and acts on your links. It is one of the most actionable dimensions — it directly informs channel strategy, content format decisions and mobile optimisation priorities.

Device Type: Mobile vs Desktop

The device type split (Mobile / Desktop / Tablet) shows the primary environment of your link audience. In most marketing contexts in 2026, mobile dominates — but the specific split matters for decisions:

• A campaign showing 90%+ mobile means the destination page experience on mobile is the only one that matters for the majority of visitors — desktop experience is secondary.
• A B2B email campaign showing 60% desktop reflects the reality that most business email is read at a desk during working hours.
• An SMS campaign showing 98%+ mobile is expected — SMS is inherently a mobile channel.

OS and Version: iOS vs Android

The OS breakdown — and specifically the iOS vs Android split — tells you which mobile platform your audience is on. This matters for:

• App development priority. If 75% of your mobile audience is on iOS, iOS app quality is more commercially important than Android parity.
• Mobile redirect configuration. Cuttly's device targeting (mobile alternative redirects) routes iOS and Android visitors to different destinations — App Store vs Google Play, platform-specific content, iOS deep links vs Android deep links. The OS analytics data tells you which platform routing matters most.
• Demographic inference. iOS-dominant audiences skew toward higher-income demographics in most Western markets. Android-dominant audiences reflect a wider demographic range globally and are the majority in many emerging markets.
• OS version data reveals how current your audience's devices are — relevant for progressive web app support and mobile feature compatibility decisions.

Browser and Version

Browser analytics shows which browsers your audience uses with version-level granularity. Chrome Mobile, Safari, Facebook in-app browser (Facebook 519.0 etc.), Samsung Internet, Chrome Desktop — each tells you something. The in-app browser data is particularly interesting: a large proportion of traffic via the Facebook in-app browser suggests your link is being shared and clicked within the Facebook app itself, which affects how you should think about the experience visitors have (in-app browsers behave differently from native browsers, with limitations on cookies, JavaScript and some web features).

Device Brand and Model

Cuttly's analytics includes device brand and model breakdown — Samsung Galaxy S25 Ultra, iPhone 16 Pro, and so on. This granular data is available in the PDF report and reveals the premium vs mid-range mix of your mobile audience. An audience clicking predominantly on current flagship devices has different purchasing power characteristics than one clicking on mid-range devices from two or three years ago.

Country Analytics — Geographic Intelligence

Country analytics shows where in the world your link clicks come from. Cuttly derives country from geo-IP lookup at redirect time — the IP address is used only for this lookup and then discarded. Only the country-level aggregate is stored.

Country data produces two categories of insight:

Confirming Expected Distribution

For most campaigns, the top country result should be your primary target market. If you are a UK brand running a UK email campaign and the country data shows 85% UK clicks, the distribution is working as expected.

Discovering Unexpected Markets

The more valuable insight comes from the unexpected. A brand that did not target Germany discovering that 20% of their link traffic comes from Germany has a market signal worth investigating. Did content get shared in a German community? Is there organic demand that the brand has not yet addressed with localised content? Country analytics surfaces these signals in real time — often before any other data source catches them.

Practical applications of country analytics:

• Market entry validation. Before investing in localisation or market expansion, run a campaign with global distribution. Country analytics shows which markets respond without the market development cost.
• Influencer audience verification. When considering an influencer partnership, request link analytics from a previous campaign. Country breakdown reveals whether their claimed audience geography matches reality.
• Press and editorial reach. A press release link with country tracking shows which markets picked up the story — beyond the publication's claimed readership geography.
• QR Code packaging distribution. Country data from packaging QR Codes reveals actual product consumption geography — where the product is being opened and used, not just where it was shipped.

Referrer Analytics — Understanding Your Traffic Sources

Referrer analytics shows which source delivered each click — which website, platform, email client, or channel sent a visitor to your short link. This is the channel attribution layer of link analytics.

How Referrers Are Captured

When a visitor clicks a link, their browser typically sends an HTTP Referer header containing the URL of the page they were on when they clicked. Cuttly reads this header at redirect time and categorises it into a source — facebook.com, twitter.com, m.facebook.com, a specific referring domain, or "direct" when no referrer header is present.

The Direct Traffic Problem

"Direct" in referrer analytics means the click arrived without a referrer header. This includes several scenarios:

• Email clients. Most email apps strip the referrer header — clicks from email arrive as direct. This is the most common cause of unexpectedly high direct traffic.
• SMS. SMS messages produce no referrer whatsoever — SMS clicks always appear as direct.
• Messaging apps. WhatsApp, Telegram, Signal and most other messaging apps strip referrer headers.
• HTTPS-to-HTTP transitions. When an HTTPS page links to an HTTP destination, the browser strips the referrer for security.
• Direct navigation. Users who type the URL directly or click from bookmarks produce no referrer.

This is why UTM parameters are essential for email and SMS campaigns — they provide attribution information that referrer headers cannot. Without UTM tags, every email and SMS click appears as "direct" in both Cuttly's referrer analytics and in GA4.

Social Media Referrers

Cuttly's PDF report includes a dedicated Social Media section breaking down clicks from Facebook, Twitter, Instagram, LinkedIn and other sources. Each platform is identified separately — including m.facebook.com (mobile Facebook) as distinct from desktop Facebook. This social breakdown is particularly valuable for understanding which platform drives engagement for your specific audience and content type.

Click Timing Analytics — The When of Engagement

Click timing analytics shows when your audience engages with your links — by day, by week, and with hourly granularity. This is one of the most consistently underutilised dimensions of link analytics, despite being directly actionable.

Hourly Heat Map

Cuttly provides an hourly click heat map (Single plan and above) showing click volume broken down by hour of the day across the selected time period. The heat map reveals your audience's engagement rhythm:

• Consumer email campaigns typically peak 8–10am (morning commute and start of workday) and 7–9pm (evening leisure time)
• B2B campaigns peak during business hours — 10am–12pm and 2–4pm
• Social media links peak in evenings and weekends for consumer audiences
• SMS campaign links peak within 5–15 minutes of sending — near-immediate engagement is the defining characteristic of the SMS channel

The practical application: use your own historical timing data — not generic benchmarks — to schedule sends. Your audience has specific engagement patterns. The heat map shows you exactly what they are.

Weekly Patterns

Cuttly's analytics view shows click volume broken down by week, with a comparison view between this week and last week. Tracking weekly patterns over time reveals:

• Which day of the week produces peak engagement for your specific audience
• Seasonal patterns — weeks where engagement drops (holiday periods, school breaks) or spikes (product launches, industry events)
• The rate at which click volume decays after a campaign send — how long a campaign remains active in audience engagement terms

UTM Attribution — Connecting Link Analytics to GA4

Link analytics measures the pre-arrival layer: clicks, device, country, referrer, timing. GA4 measures the post-arrival layer: sessions, pageviews, events, conversions, revenue. UTM parameters are the bridge between the two systems.

How UTM Parameters Work with Short Links

UTM parameters are added to the destination URL of the short link — not to the short link itself. The short link remains clean and brandable (go.brand.com/spring). The destination URL carries the tracking information (yourdomain.com/landing?utm_source=newsletter&utm_medium=email&utm_campaign=spring-sale-2026). When the visitor arrives at the destination after the redirect, GA4 reads the UTM parameters and attributes the session accordingly.

Cuttly has a built-in UTM builder directly in the dashboard for every short link — fill in the source, medium, campaign and optional content and term fields, and Cuttly assembles the correctly encoded UTM query string and appends it to the destination URL automatically.

What Each UTM Parameter Controls in GA4

Channels That Require UTM Parameters

Three high-volume marketing channels produce no referrer data — making UTM parameters not optional but essential:

• Email. Email apps strip referrer headers. Without UTM tags, every email click appears as direct traffic in GA4 — invisible as a channel.
• SMS. No referrer produced. Without UTM tags, SMS clicks are completely indistinguishable from other direct traffic in GA4.
• QR Codes. Scans produce no referrer. Without UTM tags on the destination URL, QR scans are classified as direct traffic in GA4 — the most expensive physical print investment in your marketing mix appears as an unlabelled entry.

Why Click Counts Differ Between Cuttly and GA4

Cuttly click counts are always higher than GA4 session counts attributed to the same campaign. The gap is normal and expected. The main causes:

• Bot and security scanner clicks. Email security tools pre-scan links in emails by making HTTP requests to them. These appear as clicks in Cuttly (which records all HTTP requests) but do not appear in GA4 (bots do not execute JavaScript). This is the largest source of discrepancy for email campaigns — often 20–50% of email "clicks" in unfiltered link analytics are bot scans.
• Ad blockers. Extensions that block GA4's tracking script prevent session recording in GA4 while having no effect on Cuttly's server-side redirect tracking. Ad blocker prevalence varies significantly by audience — technical audiences can have 20–40% ad blocker rates.
• Page load failures. If the destination page fails to load after the redirect, Cuttly records the click but GA4 does not record the session.
• Cookie consent rejection. Visitors who reject tracking cookies are not fully counted in GA4. Cuttly's cookie-free server-side tracking is unaffected.

Practical guidance: expect Cuttly total clicks to be 15–50% higher than GA4 sessions for email campaigns before bot filtering. After enabling bot click filtering in Cuttly (Single plan), the gap narrows to primarily ad blockers and page load failures — typically 5–20%.

QR Code Scan Tracking

Every Cuttly short link automatically generates a dynamic QR Code. Each scan of the QR Code is recorded as a click in the link's analytics — the same infrastructure, the same dimensions (device, country, referrer, timing), the same dashboard view.

This is the fundamental difference between dynamic QR Codes and static QR Codes:

QR Code scan analytics is the only way to measure physical-world campaign engagement at individual placement level. A QR Code on product packaging, on a poster, on a restaurant table card, on a business card — each can be a separate short link with its own analytics, revealing which physical placement generates the most engagement.

Per-Placement QR Code Strategy

The most sophisticated physical marketing teams use a separate short link and QR Code per physical placement — not one QR Code per campaign. The structure:

• go.brand.com/menu-table — restaurant table card QR Code
• go.brand.com/menu-counter — counter display QR Code
• go.brand.com/menu-window — window poster QR Code

All three point to the same destination. Analytics shows which physical placement drives the most scans. The table card is scanned 10x more than the window poster. That insight directly informs the next print run allocation.

Bot Click Filtering — Getting to Accurate Data

Bot click filtering is one of the most practically impactful features in Cuttly's analytics offering — available from the Single plan — and one of the least understood.

The problem: email security systems (used by corporate email clients, financial institutions, healthcare providers and large enterprises) automatically scan every link in every incoming email to check for malicious content. This scan looks exactly like a human click: it makes an HTTP GET request to the link URL. Cuttly records it as a click. But it is not a human — no one is there, no page is loaded, no conversion can happen.

The scale: for email campaigns to enterprise audiences (financial services, healthcare, government, large corporate), bot scanner clicks can represent 40–70% of total raw click counts. An email to 10,000 corporate recipients that shows 500 "clicks" in unfiltered analytics may have only 150 real human clicks — 350 are security scanner bots.

Bot click filtering in Cuttly identifies and removes bot/crawler clicks from the analytics count, leaving only human engagement data. The filtered count is the number to use for campaign performance measurement, CTR calculations and benchmarking.

Channels most affected by bot inflation:

• Corporate email (B2B). Highest bot scanner prevalence — enterprise security tools are most aggressive.
• Financial services email. Extremely high bot scanner rates due to regulatory compliance scanning requirements.
• Healthcare email. Similarly high — HIPAA compliance infrastructure includes aggressive link scanning.
• Consumer email (B2C). Lower but still significant — major ISPs (Gmail, Outlook) run link prefetch and security scanning.

PDF Reports and Chart Exports

Link analytics data in Cuttly can be exported in two ways: as a full PDF report for the link, or as individual chart exports (SVG, PNG, CSV).

PDF Report

The PDF report is a formatted, branded analytics document covering all dimensions for the selected date range. It contains:

• Short link and destination link details
• Total clicks by date
• Social media clicks breakdown (Facebook, Twitter, Instagram, LinkedIn, other/direct)
• Referrals and other click sources by domain
• Device clicks (Mobile / Desktop)
• OS clicks with version
• Browser clicks with version
• Brand and device model clicks
• Language clicks (browser language)
• Geo Location clicks by country

The PDF format makes it directly shareable as a client deliverable or internal report without any additional formatting work. For agencies managing link campaigns for clients, the PDF report is the default reporting artifact — generated with one click from the analytics view.

Chart Exports: SVG, PNG and CSV

Individual charts within the analytics view can be exported separately using the three-line export menu on each chart:

• SVG — vector format, scales to any size without quality loss; best for presentations and documents
• PNG — raster image; suitable for embedding in emails, slides or digital reports
• CSV — raw data from the chart in spreadsheet format; suitable for further analysis in Excel, Google Sheets or import into a BI tool

Aggregated Analytics — The Campaign View

Individual link analytics shows performance for one link. Most campaigns have many links — different channels, different audience segments, different content types, all part of the same campaign. Aggregated analytics combines all of them.

In Cuttly, campaign tags group links together. Tag all links from a campaign with the same tag (e.g. spring-sale-2026) and aggregated analytics shows total engagement across all tagged links — a campaign-level view rather than a link-level view.

Aggregated analytics is available in Cuttly from the Single plan (last 7 days, up to 10 links) with expanded availability on higher plans. It answers questions that individual link analytics cannot:

• What was the total reach of this campaign across all channels?
• Which channel drove the most clicks to this campaign?
• What was the combined device breakdown across all campaign links?
• Which geographic markets responded to this campaign?

Analytics via API

All link analytics data is accessible programmatically via the Cuttly API — enabling integration with data warehouses, BI tools, custom dashboards and automated reporting pipelines. The API is available on all plans including free.

Key API capabilities for analytics:

• Link analytics retrieval — all plans: pull click data for any short link programmatically
• Date range filtering — Team plan and above: use date_from and date_to parameters to retrieve analytics for specific date ranges — essential for automated weekly or monthly reporting pipelines

Common API analytics integration patterns: scheduled daily job pulls previous day's link analytics and writes to a BigQuery table for BI analysis; Zapier/Make automation posts link performance summary to a Slack channel after each campaign; custom dashboard aggregates analytics across all campaigns for a client-facing reporting view.

How to Use Link Analytics to Make Better Decisions

Data without decision is just noise. Here is how each analytics dimension translates into specific, actionable marketing decisions:

Decision 1: Channel Allocation

Data needed: clicks per link across a campaign, broken down by channel (use UTM source to identify channel per link).

Decision: which channels to invest more in and which to cut. If email drives 60% of campaign clicks and social drives 8%, the time-to-next-campaign allocation should reflect this — more email frequency, less social production cost.

Decision 2: Send Time Optimisation

Data needed: hourly heat map across 3+ campaigns to the same audience.

Decision: the specific hour to schedule sends for maximum immediate engagement. Most marketing teams use generic "best time to send" benchmarks. Your audience's heat map is better than any benchmark.

Decision 3: Mobile Optimisation Priority

Data needed: device type split across all links for a campaign or channel.

Decision: where to invest landing page optimisation effort. An audience that is 85% mobile makes desktop landing page performance a secondary concern. An audience that is 60% desktop in a B2B email context means desktop experience needs equal attention.

Decision 4: Market Expansion

Data needed: country breakdown across organic and earned media links.

Decision: which markets warrant localised content investment. Persistent traffic from a market you have not targeted explicitly is a signal worth testing with dedicated localised content before committing to full market entry.

Decision 5: Influencer ROI

Data needed: per-influencer unique click counts, device breakdown, country breakdown, timing patterns.

Decision: which influencer partnerships to renew and which to discontinue. Unique clicks per influencer is the engagement metric — not follower count, not impressions, not vanity metrics that cannot be verified.

Decision 6: Physical Placement Allocation

Data needed: QR Code scan counts per placement (using separate links per placement).

Decision: how to allocate the next print run. If table card QR Codes generate 10x the scans of window poster QR Codes, the budget for the next print run should reflect this — more table cards, fewer window posters.

Building Your Link Analytics Practice: A Practical Framework

Analytics is only valuable if it is used consistently. Here is a practical framework for building link analytics into campaign workflows:

Before Every Campaign

• Create all campaign links in Cuttly with UTM parameters for every link pointing to a GA4-tracked destination
• Apply a consistent campaign tag to all links
• Enable bot click filtering on all links if targeting corporate or enterprise audiences
• Enable unique click counting on key measurement links

During the Campaign

• Check click velocity in the first 24 hours after send — early signals predict final performance
• Monitor device and country breakdown as clicks accumulate — early surprises may warrant mid-campaign adjustments
• For multi-wave campaigns, use performance from wave 1 to inform timing and channel mix for wave 2

After Every Campaign

• Download the PDF report for all significant links and save to the campaign record
• Export the click timeline as CSV for trend analysis
• Record unique clicks per channel in your channel performance tracker
• Update your own CTR benchmarks with the new data points
• Document any anomalies — unexpected countries, device shifts, unusual timing patterns — for future reference

The Analytics Stack: Link Analytics + GA4 Together

Neither link analytics nor GA4 alone gives the full picture. Together they cover the complete visitor journey:

The combination of server-side link analytics (pre-arrival) and GA4 (post-arrival) covers every marketer's measurement needs. Link analytics fills the channels GA4 cannot see. GA4 covers the conversion and behaviour depth that link analytics does not attempt to measure. They are not competing tools — they are complementary layers of the same measurement system.

Start tracking every link today — create a free Cuttly account and every short link you create automatically comes with full analytics, no setup required.