Keitaro is a click tracker: it redirects, split-tests and reports on campaigns, and it does that well. It was never meant to own the lead after it's created — scoring it for fraud, delivering it to a CPA network over API, holding a status, and reconciling the payout. That's the half you're moving to d0pe.
This migration is additive: your tracker keeps running the click while d0pe takes the lead. You can point a single test source at d0pe first, verify the round-trip, then cut over — nothing is deleted in Keitaro and you can roll back at any point. A first flow takes about ten minutes.
On a clean VPS, run the one-line installer and sign in. It sets up the app, database and analytics and asks only for your license key.
For each Keitaro affiliate network/offer, create a Partner (the advertiser) and a Campaign under it carrying the payout and offer params. Campaigns are the routing targets.
Paste the advertiser's endpoint and auth into an integration, then drag your lead fields onto the request template and map the response's lead-id and status back — no code. Paste the partner's API docs into the AI assistant for a draft mapping.
Create a Flow, grab its ingest endpoint + token, and wire your prelander/source to POST leads there instead of the tracker's lead endpoint. Keep Keitaro handling the click if you want.
Enable the antifraud checkers (IP, phone, email, messengers, device) and set the per-flow accept threshold. This is the lead-level fraud filtering a click tracker's bot filter doesn't do.
Add routes that match by geo and priority, attach campaigns as recipients with weights, and set daily caps per recipient with fallback — the equivalent of your tracker rules and caps.
Set your postback rules — notify your traffic source over S2S and/or feed your ad platforms (Facebook CAPI, Google Ads, GA4) — so a deposit event fires the real payout. Send a probe lead to verify the full round-trip, then switch your live source over.
No. d0pe owns the lead, not the click. Most teams keep their tracker for redirects and split-testing and run d0pe alongside it for antifraud, delivery and statuses.
No. It runs in parallel: point one test source at the d0pe flow, verify the probe lead's round-trip, then cut your live source over. Nothing in Keitaro is deleted, so you can roll back.
About ten minutes once d0pe is installed: create a partner + campaign, map the integration, wire the flow endpoint, and send a probe lead.
There's no binary importer, but the visual JSON mapper plus the AI assistant get you there fast — paste the advertiser's API docs and it drafts the field mapping for you to confirm.