The path of a visitor and a conversion
Advertising learns from conversions: the more precisely an ad platform hears about registrations and deposits, the better it finds buyers. This article shows the whole path — from a click on an ad to the conversion being sent on — and where to check each step. Every screen has its own article, linked below.
What it all rests on
Three things tie a conversion to the advertising.
- The visitor. The Qubix code keeps a visitor identifier in the browser — every event of this person carries it.
- The click. A visit from an ad carries marks from the page address, above all the ad number (
ad_id). - The tracker campaign. A visit belongs to the campaign whose entry point — domain and path — covers the page address. When several campaigns share one entry point, the click picks one — see One landing, several sources.
A conversion finds its visitor, and through the visitor — the click, campaign, ad and the campaign's traffic source. A conversion without a visitor identifier is tied to nothing.
How Qubix learns about visits
| Site hosted in Qubix | Site hosted elsewhere | |
|---|---|---|
| Tracking code | Qubix inserts it itself when it serves the page | you add it from the Connect the site block of the website card — Script from the Qubix domain or Through your nginx |
| Switch | Rastrear eventos is on from the start (except a site of the Whitepage type) | Rastrear eventos |
| More | A hosted site counts itself | Connecting a website hosted elsewhere |
Visits are counted with no calls from you; the tracking code reports them from the browser. On a site hosted in Qubix the server decides which page opens a visit: a page opened through the entry point of a campaign opens one, further pages of the same site continue it, and an opening by the site's own address outside a campaign is not counted as a visit. On a site hosted elsewhere the code itself counts a visit when a page is opened not from another page of the same site; further pages continue it. Clicks and forms are counted on the pages of a visit. The numbers are on the Statistics tab of the website card.
Steps of your own — "passed the quiz", "scrolled down to the form" — the page marks with a call such as
sdk.sendEvent('quiz_step'). The step is tied to the visitor and the click, but the standard reports do not show it:
the AI assistant builds its numbers when asked in words — see Your landing's statistics.
How Qubix learns about a conversion
Qubix accepts a registration, a deposit and a rejection in four ways and handles them alike: it finds the visitor, drops repeats, checks the deposit threshold and sends the conversion on.
| Where the conversion happens | Who tells Qubix | What to do |
|---|---|---|
| at the affiliate network | the network — with a postback | copy Postback URL from the network card into the postback settings of the network's panel — see Connecting a network |
| on your site, which has its own server | the site server — with a request to the postback address | the address is in the card of a domain with the Postback role, block URL del postback; the server gets the visitor identifier from the page — see If your website has its own backend |
| on your site, with no server of its own | the page — with a code call | sdk.sendEvent('reg') or sdk.sendEvent('dep', …) at the place in the site code where the registration or payment went through — see Report a registration or a deposit |
| on a site hosted in Qubix, with a server handler | the handler — with a call | Qubix.conversion('reg') — see Site backend |
The postback address with the code — in the domain card and in the network card alike — is shown only to those who see all domains.
An app install is reported by the PWA storefront itself or by the network with a postback.
The network learns the visitor identifier from the offer link and returns it in the postback.
- When Qubix builds the offer link itself — on a page it serves and on a jump by the campaign link — it appends the
Parámetros de la oferta field of the network card, for example
sub1={click_id}. A button on a landing hosted in Qubix gets such a link from the Qubix code — see A landing button that leads to the offer. - On a site hosted elsewhere the Parámetros de la oferta are not appended: the button builds the offer link
itself and puts the visitor identifier,
sdk.getPiuid(), into the network's parameter. Read the identifier at the moment of the click, not when the page loads: on a site connected with the script from a Qubix domain it appears once Qubix has answered the page's first event, and stays empty while both Rastrear eventos and Grabar sesiones are off for the sites of that domain.
What Qubix understands on its own:
reg— a registration,dep— a deposit,installed— an app install,trash— a rejection. A network's status words (lead,sale,rejectedand others) Qubix assigns to a registration, a deposit or a rejection by itself.- A deposit not above the threshold (2 USD by default) is recorded, but it goes neither into reports nor out.
- Repeats are not counted:
- the same conversion of the same visitor with the same deal number arriving again within four days;
- without a deal number — the same status word of the same visitor with the same amount within 60 minutes; the window is set in the protection settings and starts anew after the server restarts;
- a second registration of the same visitor if the first one had a deal number.
- An event of your own — not a registration, deposit, install or rejection:
- the page records it as a step under its name (see above);
- it goes to Facebook only if its name is in the source's event map; in the source form your own name cannot be added to the Facebook map — only through the AI assistant or the API;
- from a network, an event of your own is recorded under its name only at the postback address with the code and only if the event map of the campaign's source names it; any other unknown status at that address is not counted;
- a network's status word becomes an event of your own in lowercase: Latin letters, digits and underscores, starting with a letter, at most 64 characters; the name in the map is written the same way, in lowercase, and the names of Qubix's own events cannot become events of your own; the standard reports do not show events of your own.
- The postback domain takes requests at other paths too — this is how you move from other trackers. Such a request is accepted only if one of its values is the identifier of a visitor Qubix already knows, and an unknown status there, even one the map names, counts as a deposit if the request carries an amount, otherwise as a registration.
Where the conversion goes next
Where to — is decided by the traffic source of the campaign the visitor's click belongs to.
- Facebook (a source on the
facebooktemplate) — through the Conversions API, by this source's map "Qubix event → Facebook event". A pixel is needed: from the ad link or from the ad itself. More — FB CAPI. - A source with a postback — to the address in the Postback S2S field of the source card, and only for the statuses ticked in Send postback for statuses. Installs and events of your own are not sent by postback. More — Parameter passing and postback.
A conversion with a pixel or a Facebook ad whose click belongs to no tracker campaign with a source does not go to Facebook. Their number for the period is the Not sent to Facebook: N label in the Facebook: no tracker campaign row of Fuentes.
Where to check each step
| Step | Where to look |
|---|---|
| the code on the site works, visits come in | website card → Statistics |
| ad visits land in the campaign | tracker campaign card → Clics |
| the conversion arrived | campaign card → Registros and Depósitos; Audience → the visitor card with the whole path |
| the network postback reached Qubix | Audience → Postbacks |
| the conversion went to Facebook | the Facebook window → the Reconcile tab — the delivery strip above the table; Fuentes — the Not sent to Facebook: N label in the Facebook: no tracker campaign row |
The Clics, Registros and Depósitos tabs of the campaign card show visits with an ad number in the address and conversions of such visits. A test visit opened by hand without an ad number is found in Audience and on the Statistics tab of the website card. An administrator sees it; with limited access you see visits and events only of the ads of your campaigns.