Each party reports different numbers
How it's fixed
- Map one click ID through every platform
- Set postbacks in the right order
- Reconcile a sample of conversions
- Home
- Services
- Postbacks and funnels
- S2S postbacks
Postbacks and funnels
S2S postbacks every party agrees on
Server-to-server postbacks between advertisers, networks, trackers and publishers, mapped and tested so the same conversion shows up for everyone, at the right payout.
Approved RedTrack setup partnerUsually replies within minutes
Common problems
S2S postbacks problems I solve
Broken tracking and loose processes waste budget and lead to bad decisions. These are the issues I see most often, and how each one gets fixed.
Click IDs in the wrong sub ID slot
How it's fixed
- Follow each network's sub ID rules
- Update every tracking link
- Confirm values in reports
Postbacks not firing
How it's fixed
- Check the URL, tokens and goal settings
- Fix whitelisting or HTTPS issues
- Fire live test conversions
Wrong payouts passed
How it's fixed
- Set payout tokens per party
- Check currency and rounding
- Test each payout type
Conversion APIs not connected
How it's fixed
- Send conversions to Meta, TikTok and Google from your tracker
- Pass the right click IDs
- Check events arrive
No record of how it is set up
How it's fixed
- Document every postback and mapping
- Note who owns each step
- Keep it updated as partners change
What's included
My S2S postbacks services
Pick what you need. Every quote is built around your setup and agreed before work starts.
Postback mapping
A clear map of how IDs pass between every party.
Tracker postbacks
RedTrack, Voluum, Binom and others set up.
Network postbacks
Everflow, CAKE, TUNE, Trackier and Impact connected.
Publisher postbacks
Partners get their own IDs and payouts back.
Conversion APIs
Meta, TikTok and Google Ads fed from your tracker.
Pay per call
Call platforms like Ringba connected to your tracker.
Live testing
Real test conversions checked on every side.
Documentation
A short note anyone on your team can follow.
Integrations
RedTrack
Voluum
Binom
Everflow
CAKE
TUNE
Trackier
Ringba
Under the hood
Every party, one click ID
The same click ID travels from the publisher to your tracker and on to the network, so each side can match the same conversion at the right payout.
Example: a three-party postback chain
# 1. Network tells your tracker about the sale
https://track.yourbrand.com/postback?clickid={sub_id}&sum={payout}
# 2. Tracker tells the publisher, with their own click ID
https://publisher.example/pb?cid={pub_click_id}&amount={pub_payout}How it works
How my S2S postbacks service works
Six clear steps, from first look to a setup you can scale on.
- Step 01Understand your goalsA quick call or brief about what you need and where things stand.
- Step 02Review what existsI look at your current setup, accounts or pipeline before changing anything.
- Step 03Agree the planScope, timeline and price agreed in writing before work starts.
- Step 04Do the workBuilt or managed inside your own tools, with clear names and notes.
- Step 05Test and checkEverything tested with real data before you rely on it.
- Step 06Report and improveClear updates, or a handover guide for one-off projects.
Ready to improve your S2S postbacks results?
Tell me what you're working on and I'll reply with a plan and a quote. I usually reply within minutes.
"Matthew is truly an expert in Voluum and Facebook. He set up all of my tracking and integrations over the weekend and worked around the clock."
FAQ
S2S postbacks questions
What is an S2S postback?
A server-to-server message that tells one platform about a conversion recorded on another, using a shared click ID, without relying on browser cookies.
Can you connect platforms I do not control?
Yes. I work from each partner's instructions and test with them before launch.
Do you handle pay per call?
Yes. I connect call platforms like Ringba so calls and sales report back to your tracker.
How long does it take?
Most integrations take one to three days, including live tests.
Related articles