Conversions go back to the networkthe click came from.
Push, pop, native and in-app networks optimize campaigns on postbacks. Adset.Pro fires an S2S postback with the network's click id the moment a registration, deposit or PWA install happens — from a ready template for 20+ networks or from any URL of your own with macros.
Why connect S2S postback
Ready network templates
For PropellerAds, ExoClick, Adsterra, TrafficStars, Clickadu, HilltopAds, Galaksion, Evadav and other networks the source template fills in the link parameters and the postback URL — you just add your account and goal IDs.
Any network via your own URL
Network not listed? Paste its postback URL with macros: network click id, event, payout, country, sub1–sub10, campaign and offer. Works for a CRM or your own analytics too.
The network sees what you decide
Each campaign sets the share of conversions (0–100%) and the payout share (0–300%) sent to the source postback. Tracker stats and reports stay unchanged.
Fires across all campaigns
The postback is attached to the source and fires from all its campaigns — no need to add a pixel to every stream set. The final URL and the network's response for every send are in the logs.
What Adset.Pro sends to the traffic source
| Macro | What it's replaced with |
|---|---|
| {event.ext_click_id} | The network's click ID stored on the click: subid, visitor_id, etc. |
| {postback.event} | Event value from the mapping — the goal or status the network expects |
| {event.event_revenue} · {event.event_currency} | Conversion payout and currency; for the source postback — with the payout share applied |
| {event.event_type} | Internal event type: cpa_accept, cpa_hold, pwa_install… |
| {event.event_click_id} | Adset.Pro internal click id |
| {event.user_country} · {event.ext_sub1…10} | User country and the click's sub-parameters |
| {campaign.name} · {offer.name} | Campaign and offer names |
| {user.*} | Buyer parameters from their profile |
Connect in 4 steps
Create a source from a template
Sources → + Source → pick the network's template. The tracking link parameters and the postback URL are filled in for you.
Add the network details
Replace the placeholders in the postback URL with your account and goal IDs from the network and set a value for each event.
Pick the source in a campaign
The postback fires for every campaign with this source. Optionally set the conversion and payout share.
Check the logs
Make a test conversion and open the pixel logs: you'll see the final URL, the network's response and the send status.
Common questions
Create a source without a template: map the network's click id parameter to ext_click_id and paste its postback URL with the {event.ext_click_id} macro. Any system that accepts a GET request works: an ad network, a CRM or your own analytics.
The conversion and payout shares let you control what the network's algorithm sees — for example, not handing it your full install volume or scaling the payout for optimization. Skipped postbacks are marked Ignored in the logs, and tracker stats stay unchanged.
Deposit, redeposit, registration, declined and trash leads, PWA or iOS app install, push subscription, plus bot start and Telegram channel join. Each event gets its own value — whatever the network expects.
A source postback is attached to the source itself, fires in all of its campaigns, and the conversion and payout shares apply to it. A stream-set pixel works only in a specific campaign — that's how Meta, TikTok or Google are usually connected.
Connect S2S postback
on the free Starter plan
Included in every plan · Live support · No card required