Analytics
Real-time analytics for every link and install
WarpLink records every click and every attributed install, and shows recent taps within minutes, per link and per campaign, broken down by device, country, referrer, and UTM parameters. Deep linking, install attribution, and real-time analytics come from the same SDK, so the numbers and the links they describe are one system rather than three vendors you reconcile by hand.
What is real-time link analytics?
Real-time link analytics counts every click on a link, and every install attributed to it, then shows them in the dashboard within minutes, broken down by device, country, referrer, and UTM parameters. WarpLink records clicks on a path separate from the redirect, so counting never slows the person tapping, and installs appear beside the clicks that earned them.
How it works
A visitor taps the link. The redirect answers at the edge. A known bot, such as a social media crawler, gets a preview page and never becomes a click.
The click is recorded off the redirect path. The tap is queued and written in batches, so counting never delays the visitor on the other end of the link.
Uniqueness is computed when the click is written. A click is unique per link, visitor address, and rolling 24-hour window, so four taps in an hour count as four total clicks and one unique click.
Installs join the clicks. When the SDK reports a first launch, install attribution credits the install to the link that drove it, and it shows beside that link's click numbers.
You read the numbers in the dashboard. The Analytics page reads Today, 7, 30, and 90 days, or a custom range, with hourly, daily, and weekly trends and the previous period alongside.
The same numbers are available in code. GET /v1/analytics, CSV exports, and the MCP server return what the page shows for the same window, filters, and reporting time zone.
Key facts
- Recent taps show in the dashboard within minutes.
- Breakdowns: country, referrer, device, operating system, browser, campaign source, app, and tap source.
- Retention by plan: 90 days on Free, 180 days on Starter, 1 year on Growth, 3 years on Scale, 3 years on Unlimited. Free reads the last 30 days of its 90; an upgrade shows the rest at once.
- On the Free plan, passing the monthly click limit freezes analytics at that moment. Paid plans are never frozen.
- Redirects keep working past any click limit, on every plan. A custom domain serves while your plan includes it: Free includes a 90-day trial (about 3 months), with a grace period of up to 30 days after a paid plan ends.
- The MCP server exposes 34 tools, is free on every plan, and shares the REST API limit of 60 requests a minute.
- Plans start at Free ($0, 10K clicks a month) and run through Starter ($19), Growth ($49), and Scale ($99) to Unlimited ($149, no click ceiling).
How real-time link analytics works
Share
Create a link and share it. Every tap is counted at the edge, whether it opened your app, went on to the store, or landed on your website. Uniqueness is computed when the click is written, per link, address, and 24-hour window, so one curious reader tapping four times is still one unique click.
Watch
Every click is recorded at tap time, and recent taps show in the dashboard within minutes. Totals, unique clicks, and the trend over time sit beside the installs that attribution credited back to the same link, with hourly, daily, and weekly buckets and the previous period drawn alongside.
Break it down
Break the same clicks down by device, country, referrer, and UTM parameters, per link and per campaign. Filter by several values, compare links, and read days in your organization's time zone. The REST API and MCP server return the same numbers as the dashboard. Retention runs from 90 days up to three years.
From an AI client
{
"tool": "get_link_analytics",
"input": {
"link_id": "3f9a1c2e-6b7d-4e1a-9c2f-8a5b1d0e7c44",
"days": 7
},
"output": {
"total_clicks": 1842,
"unique_clicks": 1290,
"time_series": [
{ "date": "2026-09-15", "total": 240, "unique": 178 },
{ "date": "2026-09-16", "total": 265, "unique": 191 }
],
"sources": [
{ "source": "app_open", "total": 322, "unique": 210 },
{ "source": "redirect", "total": 1520, "unique": 1080 }
]
}
}{
"mcpServers": {
"warplink": {
"url": "https://api.warplink.app/mcp"
}
}
}Frequently Asked Questions
Clicks are recorded at tap time, and recent taps show in the dashboard within minutes. The redirect is answered at the edge and the click is recorded on a separate path, so counting never delays the person tapping the link. That is what lets you post a link, watch the first taps arrive, and decide whether the message landed while it is still worth changing.
Yes. The utm_source, utm_medium, and utm_campaign values on the link a visitor tapped are stored with the click, so clicks group by source, medium, and campaign the same way the rest of your reporting does. Device, country, and referrer work the same way, per link and per campaign, which is what tells you that a channel brought clicks but a different one brought installs.
Retention follows the plan: 90 days on Free (Free reads the last 30 days of it; an upgrade shows the rest at once), 180 days on Starter at $19 a month, 365 days on Growth at $49 a month, and three years on both Scale at $99 and Unlimited at $149. The window moves with time, so older clicks fall out of it. Pick the plan that covers the period you genuinely look back over, not the longest one on the page.
Your links keep working. A click limit never blocks a redirect, on any plan, including after the Free plan's 10,000 clicks a month are used. Links on your app's own aplnk.to address never stop redirecting, and a custom domain serves while your plan includes it: Free includes a 90-day trial (about 3 months), and after a paid plan ends there is a grace period of up to 30 days. When the limit is reached analytics freeze at that moment, never the links themselves, and the dashboard warns you well before you get there. The plans are at warplink.app/pricing.
Yes, in three ways. The dashboard exports your clicks as CSV, so the numbers move into a spreadsheet or a warehouse without a script. The REST API has export routes that start a click export, report its status, and download the file, and GET /v1/analytics returns the same numbers as the Analytics page. An AI client can do both over the MCP server, which is free on every plan, needs the analytics:read or links:read scope, and shares the REST API limit of 60 requests a minute.
Your links should open the app.
Your data should tell you why.
Set up deep linking, attribution, and analytics in minutes. Free to start.
Start building, freeHave a question?