For Affiliate & Partner Networks
Run a network with a portal for each partner. Partners can find offers, submit traffic with their posting key and campaignId, and review payouts. Your contracts choose the buyers, and each partner sees only its own records.
Self-serve
Per-partner portal
Per partner
Posting keys
CAPI + CPA
Conversions
Cross-partner
Dedup
What Breaks At Scale
Running a partner network is an operations problem
Four things that turn a growing affiliate base into a full-time job unless the portal handles them for you.
Every partner means manual onboarding
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.
Partners can see too much
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 business risk.
The same lead gets sold twice
When two partners send the same person, you either pay both payouts and absorb the duplicate, or you sell a buyer a lead they already have. Cross-partner dedup has to happen at intake.
You optimize on volume, not conversions
Without postbacks and conversion tracking, partners chase raw lead counts. You need CPA postbacks and platform conversions so everyone optimizes on what actually makes money.
How Lead Router Solves It
A partner network with less manual work
Self-serve onboarding, safe submissions, transparent payouts, and conversion tracking on one platform.
Self-serve partner portal
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.
Partner posting keys and API
Each partner uses its posting key across its campaigns. Send that key as the bearer token and put campaignId in the request body. Separate portal API keys let a partner read the records its role allows. See the lead API.
Payouts and payout reports
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.
Partners see only what they should
Partner API responses are trimmed to an approved list of fields, and rejection reasons are cleaned up so partners cannot reverse-engineer your filters or other partners’ activity. The portal is self-serve without being a data leak.
Cross-partner deduplication
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.
Postbacks and CPA conversion tracking
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.
Recruit publishers and connect their outcomes
Explore the detailed workflow and configuration requirements for each capability.
Publisher recruitment
Public signup can collect custom questions and terms, with manual or configured automatic approval. The publisher portal provides campaign instructions, source attribution and posting history under the approved role.
Feedback and payout
Send the ad-platform and webhook events you set up to the systems that buy your traffic. A payout basis of Sold or Delivered, plus reporting scoped to each partner, shows partners what they have earned separately from what has been paid out.
Frequently Asked
FAQ
Questions network operators ask before moving their partners onto a new platform.
Do partners get their own login and portal?
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.
How do partners authenticate lead submissions?
Each partner has a posting key shared across its campaigns. The partner sends it as a bearer token and includes the campaignId in the lead submission. Scoped portal API keys give separate access to campaigns, leads, payouts, and posting logs.
How are partner payouts handled?
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.
Do you fire postbacks and conversion pixels?
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.
How do you prevent partners from seeing each other’s data or gaming rejections?
Partner API responses are trimmed to an approved list of fields, so partners see only what they should. Rejection reasons shown to partners are cleaned up 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
Give every partner a portal, and keep control yourself
Offers marketplace, partner posting keys, payouts and reports, sanitized partner responses, cross-partner dedup, and CPA conversion tracking. One platform from affiliate submit to buyer delivery.
Every feature is part of the plan. Usage is billed in credits.