Join Kapvexa
Every conversion Kapvexa pays out has already been through the same five stages — routed, tracked, verified, reviewed, and paid. Here's what actually happens at each one.
A visitor lands on a publisher's link, smartlink, or pixel-tagged page. Kapvexa opens a session and assigns it a click ID — the thread that ties everything downstream back to the publisher who sent it, no matter how many steps the visitor takes after.
If the publisher is running a smartlink rather than a single fixed offer, that click is auto-routed to whichever live campaign fits the visitor's GEO and vertical best — so one link keeps earning even after any single offer pauses or caps out.
The visitor completes whatever the campaign is paying for — a sale, a lead, an install. What counts as a conversion is defined by the advertiser up front, so publishers know exactly what they're being measured against before they send traffic.
Server-to-server postback is the default: the advertiser's own backend confirms the conversion directly to Kapvexa, matched to the original click ID. That confirmation doesn't depend on a browser pixel firing, so it survives ad blockers, cross-device journeys, and visitors who close the tab before a script loads. Every confirmed event is then screened against the campaign's rules and basic fraud signals before it's queued for review.
Approved conversions post to the publisher's dashboard immediately, with status visible the whole way — pending, approved, or rejected with a reason. Payouts go out on a fixed schedule, not on request.
S2S postback by default, with pixel and link-based tracking available where a backend integration isn't possible. Click IDs persist across the session so multi-step and multi-device journeys still attribute correctly.
One link that routes each visitor to the best live offer for their GEO and vertical automatically, instead of a publisher having to manually swap links every time a campaign pauses or caps out.
Clicks, conversions, approval status, and earnings in one dashboard, broken down by campaign, GEO, and date range — the same numbers both sides of the network are looking at, not two different exports.
Approve at the conversion level, not the invoice level. Publishers see exactly which conversions were paid, which were rejected, and why — on a schedule that doesn't move.
Ad blockers and lost pixels. A browser pixel only fires if the script loads and the visitor doesn't block it. S2S postback comes from the advertiser's server, so it isn't affected by client-side blocking.
Multi-device journeys. A visitor who clicks on mobile and buys later on desktop still attributes correctly as long as the click ID carries through, which is how Kapvexa's tracking is built by default.
Duplicate and low-quality conversions. Conversions are screened against campaign rules before they're approved, so advertisers aren't paying for the same lead twice or traffic that doesn't match the campaign's terms.
Pick whichever fits how your team already works — they're not mutually exclusive, and most programmes end up using more than one.
Set up campaigns, review conversions, and check payout status without writing any code. Most advertisers and publishers run entirely from here, day to day.
Point your existing checkout, CRM, or lead system at a Kapvexa postback URL on conversion. No SDK, no library to install — just a server-side request with the click ID attached.
Pull campaigns, clicks, conversions, and payout data programmatically, for teams who want Kapvexa numbers inside their own BI tools or finance systems.
Server-to-server postback is the default and the most reliable. Pixel-based and link-based tracking are also supported for campaigns where a backend integration isn't available yet. See our full comparison.
Review time depends on the campaign's own verification rules, but status is visible on the dashboard the moment a conversion comes in — pending, approved, or rejected with a reason, not a black box.
Yes — a lead-then-sale hybrid (a smaller CPL followed by a CPS if the lead converts) is common where the lead and the sale happen weeks apart. See our guide to CPS, CPL, and CPI for the full breakdown.
Yes, alongside the dashboard — campaigns, conversions, and payout data can be pulled programmatically for advertisers and publishers who want to plug Kapvexa into their own systems.
The publisher sees the rejection and the stated reason immediately in their dashboard — no unexplained gaps in earnings. Rejection reasons come from the campaign's own stated rules, set by the advertiser up front.
Yes — moving from pixel to S2S postback mid-campaign is common as programmes mature, and doesn't require pausing the campaign to do it.
Set your model, connect tracking, and watch conversions move from pending to paid.
Talk to Kapvexa