Parameter names mapped, not guessed
Keitaro accepts a closed list — subid, status, tid, payout, sub_id_1..30 — and discards anything else without a word. Every macro is mapped to a name from that list.
Nine postbacks without nine trips through the form
The extension opens from the toolbar icon, asks which tracker you use, and creates the postbacks in your partner dashboard — with the parameter names that tracker expects. It reads the parameter list out of the dashboard itself, so a macro added there is picked up on its own.
- Keitaro, Partner Postback Bot, or any other receiver
- Parameter names mapped to the ones your tracker accepts
- Every URL shown in full before anything is created
- No server of ours: nothing leaves the dashboard
Free. Chrome on a computer, signed in to the account the dashboard is open on.
Global · Keitaro
- Registration
status=registration - First deposit
status=deposit - Commission
status=sale
and six more events
First deposit
https://track.example.com/9f3…/postback?subid={click_id}&status=deposit&payout={sumdep}&sub_id_7=ftdCreate 9 postbacks
Nothing is written until this screen is confirmed, and every URL is shown on it in full.
9events created in a single pass
3answers to "which tracker"
0servers of ours between you and the dashboard
The wizard
Click the icon, answer four questions, press Create
The extension works from any tab and opens the dashboard itself if it is not open already. State survives the trip, so moving to another tab does not start the flow over.
-
01
Pick your tracker
Keitaro, Partner Postback Bot, or any other receiver by its address. That one answer decides every parameter name that follows.
-
02
Let Keitaro fill itself in
Click the icon on your tracker's own tab and the domain and the postback key are read there. Both can be typed by hand if the tracker and the dashboard live in different browsers.
-
03
Choose the scope and the events
Global, or one campaign taken from the dashboard's own list. Then the events: four are ticked by default and all nine are one tap away.
-
04
Read every URL, then create
The review screen shows each URL in full. Nothing is written until you confirm it, and what gets written is the request the dashboard's own form sends on Save.
What it takes care of
The parts that go wrong by hand
Nine passes through one screen is merely tedious. What makes it expensive is that a parameter name the tracker does not recognise is dropped in silence.
Repeating events get a transaction id
Re-deposits, commission and withdrawals carry a tid built from {date_time}. Without one, a second conversion on the same click overwrites the first.
The parameter list comes from the dashboard
Each event's parameters are requested from the dashboard rather than carried inside the extension, so a macro added there is picked up on its own — visitor_id and country_ip arrived exactly that way.
Every URL in full, first
The review screen is the only screen that writes. What it shows is what will be created.
Or take the whole pack from the bot
The Partner Postback Bot's card of URLs ends on ⚡ Set it up automatically, which opens the dashboard with the events, the names and the scope already answered.
One step stays on your side
Append &click_id={subid} to every offer URL that points at the advertiser. Without it the postbacks arrive with an empty click id and the tracker has no click to attach them to.
Keitaro
Where each macro ends up
The preset in full. For any other tracker the names are passed through unchanged, with a note on what to check on the tracker side.
https://track.example.com/9f3…/postback?subid={click_id}&status=deposit&payout={sumdep}&sub_id_7=ftd
- {click_id} → subid
- The click. It is what Keitaro matches the conversion on.
- {sumdep}, {wdr_sum}, {commission} → payout
- Sums. One slot, because only one of them travels with any given event.
- {status} → sub_id_6
- Our own withdrawal status, moved out of the way: Keitaro's status carries the conversion type.
- The event label → sub_id_7
- All nine events are coded with Keitaro's system statuses and several share one, so the label is what tells them apart.
- {cid}, {ac}, {site_id}, {trader_id} → sub_id_8..20
- Everything with no slot of its own, inside Keitaro's documented thirty.
Every macro travels in a parameter row, never in the URL field: the dashboard cuts the URL's query at the first macro and appends the parameters composed from the enabled rows.
Questions
Does anything change on the platform side?
No. The extension sends exactly the request the dashboard's own form sends on Save: from your browser, with your session and your CSRF token.
Does my postback key go anywhere?
No. It is read on your own tracker tab, when you click the icon there, and it never leaves the browser. The wizard shows only its first three characters.
My tracker is not Keitaro.
Then pick "any other tracker" and give the receiver address. The parameter names are passed through unchanged, and the last screen names the one thing worth checking on the tracker side.
Can I use it on a phone?
No: an extension installs into Chrome on a computer. The half of this that works from a phone is the bot.
Why does the install button not point straight at the store?
Because the Academy is read on phones as often as in Chrome, and the store answers a phone with screenshots of something that reader cannot install. The link asks the browser first.
I have no tracker at all.
Then your tool is the Partner Postback Bot: it receives the postbacks itself.
Auto-Postback
Install it and let the form fill itself in
Free, and useful from the moment a partner dashboard is open.
Install from the Chrome Web Store