Supported platforms
What it plugs into, and what it does not.
Every name below is a template that exists in the product today. The last section is the things that are not built — listed here rather than discovered after you have moved your campaigns over.
Paste one URL into the ad network.
Each of these has a template with that network’s own tokens already in it — the campaign id, the site id, the creative, the cost macro where the network provides one. You copy a finished URL rather than assembling one and finding out a week later that a placeholder never resolved.
Conversions that arrive with the right names on them.
Every network calls the same three things something different. These have their parameters mapped already, so a postback lands as a conversion with a payout and a status rather than as a row of unnamed fields.
- lemonads
- ShareASale
Not on the list?
Pick the shape its parameters already use. These five cover most platforms, including ones that have never heard of us.
cid / payout / statusThe standard shape
aff_sub / amount / statusTUNE and its descendants
subid / sum / statusCommon in CIS networks
clickid / revenue / eventEvent-named conversions
s1 / price / statusOlder CPA platforms
API sync: cost and conversions, without a macro.
Postbacks are not worth a section — every network on this page takes one, and that is how cost and conversions have always moved. What is new is an authenticated API in both directions: spend read from the platform rather than trusted from a URL, and conversions returned to its optimiser rather than dropped at your side. Not every platform offers one, and the ones that do are here.
Working now
10 platforms · costPaste a key from your own account and spend starts arriving. Nothing to wait for and nobody to ask.
- Any reporting endpoint
Pending
4 platforms · waiting on approvalBuilt, with the Connect button in the app. Each of these has to approve our OAuth application before anyone can press it, and Google wants a developer token at Basic Access on top. That is ours to finish, not something you can hurry along.
Conversions, returned by API
Not builtThe other direction is not here yet on any of them. Conversions go back by postback today, which every network accepts; the nine platforms that want a Conversions API instead — hashed user data, OAuth, retries — do not have one from us, and a CAPI endpoint put in a postback field is refused rather than quietly dropped.
Not built yet
The list nobody else publishes.
If one of these is the thing you need, say so before you switch — what people ask for decides the order they get built in.
Cost sync for Google, Microsoft, Meta and TikTok
The connectors are built and the screens are there. Each platform has to approve our application before anyone can press Connect, and those approvals are in progress — Google Ads also requires a developer token at Basic Access.
A public API
There is no customer-facing REST API yet. Reporting is read in the app or exported; conversions come in by postback. If you need to read data programmatically, tell us what for — it decides what gets built first.
ClickBank order lookup
The integration is written against ClickBank’s published specification but has not been run against a live account. The first customer to connect one will confirm it or give us the correction.
Zapier, Make and webhooks out
Nothing yet. Conversions arrive by postback, and nothing leaves on an event.
Need a network or a platform that is not here? Send us its documentation — that is how most of this page got written.
Point a domain at us and run a click through it.
The free plan takes ten thousand clicks a month and no card. If it does not do what you need, you have lost twenty minutes.