Features
Link & Conversion Tracking
First-party click, lead and payment attribution from one script tag.
A visitor clicks an affiliate link, the tracking script stores a first-party visitor id, the visitor signs up, then pays, and the payment becomes a commission for the affiliate.
01 /Overview
Add one script tag and every referral link, coupon and checkout on your site is attributed. Clicks are stored in a first-party cookie on your root domain, mirrored in localStorage, and tied to the signup and the payment that follow, so affiliates are credited for the customers they actually bring.
02 /How it works
The script records the click and stores a visitor id in a first-party cookie for the campaign's cookie window.
AffTrack.lead({ email, customer_id }) ties the new user to the referral. Attribution is last click within the window.
Your billing webhook or the conversion API reports the payment; a pending commission is created at the campaign's rate.
Full refunds reject the commission, partial refunds shrink it, and paid ones are clawed back from the next payout.
03 /In depth
Referral parameters are set per campaign and baked into the script, so ?ref=, ?via=, hash links like #via-jane and the parameters of other platforms (fpr, lmref, tolt, aff) all work. Migrating from another tool doesn't break a single link that's already out there.
Each click carries sub-IDs sub1–sub5, UTM tags, ad click ids (gclid, fbclid, msclkid, ttclid), page title and language. Device, browser, OS and country are derived server-side. Crawlers and link previews are ignored, and repeat clicks by the same visitor within 30 minutes count once.
The visitor id is stored on the detected root domain, so marketing site, app and docs subdomains share it. data-domains carries it across separate domains. Stripe Payment Links, pricing tables and buy buttons get client_reference_id automatically, Paddle gets customData, and forms get a hidden aff_vid field.
With data-consent="required" the script stores and sends nothing until you call AffTrack.consent(true), so it fits the cookie banner you already have.
04 /FAQ
Yes. The visitor id is a first-party cookie on your own root domain, mirrored in localStorage, and with a branded tracking domain the script and tracking calls are served from your domain too.
Each campaign sets its cookie window in days and whether the first or the last click wins. Leads can also expire after a set time.
Yes. POST /track/conversion with your secret key, a unique event_id, the customer id and the amount in minor units. Repeated event ids are ignored, so retries are safe.
05 /Related
Connect your billing, add one script tag and invite your first partners. Import affiliates, codes and history from Rewardful, FirstPromoter, Tolt or a CSV.