Integrations — Framer

Affiliate tracking for your Framer site. One snippet, ten minutes.

Paste one script tag into Framer's Custom Code panel, keep the ?via= links your affiliates already share, and Qanary starts tracking through to your checkout — no plugin needed.

site settings → custom code → start of head. that's the whole install.

Beyond Framer's built-in tools

Framer ships beautiful sites. Attribution isn't built in.

However you're tracking referrals on Framer 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 → Start of <head>. Coupon-code fallback, fraud checks before commission, and payouts through Wise or PayPal — the same system whether you're on Framer or anywhere else.

How it works

Paste, stamp, verify. Three steps.

1. Paste the tracking snippet — Site Settings → Custom Code → Start of <head>. 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 — Framer sites typically link out to a Stripe or Lemon Squeezy checkout — keep ?via= on your CTAs, or wire Qanary.checkoutStamp() into the checkout URL (Lemon Squeezy: checkout[custom][qanary_via]=STAMP_REF).

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.

custom code · framer
<script src="https://app.qanary.cloud/qanary.js"
  data-qanary="YOUR_PROGRAM_SLUG" async></script>

Paste this exact tag into Site Settings → Custom Code → Start of <head>, publish, and it's live. Swap YOUR_PROGRAM_SLUG for the program slug from your Qanary dashboard.

What the snippet does

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 or Lemon Squeezy checkout URL, so a sale started from a Framer CTA 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.

Common Framer setups

Whatever's linked from your Framer site.

Framer → hosted checkout

A marketing site with buttons out to Stripe or Lemon Squeezy. The snippet's stamp appends to the checkout URL at click time.

Framer + a membership tool

Gated content behind Memberstack or Outseta on top of Framer — the same snippet keeps attributing while the membership tool handles access.

Marketing site, checkout elsewhere

Framer handles the front end; a separate app handles billing. Keep ?via= on the links 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.

At a glance

See it side by side.

Capability Tracking it yourself Qanary
Setup time on Framer 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
Why this beats a spreadsheet

It works the day you publish.

FAQ

Fair questions.

Where exactly does the snippet go in Framer?

Site Settings → Custom Code → Start of <head>, then publish. The snippet needs to be site-wide so it loads on every page a visitor might land on.

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.

How does attribution survive the jump to a hosted checkout?

A small embed script appends the stamp to the checkout URL at click time — client_reference_id for Stripe, checkout[custom][qanary_via] for Lemon Squeezy — or you can rely on the cookie alone if ?via= stays on the link.

I use Memberstack or Outseta for membership — does this still work?

Yes. The tracking snippet lives in Framer's Custom 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.

Go deeper

Everything you need to start tracking.

Paste the snippet. Start tracking tonight.

Join the waitlist now; when registration opens, wire your Framer site in ten minutes.

Join the waitlist