On this page
You posted the demo clip, it did numbers, and a prospect tapped the link in your bio to start a trial. This is the person your entire funnel is built to catch — they saw the product, understood the value, and chose to act in the same breath. They land on your signup page, see "Continue with Google," and tap it. And nothing useful happens. The OAuth popup either never opens, opens to a blank screen, or throws them into a logged-out Google sign-in flow — all inside TikTok's in-app browser, with the feed one swipe away.
Most of them swipe. The intent was real and it was perishable, and "type my Google email, get a code, switch apps, come back, hope it didn't break" is more than a spur-of-the-moment trial is worth. The signup never happens, and it doesn't show up anywhere as a problem — it reads as a weak click-to-signup ratio that looks like a messaging problem and isn't.
the conversion problem SaaS founders face
Modern signup is gated on auth, and modern auth is gated on a browser session you don't control. "Continue with Google," "Sign in with Microsoft," magic links, passkeys — every one of them assumes the prospect is in a real browser where their identity provider session already lives. The OAuth redirect chain hops from your app to accounts.google.com and back, and that round trip needs cookies, popups, and the system browser to behave normally.
In-app browsers break exactly that. When a prospect taps your bio link from inside TikTok, Instagram, or LinkedIn, the platform's webview renders your signup page itself instead of handing off to Safari or Chrome. So the Google session sitting on the same phone — the one that would make "Continue with Google" a single tap — is invisible. Worse, Google actively blocks OAuth inside many embedded webviews for security reasons, returning a disallowed_useragent error or a dead-end screen. The prospect who wanted to try your product hits a sign-in wall that simply doesn't work, on a webview that has its own empty cookie jar.
We named this problem the vanishing visitor and wrote the full mechanism explainer there. The short version for founders: the session that proves "this person already has a Google account, here's the one-tap consent screen" lives in their real browser. Your bio link opens inside the platform's webview, which can't reach it — and which the identity provider may refuse to authenticate at all. Your single highest-intent acquisition channel terminates at a button that does nothing.
what this costs
Auth-wall loss is hard to see because it never reaches your analytics as a failure — the prospect lands, the signup event doesn't fire, and the row just doesn't exist. But the structural pattern is consistent: social traffic arriving through an in-app browser converts to signup at a fraction of the rate the same prospect would convert at in Safari, and the gap is widest precisely on SSO-first signup flows, because the failure is hard-gated on the conversion event itself.
The math is unforgiving because it compounds against your best traffic. If a founder is paying for a creator collab, or pouring hours into LinkedIn and short-form, the in-app-browser cohort is typically the largest single source of "clicked, didn't sign up." A funnel doing, say, a few hundred bio-link taps a month into a Google-SSO signup is often leaving the majority of mobile-social signups on the table — not because the pitch was weak, but because the auth handoff never fired while intent was hot. Founders who fix only the handoff routinely report signup conversion on social traffic moving in the range of 2–4× with no other change.
what linkboo does
linkboo replaces the URL in your TikTok, Instagram, LinkedIn, X, or Threads bio (and in your link-in-collab posts) with a link-in-bio page — or a direct-route link straight to your signup, your choice — that has the in-app browser escape flow built into every outbound click. When a prospect taps your linkboo URL from any webview, linkboo detects it and immediately bounces the destination out to the prospect's real browser — Safari on iOS, Chrome on Android — where their Google, Microsoft, and Apple sessions live, before your signup page even loads.
The prospect never sees a friction prompt or has to know what "open in Safari" means. They tap, your signup page opens in the real browser, "Continue with Google" works on the first try, and they're in the product in two taps. The auth that was dead in the webview is alive again.
Concretely, for SaaS founders this means:
- Google / Microsoft / Apple SSO actually completes — the OAuth round trip runs in a real browser, so the identity provider authenticates instead of returning
disallowed_useragent - Magic links and passkeys land in the right browser — the session the link creates is in the same browser the prospect keeps using, not a webview they'll abandon
- Returning users are recognized — anyone already logged into your app on that device drops straight into the dashboard instead of a login wall
- Fallback is graceful — if SSO still isn't an option, the prospect lands logged-out in their real browser (where autofill and password managers work), not a webview where nothing does
linkboo is also a full link-in-bio page — multiple links, themes, a clean product surface, the things you'd expect from a Linktree or Beacons alternative. For a B2B funnel the escape flow is the wedge; the page is the convenience.
the destinations where SaaS founders bleed the most
Deep writeup on the specific mechanism that kills product signups:
- Google login fails in the TikTok browser — the
disallowed_useragentblock, the embedded-webview OAuth suppression, and exactly how the escape flow restores "Continue with Google" on the first tap
The same failure mode applies to Microsoft and Apple SSO, magic-link sign-in, and passkey flows from Instagram, LinkedIn, and X webviews — the identity provider can't reach a session that lives in the system browser, so the escape flow is the fix in every case. The full destination index is here.
why not Linktree, Beacons, or a raw signup URL?
None of them have an in-app browser escape flow. They're link-in-bio pages. When a prospect taps a Linktree URL from TikTok, your signup link opens inside TikTok's webview exactly as a raw URL would — "Continue with Google" still fails, the OAuth popup still dies, the trial still doesn't start. Dropping a generic link-in-bio tool between your bio and your signup page doesn't touch the structural loss, because the loss happens at the auth handoff, not the page in the middle.
If you're comparison-shopping the broader category, linkboo vs Linktree is the closest mainstream comparison.
pricing
Free up to a real volume of monthly clicks. No per-click pricing and no overage charges — which matters when a single trial signup is worth far more than a single click, and you don't want acquisition cost scaling with raw traffic. The escape flow works on the free tier; it converts as well as the paid tier on the thing that actually moves signups. See plans.
adjacent pages
- /for/small-business — solo and small-team operators driving signups and bookings from social bios
- /for/oauth-developers — the OAuth-redirect failure inside webviews, from the implementer's side
- /for/magic-link-products — products whose primary sign-in is a magic link that lands in the wrong browser
- /for/passkey-products — passkey sign-in flows that need the real browser to enroll and authenticate
- /for/stripe-merchants — checkout and billing flows that depend on the same logged-in session
The prospect who tapped your link came to sign up. Don't let the webview be the reason your best traffic never reaches the product.