Integrations — Outseta

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

Paste one script tag into your site's header, keep the ?via= links your affiliates already share, and Qanary attributes the sale straight through Outseta's embedded checkout.

site → settings → custom code → header. that's the whole install.

Beyond Outseta's built-in tools

One CRM, billing, and support suite. One attribution spine to match.

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

How it works

Paste, stamp, verify. Three steps.

1. Paste the tracking snippet — Site → Settings → Custom Code → Header. 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 — Outseta's embedded Stripe checkout inherits the page context — keep ?via= on your links and the first-party cookie carries attribution to the conversion webhook. For belt-and-braces, add the stamp to Outseta's signup custom properties and forward it to Stripe metadata.

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 · outseta
<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, 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 embedded checkout

Inherits the page context into Outseta's embedded Stripe checkout, with an optional signup custom-property fallback for belt-and-braces attribution.

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 Outseta setups

Whatever Outseta is running for you.

Gated content behind Outseta

The tracking snippet sits independently of Outseta's own auth logic — it attributes the referral before Outseta even checks membership status.

Free trial → paid conversion

A visitor signs up free through Outseta and upgrades later — the attribution cookie set at first visit still gets credit when the upgrade fires the webhook.

Multiple pricing plans

Whichever plan a referred customer picks, the commission reflects the actual sale — no flat per-signup rate that under- or over-pays.

Migrating from another tool

Swap the old tracking snippet for Qanary's in the same header 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 Outseta Custom dev project ~10 minutes
Attributes through embedded checkout 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 Outseta?

Site → Settings → Custom Code → Header, then publish. It needs to load site-wide, including on pages that host Outseta's embedded checkout.

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 attribution survive Outseta's embedded checkout?

Yes — because the checkout is embedded on your own page, it inherits the first-party attribution cookie the snippet already set, no extra wiring required.

Can I double up with Outseta's signup custom properties?

Yes — for belt-and-braces attribution, add the Qanary stamp to a custom property on the signup form and forward it into Stripe metadata alongside the cookie-based signal.

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 Outseta site in ten minutes.

Join the waitlist