On this page
We noticed the bounce.
In late 2023, linkboo was helping a friend — a small skincare creator on TikTok, around 80,000 followers — figure out why her bio link, pointing to an Amazon storefront, was converting at a rate her audience size didn't explain. She was getting 30,000 bio link taps a month. The Amazon affiliate dashboard showed her about 200 of them clicking through to actual products. The math didn't make sense. The audience was loyal, the products were good, the videos were earning genuine intent.
What was happening, mechanically, was that every viewer who tapped the link from inside TikTok landed on Amazon's storefront inside TikTok's in-app browser — a webview that did not have their Amazon login cookie. Amazon greeted them as a logged-out stranger. Most strangers, on a phone, with the TikTok feed waiting one tab over, bounced. The 200 who actually clicked were the 0.7% who happened to be paying attention to the "sign in" prompt and willing to enter their password on a mobile keyboard. The other 29,800 were getting handed to a destination that did not know them.
This wasn't her audience being uninterested. It was a structural failure of the bio link layer. And every existing tool — Linktree, Beacons, Stan, Bento — was making the same handoff to the same broken webview. None of them tried to bounce the viewer out to Safari, where the viewer's actual Amazon session lived. They all just shrugged the viewer toward whatever browser the social app decided to use.
What the existing tools got wrong
The conventional wisdom in the link-in-bio category, for the last six or seven years, has been that the value of the product is aggregation — letting creators surface multiple destinations on one tappable page. Linktree pioneered this in 2016 and the whole category followed.
That framing isn't wrong, but it stops at the wrong place. Aggregation is the what. The where — the browser context the viewer ends up in when they tap the destination — has been almost entirely ignored by the category, even as Instagram and TikTok's in-app browsers became the de facto delivery environment for billions of mobile clicks per day. By 2024, more bio link clicks happened inside in-app webviews than in real browsers. The category responded by adding more aggregation features. None of the major players shipped a serious in-app browser escape flow.
The few tools that did address it — Bouncy.ai, InAppRedirect, LinkTwin, URLGenius — built the escape mechanism as a feature for paid-media teams. URLGenius in particular is a remarkable product, built for enterprise advertisers spending six figures a month on Meta ads who needed to fix the same problem at brand-budget scale. It's priced and packaged for that buyer. It is not, and was never meant to be, a tool an OnlyFans creator with 40,000 followers buys for $9.
There was a hole in the middle. The mechanism that solves the problem — detecting in-app webviews and bouncing to Safari or Chrome — exists. The browser signals are there if you know what to look for, and the OS-level hand-off path is available on both iOS and Android. What didn't exist was a creator-native tool that put the escape flow in front of the aggregation features, sold it as the entire pitch, and priced it for working creators.
Why linkboo exists
linkboo is built around one inversion: the bounce is the product.
The aggregation features — multiple blocks, custom branding, analytics, UTM injection, import-from-Linktree, the things every category competitor has — are all in here. They exist because creators need them. But they're not the pitch. The pitch is that every linkboo link, when tapped from inside TikTok or Instagram or Threads or Messenger, detects the webview and gets the viewer out of it before the destination loads. The viewer lands on Amazon already logged in, on Spotify with their account ready to pre-save, on OnlyFans with their subscription cookie present, on Shopify with Apple Pay rendering correctly, on Substack with the subscribe form posting cookies that survive. The destination thinks they're a real returning viewer, because in their real browser they are.
We built it flat-priced because creators driving real volume should not have a surprise bill when a video pops. We built it creator-native because the buyer is a person, not a procurement department, and the onboarding has to be ten minutes, not ten weeks. We built it without an SDK because most creators don't have engineering teams and the few who do shouldn't have to integrate one for the bio link to work. We built the agency tier because the people getting hurt worst by the in-app browser problem at scale are the agencies and labels managing rosters of creators who are each losing 30-70% of bio link conversions and don't know why.
We don't think we're the only legitimate tool in this space. We've written a comparison guide that says, on the record, where each competitor wins. URLGenius is a better fit for enterprise paid-media teams. Bouncy.ai may suit a metric-obsessed conversion shop. We're built specifically for creators and the agencies that work with them.
What we're confident about is the worldview: that aggregation without escape is solving the visible half of the problem and ignoring the half that's actually costing creators money. linkboo is the version of link-in-bio that takes the second half as seriously as the first.
What we believe
A few things that show up in everything we ship:
The default browser context belongs to the viewer, not the platform. Instagram and TikTok have business reasons to keep viewers inside their app. The viewer has reasons — their cookies, their saved payment methods, their actual logged-in identity — to be in their real browser. When the viewer's interest and the platform's interest collide, the viewer wins.
Flat pricing respects creators. Per-click pricing punishes the thing you're paying for the tool to enable. We refuse to bill that way.
Compliance-friendly does not mean restrictive. Legitimate businesses in regulated categories — compounded medications, hormone-replacement clinics, research-chemical retailers, peptide research, telehealth — deserve a tool that doesn't pretend they don't exist. See acceptable use for the explicit posture.
Documentation is product. Every page on linkboo's site is the product extending itself to help you understand what's happening. The /fix/ cluster, the /guides/ cluster, the /help/ pages — they exist because we think solving the in-app browser problem requires teaching people what it is.
Brand voice is honesty. We're not going to call ourselves "the leading" anything, or pretend we invented the escape flow, or sneer at competitors who got here first. The worldview is enough.
Where we are
linkboo is built and run from the United States. The team is small — under twenty people across engineering, design, support, and growth. The infrastructure is built for ten times our current load, because viral creator traffic comes in spikes and 100x days are the only days that actually matter.
We are profitable, we are not VC-backed, and we don't plan to be. That's a deliberate choice; the incentives of a profitable, founder-run company point in a different direction than the incentives of a venture-backed one. Both can build good products. The one we wanted to build is this one.
Start free → · See the worldview in action — the thesis page →