Paste one script tag into your site header, give affiliates a personal coupon code for Podia's own checkout, and Qanary attributes every course and digital product sale.
settings → code snippets → site header. that's the whole install.
However you're tracking referrals on Podia 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:
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.
One script tag in Settings → Code snippets → Site header. Coupon-code fallback, fraud checks before commission, and payouts through Wise or PayPal — the same system whether you're on Podia or anywhere else.
1. Paste the tracking snippet — Settings → Code snippets → Site 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 — Podia checkouts run on Podia's own domain, so give each affiliate a personal coupon code (the deterministic rung) or keep ?via= on links into your Podia storefront for the cookie rung.
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 Settings → Code snippets → Site header, publish, and it's
live. Swap YOUR_PROGRAM_SLUG for the program slug from your
Qanary dashboard.
Reads ?via=AFFILIATE_CODE off the URL the moment a visitor lands
and records the touchpoint — no configuration beyond the program slug.
Since checkout happens on Podia's own domain, a personal coupon code per affiliate is the deterministic signal — no cross-domain stamp required.
Ask your coding agent to run diagnose_attribution and it walks
visit → identify → webhook → attribution → ledger, so a stalled conversion is
never a mystery.
Each affiliate's personal coupon code attributes the sale the moment it's applied at Podia's checkout — no snippet needed on that step at all.
Keep ?via= on links into your storefront and the cookie rung picks up the referral before the visitor ever reaches checkout.
Whether it's a one-off digital product or a recurring Podia membership, the same coupon-code or link signal attributes the sale.
Swap the old tracking snippet for Qanary's in the same site header field — existing ?via= links and coupon codes your affiliates already shared keep working.
| Capability | Tracking it yourself | Qanary |
|---|---|---|
| Setup time on Podia | Custom dev project | ~10 minutes |
| Deterministic attribution on Podia's own checkout | No | Yes |
| Fraud checked before commission is owed | No | Yes |
| Falls back with no page to instrument | No | Yes, via coupon codes |
async,
so it never blocks page rendering while it sets the attribution cookie.
Settings → Code snippets → Site header, then save. It covers your storefront pages; Podia's own checkout is attributed separately via coupon codes.
No — it loads with the async attribute, so it fetches in the
background and never blocks page rendering.
Podia's checkout runs on Podia's own domain rather than yours, so there's no page to pass a client_reference_id-style stamp through. A personal coupon code per affiliate is the deterministic signal that survives the handoff.
Yes — coupon-code and link-based attribution both work the same way regardless of whether you're selling a course, a digital download, or a Podia membership.
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.
Join the waitlist now; when registration opens, wire your Podia storefront in ten minutes.
Join the waitlist