The Trizlink story: why your link tools never agree
Three tools, three dashboards, three numbers that never agreed, and one question none of them could answer. Why Trizlink exists, and where its numbers stop.
Why do my link tools not agree with each other?
Because a click, a page view and an impression are three different events, and your shortener, bio-page host and scheduler each count only one of them. Nobody adds them up, so you do. None of the three reads the others' data, and each keeps its own dashboard, so the total you are looking for is not a total.
That is link fragmentation. Trizlink started as a complaint about it.
What does link fragmentation cost in practice?
An afternoon with a spreadsheet, usually, and a total nobody can defend. A small team runs a campaign. The ad goes out with a short link. The same offer sits on a link-in-bio page, because that is where the social traffic lands. A few posts go out through a scheduler. Two weeks later somebody asks which of the three worked. Nobody can say without a spreadsheet.
Each tool counts its own event, and counts it honestly. The trouble is the join: no tool can see what the other two recorded for the same campaign.
The reconciliation that started Trizlink took most of an afternoon. Three exports, three date formats, two different ideas of what a unique visitor is, and a bio page whose outbound links were not tracked at all because they had been pasted in as plain addresses. The figure at the bottom of that spreadsheet was a guess presented as a total.
Would a better spreadsheet fix it?
No. A better spreadsheet reconciles faster; it still reconciles. Every export still carries its own tool's definition of a click, so the spreadsheet only lines up three numbers that were never measuring the same event.
The fix was noticing that all three surfaces end in the same act — somebody presses a link — and that if one system recorded every one of those presses, there would be nothing left to add up by hand. That is the whole architecture.
How does Trizlink count a link, a bio page and a post together?
By recording all three in the same workspace, on one timeline. A short link resolves at the edge and writes one row per visit. So does a bio page, at its own address on trizlink.com. A press on any of its link buttons writes a row of its own, which is how the editor can tell you how many times that one button was pressed in the last 14 days. The Analytics page then puts every surface in the workspace on one axis and compares each figure against the previous window of the same length. Nothing has to be joined after the fact, because nothing was split in the first place.
Posts are the third surface. They come with a catch. A post can carry one Trizlink short link, which is how its clicks land in the same report. Social publishing is built and switched off: connecting an account waits on the platforms' developer applications, and until then no post goes out through Trizlink.
Does one workspace make the numbers exact?
No, and nobody's are. Real click counts are best-effort everywhere — bots, prefetching and privacy blockers all distort them. What link analytics actually tell you walks through what moves a click count, in both directions. A chat app building a preview card fetches the link, which is a click nobody made. A privacy blocker removes one somebody did.
One workspace fixes the definition. It does not fix the counting. Bot clicks are the plain example: they are counted in your total today, and nothing separates them out yet. An alert can tell you when traffic jumps far above its usual level, and that is all it does. What one workspace does change is that a post, a bio page and a short link are measured with the same rules, so comparing them at least compares like with like, which three exports from three tools never did.
Three things hold regardless, all about your data:
- Visitor IP addresses are never stored, so they cannot leak, which is also why location is coarse and labelled as an estimate. The privacy policy says exactly what is recorded about the people who click.
- Links export as CSV on every plan including Free, in the same columns the importer reads. The whole account leaves as one file.
- Sign-in is Google only. So there is no Trizlink password to steal.
Why does Trizlink keep saying what it cannot do?
Because the first version of Trizlink had started to describe things it could not do. This Trizlink is a rebuild. The original worked, and it collected what fast-moving products collect. What it collected was features that existed in the type system and not in the interface, screens describing capabilities the code had never implemented, and documentation that had drifted far enough from the software to mislead.
Patching that was refused. The product was audited feature by feature and rebuilt against a written record of what had shipped and what had merely been claimed. Every public URL was frozen first, so no address anybody had saved could break. Every screen was drawn and approved before the app was built to match it.
So the rebuild started from a written list of claims the old product could not keep, and the same habit produces the list of what Trizlink does not do yet.
What does Trizlink not do yet?
- Social publishing is built and switched off until the platform developer applications are registered.
- A custom domain can be added and verified. Serving links from it is deferred.
- The rebuilt Android app (2.14.0) is not yet released; the Google Play listing still carries the earlier version.
- There is no iOS app.
- There is no browser extension.
Once publishing is switched on and a platform rejects a post for its own reasons, Trizlink shows you the failure and leaves the post unsent. That promise has not met a real platform yet.
The list is printed here because the Trizlink team is small and independent, with no "contact sales" button anywhere and a short roadmap.
Start on the Free plan. It is the whole product at a smaller size. Pro is $9.99 a month and Team $8.99 a seat a month from 3 seats, paid by card on the website. Free is $0 with no card: 1,000 short links, 30 bio pages and 50,000 tracked clicks a month.
Frequently asked
What is link fragmentation?
It is what happens when the links you publish are managed by several tools that do not know about each other. Each issues its own links, counts its own event with its own definition and reports separately, so you get several partial numbers and never one total.
Why do three tools make measurement harder rather than just slower?
Because they record different events. A click, a page view and an impression are not interchangeable. Exporting all three does not turn them into one figure. The dependable fix is for one system to record every link.
How does Trizlink avoid the problem instead of modelling around it?
Short links and bio pages are recorded in the same workspace on one timeline, and the Analytics page shows every surface in that workspace on one axis. A post can carry one Trizlink short link, which is how its clicks land in the same report; social publishing itself is built and switched off until the platform developer applications are registered.
Are Trizlink's click numbers exact?
No, and nobody's are. Real click counts are best-effort everywhere — bots, prefetching and privacy blockers all distort them. Bot clicks are counted in your total today; nothing separates them out yet. Visitor IP addresses are never stored.
Who makes Trizlink?
The Trizlink team. It is small and independent, with no sales team and a short roadmap. Every plan's limits and prices are written in the pricing section.
Can I leave and take my data?
Yes, on every plan including Free. Links export as CSV in the columns the importer reads, and the whole account exports as one file. Deleting your account removes your data and schedules the workspace for removal.
Share this post
https://trizlink.com/blog/the-trizlink-story-solving-fragmentationRead next
- Bio page messages and signups: advance privacy notice
Bio pages may collect Contact messages and email addresses pending confirmation no earlier than 20 November 2026 at 00:00 UTC. The new collection remains off until 14 full days after this notice is visible in the app and RSS feed, and until the updated legal pages and backend are released. Read the proposed changes in the linked post; the legal pages show current text until activation.
- Changes to our Privacy Policy and Terms, from 22 October 2026
Our Privacy Policy and Terms now cover AI suggestions and voice drafting: who answers AI requests, how long recordings are kept, and your own keys.