You aggregate traffic from dozens of affiliates and route it to buyers. That only scales if partners can onboard themselves, submit safely, and get paid transparently — without seeing your filters or each other. Lead Router is the partner network layer: a self-serve portal, campaign posting keys, payouts, postbacks, and cross-partner dedup.
Self-serve
Per-partner portal
Per campaign
Posting keys
CAPI + CPA
Conversions
Cross-partner
Dedup
What Breaks At Scale
Four things that turn a growing affiliate base into a full-time job — unless the portal handles them for you.
Without a self-serve portal, each new affiliate means provisioning logins, keys, and posting instructions by hand. That overhead caps how many partners you can actually run.
Raw rejection reasons and unfiltered API responses let partners reverse-engineer your filters, your pricing, and each other’s activity. A leaky portal is a competitive liability.
When two partners send the same person, you either pay both payouts and eat the dupe, or you sell a buyer a lead they already have. Cross-partner dedup has to happen at intake.
Without postbacks and conversion tracking, partners chase raw lead counts. You need CPA postbacks and platform conversions so everyone optimizes on what actually monetizes.
How Lead Router Solves It
Self-serve onboarding, safe submissions, transparent payouts, and conversion tracking — the full affiliate-network stack.
Each partner logs into their own portal: an offers marketplace to browse and request campaigns, their posting specs, API keys, payout history, a posting log of every submission, sub-users, and webhooks. Partners create their own sub-users and keys without you provisioning each one by hand.
Every campaign carries its own posting key. Partners post leads with that key as a bearer token — it identifies the campaign and the partner in one credential. Scoped partner API keys read campaigns, leads, payouts, and posting logs. See the lead API.
Payouts are tracked per partner with reports in the portal. Each campaign carries its own payout terms, and the posting log records what was accepted, rejected, or paid, so partners can reconcile against your numbers instead of emailing for a spreadsheet. Roll it up in reporting.
Partner API responses are stripped to an allowlist, and rejection reasons are sanitized so partners cannot reverse-engineer your filters or other partners’ activity. The portal is self-serve without being a data leak.
The engine deduplicates across partners at intake, so the same person submitted through two sources does not get paid twice or sold twice. See lead dedup.
Configure CPA postback URLs that fire when a lead converts, and push conversions to Google Ads and to Facebook via the Conversions API (CAPI). Partners and your own media buying optimize on downstream conversions, not just raw lead volume. Pair it with the referral program to grow the partner base.
Frequently Asked
Questions network operators ask before moving their partners onto a new platform.
Yes. Each partner gets a self-serve portal with an offers marketplace, their campaigns and posting specs, API keys, payout history, a posting log of every submission, sub-users, and webhooks. Partners can create sub-users and their own API keys without you provisioning each one manually.
Each campaign has its own posting key. A partner posts leads to the submission endpoint with that key as a bearer token, which identifies both the campaign and the partner. Partners can also generate scoped API keys from their portal to read campaigns, leads, payouts, and posting logs.
Payouts are tracked per partner with payout reports available in the portal. Each campaign carries its own payout terms, and the posting log records what was accepted, rejected, or paid so partners can reconcile against your numbers.
Yes. You can configure CPA postback URLs that fire when a lead converts, and push conversions to Google Ads and to Facebook via the Conversions API (CAPI). That lets partners and your own media buying optimize on downstream conversion events, not just raw lead volume.
Partner API responses are stripped to an allowlist, so partners see only the fields they should. Rejection reasons shown to partners are sanitized so they cannot reverse-engineer your filters or other partners’ activity. Cross-partner deduplication also stops the same lead being sold twice across different sources.
Built For Networks
Offers marketplace, campaign posting keys, payouts and reports, sanitized partner responses, cross-partner dedup, and CPA conversion tracking. One platform from affiliate submit to buyer delivery.
All features included from day one.