For lead generation
Leads arrive as pending, get checked against the buyer's scrub, and only approved leads count toward a partner's payout and — by default — fire its postback.
Caps, de-duplication and per-event payouts keep volume and cost where the buyer agreed.
The challenge
In lead generation the gap between a submitted form and a paid lead is where money is lost. Four common leaks — and how TrackCrown closes them.
The buyer scrubs a share of every batch, but partners were already credited the moment the form was submitted.
With TrackCrown: set the offer's default status to pending. Leads are approved or rejected after review — one by one, in bulk or from the buyer's scrub file — and only approved leads are paid.
The same person submits twice, a form is replayed, or a lead ID arrives from two sources.
With TrackCrown: one conversion per click and event, and one per lead or order ID per offer. Repeats are stored as duplicates — visible in reports, never paid or posted back.
Buyers cap daily volume. Every lead over the cap is a lead nobody pays for.
With TrackCrown: daily, weekly, monthly and lifetime caps on clicks, conversions and payout, per offer and per partner, counted in your timezone. Leads over a cap are rejected with the reason cap_exceeded.
A partner sends traffic from dozens of placements and forms; the totals hide the ones that never qualify.
With TrackCrown: ten sub IDs and a source ID on every click, carried onto every lead, so approval rates can be compared by placement, form or creative.
Day to day
Define what a lead is worth, review and scrub, keep volume inside the buyer's caps, and pay only on what was approved.
Lead events
A lead offer can pay on more than one event, and keep the buyer's downstream outcome to itself.
Pay on the form
The default event is the submitted form, with a fixed payout per lead and the revenue the buyer pays you.
Add later steps
Phone verified, appointment kept or application funded — each as its own event with its own payout.
Keep outcomes private
A private event such as a bound policy records revenue for you without being shown to partners or firing their postbacks.
Hold everything for review
With the default status set to pending, nothing is payable until someone — or the scrub file — approves it.
Review & scrub
Work the pending queue by hand, or import the buyer's decisions and let the preview show exactly what will change.
Filter the pending leads
Reporting › Conversions filtered by status, offer, partner or date — with sub IDs, country and device on each row.
Approve or reject in bulk
Select leads, approve or reject them together and add a reason — partners see it next to each lead.
Import the scrub file
Matched by lead ID or click ID; each row shows the change it will make, and errors are listed before you apply.
Check the flags
Bot and data-centre clicks are flagged, so a source with poor traffic stands out before its leads are approved.
Caps
Caps are counted as leads arrive, and a capped day starts and ends at midnight in your workspace's timezone.
Cap the offer
Clicks, conversions or payout — daily, weekly (from Monday), monthly or lifetime.
Cap each partner
A partner can have its own caps on an offer, on top of the offer-wide ones.
Target and fall back
Limit countries, devices and operating systems; clicks that miss targeting or a click cap go to the fallback URL.
Pay on approval
Approval is the moment that matters: it fires the partner's postback and puts the lead on the next payout statement.
Postback on approval
Partner postbacks fire when a lead is approved, with macros such as {sub1}, {payout} and {status}; failed calls are retried automatically.
Statements from approved leads
Payout statements include approved leads only; late approvals land on the next statement.
Partners follow along
Pending, approved and rejected leads appear in the partner portal as they change.
Features that matter
The capabilities lead teams lean on. The plan comparison shows which plan includes each one.
Setup checklist
Where each step happens in the panel, and the guide that explains it.
Step 1: Create the lead offer
Offers › Offers
Destination URL of the form, payout and revenue per lead, attribution window, and default conversion status set to pending.
Offers & linksStep 2: Add the events you pay on
Offer › Events
Form submitted, phone verified, appointment kept — each with its own payout. Mark downstream outcomes private if partners should not see them.
Step 3: Set caps, targeting and a fallback
Offer › Caps · Offer › Targeting
The buyer's daily and monthly volume, per partner if needed, plus the countries and devices it accepts and where extra clicks go.
Step 4: Report leads from the form or CRM
Offer › Tracking & links
A postback with click_id, the lead ID as txid and, if your system already knows it, a status. Test with test=1 first.
Step 5: Approve partners for the offer
Partners › Affiliates
Approval-only visibility lets you vet each source before it sends leads, with partner-level caps and payouts.
Partner managementStep 6: Fire partner postbacks on approval
Affiliate › Postbacks
Partners are told about a lead when it is approved — or on any status, with {status} in the URL if they prefer.
Step 7: Agree the scrub file format
Reporting › Conversions › Import
Ask the buyer for a CSV with txid (or click_id) and status; optional columns adjust payout, revenue or sale amount.
Step 8: Pay on approved leads
Billing › Payouts
Payout statements include approved leads only. Leads approved after a statement was generated move to the next one.
FAQ
Working with a call centre, a CRM or a ping-post setup? Tell us how leads move today and we'll show you where tracking fits.
status=pending|approved|rejected). Later decisions come back as a scrub file you import — or, if you enable it, the buyer rejects its own leads with a reason in the advertiser portal and your team is notified. Approvals after the fact stay with your staff.click_id or txid to identify each lead, plus any of event, status, payout, revenue and sale_amount — up to 5,000 rows (2 MB) per file. Every row is previewed as an update, unchanged or error before anything is applied, and the import is recorded in the audit log.cap_exceeded. Links carrying url= for Google Ads are never redirected elsewhere — there, a reached cap is recorded for reporting only.Set up a lead offer with pending review, caps and a scrub import — we'll walk you through it.