Skip to main content

Creating a source

A source describes the platform the traffic comes from: which parameters to take from the ad link and where to return the postback about events. The + Add source button opens a separate creation page (not a pop-up dialog).

How to create a source​

  1. Open Sources and click + Add source. Source creation page

  2. (Optional) Choose a ready-made template in the From template field — it will fill in the name, the postback and the set of parameters.

  3. Fill in the Name — how the source will be called in lists and statistics.

  4. Set up event passing: for a regular platform — the S2S postback field; for Facebook — the event mapping in the Conversions API block (filled in automatically when the facebook template is selected).

  5. In the Parameters table, check which data the source puts into the link (by default — Ad ID, Pixel ID, FB Click ID).

  6. Choose the Status (Active / Paused) and, if you wish, add Notes.

  7. Click Create. To exit without saving — Cancel. «Create» and «Cancel» buttons at the bottom of the form

note

The Create button is inactive until the Name is filled in. If you do not have the right to manage sources, the form opens for viewing only.

Field breakdown​

From template​

A ready-made source preset. Choosing a template fills in the name, the postback and the set of parameters for you — then they can be edited. The field is optional: a source can also be assembled manually.

Name​

The source name in the interface. Specify a clear name, for example Facebook Ads or Push network.

S2S postback​

The link by which Qubix will notify the platform about an event (registration, deposit, etc.). Macros are inserted into the link — Qubix will substitute real values into them when sending. Available macros:

{external_id}, {status}, {revenue}, {payout}, {currency}, {sub_id_N}, {tid}

Example:

https://source.com/postback?subid={external_id}&status={status}&payout={revenue}

More about the macros and how the parameters go back and forth — Parameter passing and postback.

Facebook instead of a postback

If the facebook template is selected, the S2S postback field is replaced by a Conversions API block: events are sent to Facebook automatically, and you set up only the mapping "Qubix event → 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.

Parameters​

The table describes which values the source passes in the ad link. Each row is one parameter with three fields:

  • Name — how the parameter is called in forms and statistics (for example, Ad ID).
  • URL key — under which key the value comes in the link (what stands before =).
  • Placeholder — what the source substitutes into the value: a platform macro (for example, {{ad.id}} for Facebook) or a fixed value.

Available built-in parameters:

  • Ad ID — the ad identifier. Needed to link clicks with ads and see statistics by them.
  • Pixel ID — the Facebook pixel identifier. Used to send events to the Conversions API.
  • FB Click ID — the Facebook click mark (fbclid). Facebook adds it itself; there is no need to configure it, but if it comes in — Qubix will save it.

To add a parameter, select it in the + Add a standard parameter… list below the table. To remove one — click the cross in the row.

Next to the table, Qubix shows the Example URL for an ad block — a ready-made link that can be copied and pasted into the ad's URL field on the platform. In the example you can choose your domain and a Pixel ID from a list.

Tip

Uncheck the Accept parameters from URL box if you do not want Qubix to save parameters from this source's links. By default the box is on.

Status​

Active — the source is in use. Paused — turned off.

Notes​

Free text for you and your team. Shown under the source name in the general list.

What's next​

Parameter passing and postback

Sources: the list and the card

On this page