Link Analytics
How WarpLink counts clicks, deduplicates them, filters bots, and joins installs to the links that drove them, per plan retention window.
WarpLink records every click and every attributed install as it happens, and reports them per link and per campaign. Deep linking, install attribution, and real-time analytics come from the same SDK, so the numbers describe the same links you configured, not a separate system you reconcile by hand.
What Counts as a Click
A click is recorded when a visitor's request reaches a link and is not a bot. Recording happens on a path separate from the redirect itself, so counting never delays the person tapping the link.
Before a click is ever written, WarpLink checks the request's user agent against a bot and crawler list. A bot request never becomes a click: it is excluded at that check, not filtered out afterward, so there is no "bot clicks" number to subtract. A bot that WarpLink recognizes as a social media or chat crawler gets an HTML page with Open Graph and Twitter Card tags instead, for a rich preview. A real visitor gets the redirect, and that request is what gets counted.
Unique Clicks
Unique clicks answer a narrower question than total clicks: how many distinct visitors, not how many taps. WarpLink computes uniqueness server side, at the moment a click is written, for perfect accuracy rather than an approximation.
A click counts as unique per combination of link, visitor address, and a rolling twenty-four hour window. One person tapping the same link four times in an hour is one unique click and four total clicks. The same person tapping it again the next day adds a second unique click.
Joining Installs to Clicks
Installs are attributed back to the link click that drove them and shown per link alongside your click numbers. The match itself, referrer, device ID, fingerprint, or raw signals, and the confidence score behind each one, is covered in Install attribution.
Retention by Plan
How far back you can look is set by your plan. Retention is enforced, not just marketed: data older than the window is removed on a schedule, not merely hidden from view.
| Plan | Retention |
|---|---|
| Free | 90 days |
| Starter | 180 days |
| Growth | 365 days |
| Scale | 3 years |
| Unlimited | 3 years |
Analytics Gating
Redirects always work. A link never stops routing visitors because of a click limit, on any plan.
What can change is whether new analytics keeps computing. Once a Free plan org goes over its monthly click limit, new analytics is gated behind an upgrade prompt until the next billing period, or until you move to a paid plan. Paid plans are never gated. The dashboard warns you at 50, 80, and 90 percent of your limit before that happens.
Reading Analytics
In the dashboard, clicks and installs appear as they happen, with no hourly rollup or overnight batch to wait through. You can filter by Today, 7 days, 30 days, 90 days, or a custom range, and break the same clicks down by country, referrer, and device per link or org wide, and by operating system, browser, and UTM source, medium, and campaign per link.
For a copy you can move elsewhere, export raw click rows as CSV, including UTM term and content and whether each row was the unique click.
An AI client can also pull a link's totals, unique clicks, a time series, and its redirect versus app open split, through the MCP server's get_link_analytics tool. This is a narrower view than the dashboard: it does not include installs, country, referrer, device, browser, or UTM breakdowns. The tool needs either the analytics:read or the links:read scope and is free on every plan, sharing the standard 60 requests a minute.
See Real-time analytics for the commercial overview, and the glossary for terms like click deduplication and UTM parameters.