Skip to main content

Parameter passing and postback

A source describes how a click and its data move between the platform, Qubix and the offer.

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 substitutes 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 — copy it and paste it into the ad's URL field on the platform.

You can rename a URL key

If your source already sends a value under a different name — for example pxl instead of pixel — put that name in the URL key column. Qubix reads the value under your name and stores it as the built-in parameter, so links you already use on the platform keep working. Your original link is preserved as it came in.

Ad ID

The Ad ID parameter is needed to link clicks with ads and see statistics by them. Without it the source keeps working, but the per-ad breakdown is unavailable.

About the parameters on the campaign-link side — Campaign link and parameters.

How the source is identified​

Qubix reads the source from each click, so several platforms can run on the same domain and still be told apart:

  • a click with fbclid → Facebook;
  • a click with gclid → Google;
  • a click with ttclid → TikTok;
  • otherwise — the value of the source parameter from the link;
  • if none of these is present, the source stays undefined.

Facebook, Google and TikTok add their click id to the link themselves. For any other platform, pass a source parameter in the ad link (for example ?source=propellerads) — add the Source parameter to the source and put its key in the link.

Returning events to the platform​

  • Facebook — Qubix sends conversions to the Facebook Conversions API automatically. You set up only the event mapping (which Qubix event corresponds to which Facebook event, for example deposit → Purchase). The pixel is taken from the click link, the token — from the pixel registry. More — Facebook Conversions API and Pixels.
  • Other platforms — the S2S postback field on the source form is where the notification link will live, with macros such as {external_id} and {status}.
Outbound postbacks to non-Facebook platforms

Sending server-to-server postbacks back to non-Facebook sources is not available yet — it is planned. Today, returning events to the platform works through the Facebook Conversions API.

Where conversions come from​

Registrations and deposits are reported to Qubix by the offer's affiliate network through its own postback. Setting that up is described on the network's side — see Connecting a network.

What's next​

Creating a source

Connecting a network

the postback on the partner network's side.

On this page