Pixels and outgoing callbacks
How Axalot sends matched conversion and funnel events to Facebook, HTTP GET endpoints, Telegram Bot callbacks, and stream-level pixel destinations.
What pixels mean in Tracker
In Tracker documentation, a postback is an incoming conversion signal into Axalot. A pixel or outgoing callback is an event Axalot sends out after a click, funnel event, or conversion is matched.
Send mapped events to a Facebook pixel or CAPI destination.
HTTP GET
Call an external URL when selected events occur.
Telegram Bot
Send conversion notifications to Telegram.
Stream selection
Campaign streams decide which pixels apply to accepted traffic.
Console path
Console / Tracker / PostbacksConsole / Tracker / Campaigns / Streams / Pixels
Event model
Axalot outgoing mappings can use commercial conversion states and funnel events.
| Event group | Fields |
|---|---|
| Conversion statuses | accept, redep, hold, decline, trash |
| Landing flow | land_view, land_click |
| PWA flow | pwa_view, pwa_install, pwa_subscribe |
| Telegram flow | tg_join, tg_start |
Delivery types
Requires a selected Facebook pixel and at least one mapped event. Use for optimization and ad platform feedback.
Requires a valid URL. Use for lightweight partner callbacks, internal webhooks, or custom integrations.
Requires a Telegram bot, chat id, and message. Use for team notifications and launch monitoring.
Stream-level selection
Pixels are selected inside campaign streams. This matters because two streams in the same campaign can send different outgoing events.
Stream: US mobile
Pixels: Meta primary pixel
Stream: Fallback
Pixels: noneUse this when fallback traffic should not pollute the main optimization pixel.
Pixel selection is not campaign-wide
Selecting a pixel on one stream does not select it on every stream. Add each pixel to every stream that should send events.
Setup workflow
Create or configure the outgoing destination in Tracker -> Postbacks.
Map only events the destination should receive.
Add the pixel/callback to the campaign streams that should send those events.
Send a test click and trigger the event.
Check postback logs and reports before increasing spend.
Troubleshooting
| Symptom | Check |
|---|---|
| Facebook event missing | Pixel selected, event mapped, stream matched, and incoming postback matched. |
| HTTP GET not called | URL is valid, callback is active, event is mapped. |
| Telegram message missing | Bot, chat id, message, and event mapping are configured. |
| Events sent from wrong stream | Pixel was selected on a broader or fallback stream. |
| Too many low-quality events | Decline/trash/hold events may be mapped unintentionally. |