Analytics
Every click, counted honestly and explained
Analytics is the screen your clients open every morning, so it reports real events rather than a sampled estimate. Filter by period, link, domain, country, device or campaign and every widget on the page follows the same filter. Anything you can see, you can export.
One filter bar, seven widgets, no contradictions
The filter bar sits above everything: a period ranging from today to all time or a custom range, plus chips for link, domain, country, device, browser, operating system, referrer and each UTM field. Change one chip and the summary, the time series, the map, the device breakdown, the sources table and the top-links table all recompute against it. There is no second definition of a click hiding in a different tab.
The summary compares the current period against the previous one and shows the delta, because a number without a trend is trivia. The time series switches between clicks and unique visitors and picks hour, day or week granularity to match the range. The map is a choropleth by country where clicking a country becomes a filter, with top countries and top cities tabled beside it.
- Summary — clicks, unique visitors, active links, QR scan share, change versus previous period
- Time series — hourly, daily or weekly, clicks or uniques
- Geography — country choropleth plus city-level tables
- Devices — device type, browser and operating system with versions
- Sources — referring domains with favicons, direct traffic separated, top UTM values
- Top links — a sortable table with a sparkline per row
- A/B — clicks and share per variant with an honest significance note
Bots are excluded, visitors are counted without tracking them
Bot traffic is recorded but excluded from every report by default, so a crawler sweep does not look like a successful campaign. A toggle lets you include it when you actually want to see it, which is the honest way round: hide it by default, never delete it.
Unique visitors are derived from a hash that combines request signals with a salt that rotates every day. No IP address is stored, and the same person on two consecutive days is two daily uniques rather than one identity followed over time. The metric is labelled as unique visitors per day for that exact reason, because a tool that quietly redefines "unique" over a ninety-day window is telling you a story rather than a number.
Timestamps are stored in UTC and displayed in the timezone of the workspace, and daily aggregation follows that same timezone. A campaign that ran on Tuesday in Sydney appears on Tuesday.
A single link gets the same depth as the whole account
Open any link and you get the analytics screen scoped to it, plus a live feed of the most recent hundred clicks with time, country and city, device and referrer. That feed is what people actually use to confirm a link works right after publishing it — far more convincing than a chart that updates hourly.
Links can also expose a public statistics page, opt-in per link, at the short URL with a plus sign appended. It renders under your brand, contains no personal data and is marked no-index, so it can be shared with a client or a sponsor without giving anyone dashboard access.
Retention and export are stated, not implied
Detailed events are retained according to plan, up to twenty-four months, and the interface tells you when a requested range goes past your retention instead of silently returning an empty chart. Daily rollups per link are kept permanently, so the lifetime click count of a link never resets even after detailed events age out.
Every widget exports to CSV through a streaming endpoint that handles up to a hundred thousand rows, and the same breakdowns are available through the API for teams that would rather load them into their own warehouse. Nothing is locked into a screenshot.
For context on why this matters: as of August 2026 Rebrandly caps monthly engagement events by plan at one hundred to one hundred and fifty thousand, and BL.INK does not publish its retention at all. Our limits are published, and exceeding them stops tracking, never redirects.
Frequently asked questions
Is the data sampled?
No. Every non-bot click is written as an event and the reports aggregate those events. Sampling is what happens when a vendor cannot afford to store your traffic; the click pipeline here batches events from the edge into a columnar store built for exactly this shape of query.
How quickly do clicks appear?
Clicks are queued at the edge and flushed in batches, so the recent-clicks feed and the counters update within seconds of the visit. Longer aggregations over months are the same data, read from materialised rollups rather than recomputed on every page load.
Do you use cookies or store IP addresses?
Neither. Visitor identity for the uniques metric is a daily-rotating hash that cannot be reversed into an address, and the only cookie the redirector issues is the short-lived one that unlocks a password-protected link for the person who typed the password.
Launch your branded link shortener
Connect a domain, publish your prices and invite your first customer — most partners go live in an evening.
No card required for the trial.