Affiliate tracking for your TinyPages site. One snippet, ten minutes.
Paste one script tag into TinyPages' custom code field, keep the ?via= links your affiliates already share, and Qanary starts tracking through to your checkout — no plugin needed.
site settings → custom code, header field. that's the whole install.
- ~10 minutes, no developer required
- Works with Stripe Payment Links out of the box
- Free plan, no card required
A simple landing page can still lose sales to a blocked cookie.
However you're tracking referrals on TinyPages 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 Site settings → Custom code, header field. Coupon-code fallback, fraud checks before commission, and payouts through Wise or PayPal — the same system whether you're on TinyPages or anywhere else.
Paste, stamp, verify. Three steps.
1. Paste the tracking snippet — Site settings → Custom code, header field. It sets the
first-party attribution cookie when a visitor lands with
?via=AFFILIATE_CODE and records the touchpoint.
2. Carry the referral into checkout — if you run Stripe Checkout via a server action or the Stripe plugin, read Qanary.checkoutStamp() in the page workflow and send stamp.ref into client_reference_id (Stripe) or customData.qanary_ref (Paddle).
3. Verify — open your site 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>
Paste this exact tag into Site settings → Custom code, header field, publish, and it's
live. 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 link
Carries the referral into a Stripe Payment Link or your Checkout Session, 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.
Simple site. Still fully attributed.
TinyPages → Stripe Payment Links
The classic shape: a landing page with a button out to a hosted Payment Link. The stamp appends to the link automatically.
Launch-day coupon codes
No custom code slot to spare on launch day? A personal coupon code per affiliate attributes the sale with zero snippet at all.
Landing page, checkout elsewhere
TinyPages handles the landing page; a separate app handles billing. Keep ?via= on the link out and the cookie carries the referral across.
Migrating from another tool
Swap the old tracking snippet for Qanary's in the same custom code field — existing ?via= links your affiliates already shared keep working.
See it side by side.
| Capability | Tracking it yourself | Qanary |
|---|---|---|
| Setup time on TinyPages | 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 publish.
- Live the moment you publish. The snippet is a plain script tag pasted into a field TinyPages already gives you — nothing to submit for review, nothing to wait on.
- Doesn't slow down your site. 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.
- An agent can paste it for you. Point Claude Code, Cursor, or Codex at Qanary's llms.txt and it can install the snippet and verify it in one prompt.
Fair questions.
Where exactly does the snippet go in TinyPages?
Site settings → Custom code, header field, then publish. The snippet needs to load on every page a visitor might land on with a ?via= link.
Does the snippet slow down my site?
No — it loads with the async attribute, so it fetches in the
background and never blocks page rendering.
Does the snippet slow down a simple landing page?
No — it loads with the async attribute, so it fetches in the background and never blocks the fast load time a landing page depends on.
How does attribution survive the jump to Stripe?
A small embed script appends client_reference_id to the Payment Link at click time, or you can simply keep ?via= on the link and let the cookie carry it through checkout.
Can an AI agent install this for me?
Yes — point Claude Code, Cursor, or Codex at Qanary's llms.txt
and it can install the tracking snippet and wire a webhook from a single
prompt. See the AI agent page for the exact setup.
Everything you need to start tracking.
Paste the snippet. Start tracking tonight.
Join the waitlist now; when registration opens, wire your TinyPages site in ten minutes.
Join the waitlist