Affiliate tracking for your Base44 app. One snippet, ten minutes.
Base44 builds your app from a prompt, so the tracking snippet goes in the same
place you'd add Google Analytics or a Meta Pixel — the app's custom code / head
scripts setting. No settings field yet on your plan? Ask Base44's own AI builder
to add the tag to your page head directly. Either way, Qanary starts tracking
through to checkout, keeping the ?via= links your affiliates already
share.
custom code field, or just ask the builder: "add this script tag to my page head."
- ~10 minutes, no developer required
- Works with Stripe Checkout out of the box
- Free plan, no card required
Base44 ships a real app. Coupon fallback and fraud checks are still the hard part.
However you're tracking referrals in a Base44 app 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 your app's custom code settings, or pasted in by Base44's own AI. Coupon-code fallback, fraud checks before commission, and payouts through Wise or PayPal — the same system whether you're on Base44 or anywhere else.
Paste, stamp, verify. Three steps.
1. Paste the tracking snippet — open your app's Settings and look for a custom code / head-scripts field, the same place you'd drop Google Analytics or a Meta Pixel. Don't see one? Ask Base44's builder chat to add the tag to your page head instead.
2. Carry the referral into checkout — wherever your app's
checkout flow calls Stripe, read Qanary.checkoutStamp()
client-side and send stamp.ref into client_reference_id.
3. Verify — open your app 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 your custom code field, or ask
Base44's AI to add it to the page head. 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 flow
Feeds stamp.ref into whatever step in your Base44 app kicks off
Stripe Checkout, 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.
Whatever kicks off your checkout.
Base44 app → Stripe Checkout
Your app's built-in checkout action calls Stripe. The snippet's stamp feeds straight into that call.
Base44 app with built-in user accounts
Gated content behind Base44's built-in auth — the snippet in the page head keeps attributing independent of the access logic.
Marketing page in Base44, app elsewhere
A Base44 landing page linking out to a separate app for checkout. Keep ?via= on the links 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 Base44 | 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 in a field or page your app already exposes — nothing to submit for review, nothing to wait on.
- Doesn't slow down your app. 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.
- Base44's own AI can paste it for you. No custom code field yet? Ask the builder chat directly to add the script tag to your page head, then verify with a test
?via=link.
Fair questions.
Where exactly does the snippet go in Base44?
Look in your app's Settings for a custom code / head-scripts field — the same place you'd add Google Analytics or a Meta Pixel. If that's not available on your plan, ask Base44's AI builder to add the tag to your page head instead.
Does the snippet slow down my app?
No — it loads with the async attribute, so it fetches in the
background and never blocks page rendering.
How does attribution survive Base44's built-in checkout flow?
Read Qanary.checkoutStamp() client-side right before your app's checkout action fires, and send stamp.ref into client_reference_id when it creates the Stripe Checkout session.
Does this work with Base44's built-in user accounts?
Yes. The tracking snippet runs independently of Base44's auth and access logic, so it keeps attributing regardless of how you gate content.
Can an AI agent install this for me?
Yes — Base44's own builder chat can add the script tag directly. If you also use Claude Code, Cursor, or Codex elsewhere in your stack, point it at Qanary's llms.txt and it can wire the webhook too.
Everything you need to start tracking.
Paste the snippet. Start tracking tonight.
Join the waitlist now; when registration opens, wire your Base44 app in ten minutes.
Join the waitlist