Any other tracker

AlterCPA TOP works with any tracker that accepts a GET server-to-server (S2S) postback. If yours isn’t listed, follow this three-step recipe.

The recipe

Step 1 — find your tracker’s click id macro

Every S2S tracker has a macro it substitutes for the click id when building a traffic link. Common names: {subid}, {clickid}, {click_id}, {tid}. Look in your tracker’s documentation under “S2S postback”, “conversion tracking”, or “click macros”.

Step 2 — embed it in the deep link

Put that macro where AlterCPA TOP expects {click} in the deep link:

t.me/YourBot?start=CAMPAIGNCODE-{your_tracker_click_macro}

When a subscriber clicks this link via your tracker’s redirect, the tracker replaces the macro with the real click id. AlterCPA TOP stores it and passes it back with every postback for that lead.

Step 3 — configure the five postback templates

In AlterCPA TOP (Profile → Global postbacks, or per-campaign), set five URLs pointing at your tracker’s postback endpoint. Pass our {click} back as the tracker’s click id parameter, and add a status value the tracker understands:

wait:    https://your-tracker.example/postback?clickid={click}&status=lead
hold:    https://your-tracker.example/postback?clickid={click}&status=lead
approve: https://your-tracker.example/postback?clickid={click}&status=sale
cancel:  https://your-tracker.example/postback?clickid={click}&status=rejected
trash:   https://your-tracker.example/postback?clickid={click}&status=rejected

Replace clickid with your tracker’s parameter name and the status values with what your tracker expects.

Other useful macros:

Macro	Use case
`{lead}`	Our internal lead id — a good dedup key if your tracker supports it
`{time}`	UNIX timestamp of the event
`{username}`	Subscriber’s @username (may be empty)
`{subscriber}`	Telegram user id

→ Full macro list: How tracking works

Troubleshooting

Symptom	Check
Conversion not attributed	The click id in the postback doesn’t match — make sure the tracker’s macro is in the deep link and the redirect actually went through the tracker
Postback not fired at all	Is the tracker URL publicly reachable? Private IPs and localhost are blocked. Is the URL `http` or `https`? Other schemes are refused.
`cancel` / `trash` not arriving	Check the campaign’s unsub window — leaves after the window fire no postback
Wrong status values	Consult your tracker’s S2S documentation for accepted status/goal names

Binom API overview