On this page
You ran a Bandcamp Friday sale last weekend and threaded it across four TikToks pinned to your profile. By Sunday night the TikTok analytics showed roughly 6,200 outbound clicks on your Bandcamp bio link and three support emails in your inbox — all variations of "I bought the album but the download link never came" — from listeners whose order confirmations show up in your Bandcamp seller dashboard but who never received the email with the actual download URL. By Monday morning the support thread was at eleven messages and your refund rate for the weekend sat at 4%.
The pattern is a Bandcamp-specific consequence of the vanishing visitor. Bandcamp's checkout works — the credit card processes, the order lands in the dashboard, the fan's payment clears — but the email-confirmation handshake that ties the order to the fan's Bandcamp account fails inside TikTok's webview. The download link gets emailed to an address the in-app browser couldn't validate against an existing account, the fan's purchase doesn't appear in their Bandcamp collection, and the support burden lands on you. The sale completed; the post-sale handoff didn't.
what specifically breaks on Bandcamp's checkout from TikTok
Bandcamp's purchase flow has a quirk that most music checkout flows don't: it's structured to serve both logged-in collectors (fans with Bandcamp accounts) and anonymous buyers (fans buying without an account). For logged-in collectors, the post-sale handoff is automatic — the order lands in their Bandcamp collection, the download is available in the app, the support burden is zero. For anonymous buyers, Bandcamp emails a download link to the address provided at checkout, and the fan downloads from that email link. Both flows work — outside an in-app browser.
Inside TikTok's webview, three Bandcamp-specific failure modes stack:
1. The fan's Bandcamp session isn't there to recognize them as a collector. A fan with an existing Bandcamp account who taps your link from TikTok lands on the album page logged out. The "Add to collection" pathway that would have routed the purchase through their existing account doesn't appear. They proceed as an anonymous buyer instead, paying at the same price but losing the collection-side benefits.
2. The checkout cookie writes to the wrong jar. Bandcamp's checkout uses an in-session cookie to associate the cart, the payment, and the post-sale email together. Inside the in-app browser, the cookie writes to the TikTok webview jar. When Bandcamp's post-purchase logic checks for the cookie to confirm the buyer, the cookie's there for the duration of the in-app browser session — but if the fan closes the TikTok tab before the confirmation email lands (which is common, given the email may take 30–60 seconds), and reopens Bandcamp in a different browser later to download, the session has no continuity. Bandcamp's "check your purchases" page in their actual app or default browser shows nothing.
3. The download email links back to a Bandcamp authentication context the fan can't satisfy. The email Bandcamp sends contains a download link that requires either the fan's account login or a one-time email-verification flow. When the fan taps the download link from their email app, the link opens in their actual default browser (Safari or Chrome), where they're either logged out of Bandcamp entirely or where the verification token sent at purchase time doesn't match because it was tied to the in-app browser session. Bandcamp shows an error: "this download link has expired" or "we couldn't verify your purchase." The fan emails you.
what it's costing on Bandcamp specifically
Bandcamp's purchase data is unusual among streaming platforms in that there's a direct revenue-per-click number. A failed Bandcamp checkout isn't a "did the algorithm count it" question — it's a real refund, a real support ticket, or worst case, a real chargeback when the fan disputes the charge with their bank because they "never received the product."
The cost shape on Bandcamp from TikTok-driven traffic, based on the support-ticket and refund data Bandcamp-active artists have published in r/Bandcamp and similar venues: 2–5% of TikTok-attributed purchases generate a post-sale support ticket, with the most common ticket being "I bought it, where's my download." A fraction of those become refunds; a smaller fraction become chargebacks. The compound cost is the refund rate plus the time spent on support plus the Bandcamp Friday-window goodwill burned with the fans who got a worse experience than they paid for.
Independent measurements on in-app-browser-escape routing for Bandcamp specifically aren't published widely because Bandcamp's scale is smaller than Spotify's, but artists running A/B tests on their own redirects have reported support-ticket rate dropping to roughly the 0.5% baseline that desktop and direct-URL Bandcamp traffic generates. The lift is in support cost saved more than in incremental sale capture, though the incremental sale lift exists too (anonymous-buyer-to-collector conversion roughly doubles when the fan starts the checkout from a context where their Bandcamp session is present).
how linkboo's escape flow handles Bandcamp specifically
The Bandcamp escape is engineered around the email-handoff problem rather than the OAuth or universal-link problem that hits the streamers. Bandcamp's mobile experience is web-first (no dominant mobile app the way Spotify or Apple Music have), which means the escape's primary job is to land the fan in the browser where their Bandcamp session cookie lives, in a way that the post-purchase email and the download link will both function.
When a fan taps a linkboo-wrapped Bandcamp link from TikTok:
- Linkboo's landing loads inside TikTok's webview for ~200ms.
- The escape detects TikTok's in-app browser, identifies the destination as Bandcamp, and hands the visitor off to their device's real browser — Safari on iOS, Chrome on Android.
- Safari (iOS) or Chrome (Android) opens with the Bandcamp album page. The fan's Bandcamp session cookie is present.
- The fan is recognized as a collector (if they have an account). The "Add to collection" path is available. The checkout cookie writes to Safari/Chrome's jar — the same jar the post-purchase email's download link will be opened from when the fan taps it.
- Purchase completes. Confirmation email arrives. The fan taps the download link in their email app; it opens in Safari/Chrome where the verification token matches; the download starts. The album appears in their Bandcamp collection.
The piece linkboo handles that generic escapes miss is session-cookie continuity between the checkout and the email-link follow-through. The escape doesn't just land the fan in their default browser at purchase time — it ensures the cookie that ties the purchase to the fan persists across the gap between checkout and email-tap, so the download flow operates in the same browser context throughout.
related Music fixes
The Music cluster covers play-counting, pre-save, and purchase flows. Bandcamp's failure mode is most similar to SoundCloud's (session-dependent engagement that strips when the cookie jar is wrong) and most adjacent to e-commerce flows generally:
- SoundCloud link in app browser — the follow/repost engagement-stripping case
- Spotify pre-save link from Instagram — the OAuth pop-up failure mode for streaming platforms
- Apple Music link from TikTok — the universal-link interception problem
- Etsy link from TikTok bio — the most structurally similar e-commerce checkout case, where merch and physical-good sales overlap with Bandcamp's vinyl/cassette flow
For the underlying explanation of why authenticated post-sale flows break in social-app webviews, why your bio link logs people out is the long-form thesis.
for musicians using Bandcamp as the primary revenue channel
If Bandcamp is your primary revenue channel — which is the case for most independent labels and self-releasing artists with an established audience — the musicians persona page covers the Bandcamp Friday cadence, the merch-bundle pattern for higher-AOV checkouts, the pre-order discount mechanics, and the support-burden reduction that comes with reducing the in-app browser-related ticket volume.
Not ready to fix it? Compare the escape tools for music links →
Will the escape preserve Bandcamp's "fan-funded campaign" attribution if I'm running one?
Yes. Bandcamp's fan-funding campaigns track contributions against the campaign's URL slug; the escape preserves the URL path and the campaign attribution rides through unchanged. Contributions count toward the campaign goal the same way they would from a direct URL.
Does this work for Bandcamp's vinyl/cassette physical-merch checkouts as well as the digital download flow?
Yes. Physical-merch checkout uses the same session-cookie structure as digital. The only difference is the post-purchase email contains shipping confirmation rather than a download link, but the email-tap-to-account verification flow operates identically and benefits from the same session-cookie continuity.
What about Bandcamp Friday — the day when Bandcamp waives its share and artists get 100% of the sale price?
Bandcamp Friday traffic spikes hit the in-app browser failure mode harder than normal traffic because the higher volume includes more new-to-Bandcamp listeners who don't have existing accounts. The escape's lift is proportionally larger on Bandcamp Fridays for the same reason. Several artists who've measured the Bandcamp Friday lift have reported the largest single-day sale recovery of their Bandcamp tenure.
Does the escape preserve Bandcamp's "pay what you want" pricing flow?
Yes. PWYW pricing operates on the album page after the escape lands the fan in their default browser. The slider, the suggested price, the minimum price — all behave normally because they're rendered in a browser context Bandcamp expects.
Will the escape help with Bandcamp's mobile app deep-link behavior?
Bandcamp's mobile app handles deep links from `bandcamp.com` URLs as universal links on iOS and as App Links on Android. The escape's iOS universal-link handoff routes through Safari, where iOS will hand off to the Bandcamp app if installed. Fans with the Bandcamp app land in the app; fans without it land in the logged-in mobile web context. Both work.
What about chargeback risk on the support tickets the escape doesn't catch?
Bandcamp's chargeback policy treats "buyer didn't receive product" claims by referencing the order record and the email-delivery log. The escape reduces the underlying frequency of those claims by ensuring the email-delivery and download-link verification flow completes cleanly. For the residual cases where a chargeback fires anyway, Bandcamp's seller support is responsive in providing the delivery-log evidence that protects the artist.