Affiliate tracking for your Bolt.new app. One snippet, ten minutes.
Bolt.new generates a real codebase and hands you the editor right in the browser,
so the tracking snippet is just another line in index.html. Prompt
Bolt's AI to add it, or flip to the code pane and paste it yourself, then deploy.
Keep the ?via= links your affiliates already share and Qanary starts
tracking through to checkout.
prompt it: "add this script tag to the head of index.html." or paste it in the code pane yourself.
- ~10 minutes, no developer required
- Works with Stripe Checkout out of the box
- Free plan, no card required
Bolt gives you the whole codebase. Coupon fallback and fraud checks are still the hard part.
However you're tracking referrals in a Bolt.new app today — a spreadsheet, a generic pixel, or nothing yet — attribution needs to survive ad blockers, the commission math needs to survive an audit, and the payout needs to go out on a rail you already use. Here's what one script tag adds:
Tracking it yourself
Basic click tracking at best — no coupon-code fallback for ad blockers or podcasts, no fraud check before a commission is owed, and payouts mean a manual spreadsheet.
Qanary
One script tag in index.html. Coupon-code fallback, fraud checks
before commission, and payouts through Wise or PayPal — the same system whether
you're on Bolt.new or anywhere else.
Prompt, stamp, verify. Three steps.
1. Paste the tracking snippet — prompt Bolt: "add this script
tag to the <head> of index.html." Or toggle from Preview to
the code pane and paste it in yourself.
2. Carry the referral into checkout — wherever your app calls
Stripe Checkout (a Netlify function, an API route, whatever Bolt scaffolded),
read Qanary.checkoutStamp() client-side and send
stamp.ref into client_reference_id.
3. Verify — open your deployed app with a test
?via=, run a test-mode checkout, and confirm the conversion lands
attributed — or ask your coding agent to run the MCP
diagnose_attribution tool.
<script src="https://app.qanary.cloud/qanary.js" data-qanary="YOUR_PROGRAM_SLUG" async></script>
Prompt Bolt to paste this exact tag into
index.html's <head>, or add it yourself in the
code pane, then deploy. Swap YOUR_PROGRAM_SLUG for the program
slug from your Qanary dashboard.
One tag. Three jobs.
Sets the attribution cookie
Reads ?via=AFFILIATE_CODE off the URL the moment a visitor lands
and records the touchpoint — no configuration beyond the program slug.
Stamps your Checkout call
Feeds stamp.ref into whatever function creates the Stripe
Checkout session — a Netlify function, an API route, or a call Bolt scaffolded
for you — so a sale still traces back to the right affiliate.
Verifiable end to end
Ask your coding agent to run diagnose_attribution and it walks
visit → identify → webhook → attribution → ledger, so a stalled conversion is
never a mystery.
Whatever function runs your checkout.
Bolt.new + Netlify function → Stripe Checkout
The most common shape after a one-click Netlify deploy: a serverless function creates the Checkout session. The snippet's stamp feeds straight into that call.
Bolt.new + Supabase auth
Gated content behind Supabase (or another backend Bolt wired up) — the snippet in index.html keeps attributing independent of the access logic.
Marketing page in Bolt, app elsewhere
A Bolt-built landing page linking out to a separate app for checkout. Keep ?via= on the links and the cookie carries the referral across.
Migrating from another tool
Swap the old tracking snippet for Qanary's in index.html — existing ?via= links your affiliates already shared keep working.
See it side by side.
| Capability | Tracking it yourself | Qanary |
|---|---|---|
| Setup time on Bolt.new | Custom dev project | ~10 minutes |
| Coupon-code fallback for ad blockers | No | Yes |
| Fraud checked before commission is owed | No | Yes |
| Falls back with no page to instrument | No | Yes, via coupon codes |
It works the day you deploy.
- Live the moment you deploy. The snippet is a plain script tag in a file Bolt already generated — nothing to submit for review, nothing to wait on.
- Doesn't slow down your app. Loads with
async, so it never blocks page rendering while it sets the attribution cookie. - Coupon codes cover the rest. A podcast mention or a DM with no link at all still attributes through a coupon code — see links & coupon codes.
- Bolt's own AI can paste it for you. You don't need a separate coding agent — prompt Bolt directly to add the script tag, then verify with a test
?via=link.
Fair questions.
Where exactly does the snippet go in Bolt.new?
index.html's <head>. Prompt Bolt's AI to add it, or switch from Preview to the code pane and paste it in yourself.
Does the snippet slow down my app?
No — it loads with the async attribute, so it fetches in the
background and never blocks page rendering.
How does attribution survive a Stripe Checkout call in Bolt.new?
Read Qanary.checkoutStamp() client-side before your app calls its checkout function — a Netlify function or API route Bolt scaffolded — and forward stamp.ref into client_reference_id.
Does this survive Bolt regenerating parts of my app?
The snippet lives in index.html, which Bolt rarely rewrites when iterating on components. If you ask it to rebuild index.html specifically, just ask it to keep the Qanary script tag in place.
Can an AI agent install this for me?
Yes — Bolt's own AI can paste the snippet directly. If you export to GitHub and use Claude Code, Cursor, or Codex on the repo too, point it at Qanary's llms.txt and it can wire the webhook as well.
Everything you need to start tracking.
Prompt it, paste it, start tracking tonight.
Join the waitlist now; when registration opens, wire your Bolt.new app in ten minutes.
Join the waitlist