Affiliate tracking for your Webflow site. One snippet, ten minutes.
Paste one script tag into Webflow's Custom Code panel, keep the ?via=
links your affiliates already share, and Qanary starts tracking through to your
checkout — no marketplace app, no waiting on a review.
project settings → custom code → head code. that's the whole install.
- ~10 minutes, no developer required
- Works with Stripe Payment Links out of the box
- Free plan, no card required
Webflow isn't Shopify. Most affiliate tools stop there.
Affiliate platforms build their integrations around ecommerce platforms first — Webflow support, if it exists at all, is usually a forum thread suggesting you hire a developer. Here's the difference one script tag makes:
Typical affiliate software
No Webflow app in the marketplace, so tracking becomes a custom project — a developer wiring a pixel by hand, billed by the hour.
Qanary
One script tag in Project Settings → Custom Code → Head Code. It reads the
?via= parameter that's already in your affiliate links and starts
tracking immediately.
Paste, stamp, verify. Three steps.
1. Paste the tracking snippet — Project Settings → Custom Code
→ Head Code. 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 — on Stripe Payment Links,
append ?client_reference_id=STAMP_REF at click time with a small
embed script, or simply keep ?via= on inbound links and let the
cookie carry it.
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 Project Settings → Custom Code
→ Head Code, publish the site, 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 Stripe Payment Links
Carries the referral through to checkout as client_reference_id,
so a sale on a hosted Payment Link 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's behind your Webflow front end.
Webflow → Stripe Payment Links
The most common shape: a marketing site with buttons out to a hosted Payment Link. The snippet stamps the click-through automatically.
Webflow + a membership tool
Gated content behind Memberstack or Outseta on top of Webflow — the same snippet in the head keeps attributing while the membership tool handles access.
Marketing site, checkout elsewhere
Webflow handles the front end; a separate app handles billing. Keep
?via= on the links out and the cookie carries the referral across
the handoff.
Migrating from another tool
Swap the old tracking snippet for Qanary's in the same Head Code field —
existing ?via= links your affiliates already shared keep working.
See it side by side.
| Capability | Typical affiliate software | Qanary |
|---|---|---|
| Native Webflow support | Rare | One script tag |
| Setup time | Custom dev project | ~10 minutes |
| Works with Stripe Payment Links | Depends on manual wiring | Yes, out of the box |
| Falls back with no page to instrument | No | Yes, via coupon codes |
It works the day you publish.
- No marketplace app to wait on. The snippet is a plain script tag pasted into a field Webflow already gives you — nothing to submit for review.
- Doesn't touch your Lighthouse score. Loads with
async, so it never blocks the render Webflow's own site speed grading measures. - 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 Webflow?
Project Settings → Custom Code → Head Code, then publish the site. The
snippet needs to be on every page a visitor might land on with a
?via= link, so Head Code (site-wide) is the right place rather
than a single page's settings.
Does the snippet slow down my site or hurt my Webflow speed score?
No — it loads with the async attribute, so it fetches in the
background and never blocks page rendering.
How does attribution survive the jump to Stripe Payment Links?
A small embed script appends ?client_reference_id=STAMP_REF to
the Payment Link at click time, or you can simply keep ?via= on
the link and let the cookie carry it through checkout. See the
Stripe Payment Links recipe
for the exact setup.
I use Memberstack or Outseta for membership — does this still work?
Yes. The tracking snippet lives in Webflow's Head Code independent of whatever membership tool gates your content, so it keeps attributing regardless of which one you run.
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 Webflow site in ten minutes.
Join the waitlist