Analytics
Real-time analytics for every link and install
WarpLink records every click and every attributed install as it happens, and reports them 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.
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
Clicks and installs appear as they happen. There is no hourly rollup and no overnight batch to wait through, so a link you shared a minute ago already has numbers worth reading. Totals, unique clicks, and the trend over time sit beside the installs that attribution credited back to the same link.
Break it down
Break the same clicks down by device, country, referrer, and UTM parameters, per link and per campaign, and export the numbers as CSV when you want them elsewhere. An AI client can pull a link's click analytics over the MCP server instead. How far back you can look is set by your plan, from 90 days up to three years.
From the API or an AI client
const response = await fetch("https://api.warplink.app/v1/links", {
method: "POST",
headers: {
Authorization: "Bearer wl_live_xxx",
"Content-Type": "application/json",
},
body: JSON.stringify({
destination_url: "https://app.example/promo",
}),
});
const link = (await response.json()) as { short_url: string };{
"mcpServers": {
"warplink": {
"url": "https://api.warplink.app/mcp"
}
}
}Frequently Asked Questions
As they happen. 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. Nothing waits for an hourly rollup or an overnight batch, which 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, 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. Redirects always work and are never blocked, on any plan, including after the Free plan's 10,000 clicks a month are used. When the limit is reached only new analytics is gated behind an upgrade, never the links themselves, and the dashboard warns you well before you get there. The plans are at warplink.app/pricing.
Yes, in two ways. The dashboard exports your clicks as CSV, so the numbers move into a spreadsheet or a warehouse without a script. An AI client can read a link's click analytics over the MCP server, which is free on every plan, needs either the analytics:read or the links:read scope, and shares the REST API limit of 60 requests a minute. Click analytics is read through those two surfaces rather than through a REST endpoint of its own.
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?