Parameter passing and postback
A source connects the platform and Qubix in both directions:
- From the link into Qubix — when a visitor clicks an ad, Qubix takes the required parameters from the link (the ad identifier, the pixel, etc.) and binds them to the visit.
- From Qubix to the platform — when an event happens (registration, deposit), Qubix sends a postback to the platform so that it knows the result.
The settings for both directions are set in the source — see Creating a source.
Parameters in the ad link
Which values to take from the link is set by the source's Parameters table. For each parameter you specify:
- URL key — under which key the value comes in the link;
- Placeholder — what the platform will substitute into the value (its own macro or a fixed value).
Example of a link for a Facebook ad:
https://your-domain/?pixel=123456789&ad_id={{ad.id}}
Here {{ad.id}} is a Facebook macro: when showing the ad, the platform replaces it with the real identifier itself. The ready-made link for your source is assembled by Qubix in the Example URL for an ad block on the source form — it can be copied and pasted into the ad's URL field on the platform.
The Ad ID parameter is needed to link clicks with ads and see statistics by them. Without it the source will keep working, but the per-ad breakdown will be unavailable.
About the parameters on the campaign-link side — Campaign link and parameters.
S2S postback: notifying the platform
A postback (server-to-server, S2S) is a request Qubix sends to the platform when an event occurs. The request template is set in the source's S2S postback field. Macros are inserted into the template — Qubix will substitute real values into them before sending:
| Macro | Value |
|---|---|
{external_id} | The visit/lead identifier on the platform's side. |
{status} | The event status (for example, registration, deposit, rejection). |
{revenue} | The revenue for the event. |
{payout} | The payout for the event. |
{currency} | The currency. |
{sub_id_N} | Additional marks (sub_id_1, sub_id_2, etc.). |
{tid} | The transaction identifier. |
Example postback template:
https://source.com/postback?subid={external_id}&status={status}&payout={revenue}
Facebook: Conversions API instead of a postback
For a source on the facebook template, the regular postback is not used. Instead, Qubix sends events directly to the Facebook Conversions API. You set up only the event mapping: which Qubix event corresponds to which Facebook event (for example, deposit → Purchase). The pixel identifier is taken from the click link, and the access token — from the pixel registry.
More — Facebook Conversions API and Pixels.