Smart Pixels

A Smart Pixel is how conversion events get fed into the Intelitics platform. Learn it's structure here

A
Written by Andrew Alvarado
Updated over a week ago

"Smart pixels" are used to feed the Intelitics platform conversion event data (Installs, Registrations, Deposits, etc.). Our "smart pixel" allows the Intelitics platform to gather conversion data in as close to real time as possible.

  • For an Operator: this is typically placed inside of the gaming platform on specific conversion events.

  • For a Network: these are typically placed with an operator for a trackable campaign.

Clicks are updated with new conversion details through a “smart pixel”. This is a static URL that is given the click’s unique ID along with conversion details, such as registration or deposit information.

Use this when a click ID already exists and a conversion should be added / updated to that click.

Base URI

https://yourcustomdomain.com/convert/{click_id}

Required Parameters

  • type
    - Type: [“install”, “registration”, “deposit”]
    - The type of conversion being reported. Conversions are linear, but can skip any step in this process if that type of event is not wanted or not available to be tracked

  • click_id
    - Type: uuid
    - Intelitics generated unique ID of the initial impression or click

Optional Parameters

  • test
    - Type: boolean
    - Settings this parameter to “true” will process the call and redirect to the correct tracking link, but without storing the conversion in the database

  • player_id
    - Type: string
    - A custom player ID from your gaming platform for tracking purposes

  • currency ("deposit" type events only)
    - Type: ["eur", "usd", "gbp"]
    - Currency code the deposit was made in

  • amount ("deposit" type events only)
    - Type: float
    - The amount of money made for the deposit

  • time
    - Type: ISO8601 datetime string
    - The time the conversion occurred. By default, the current time will be used. This parameter should only be used in cases where an old event is being reported, possibly from a failed pixel fire

  • transaction_id
    - Type: string
    - A custom id relating to deposit events, so Intelitics can match events from different data streams.

Example URI

https://yourcustomdomain.com/convert/fd3ba970-2330-4576-94ba-e1efc470bd56?type=deposit&currency=usd&amount=40&player_id=1874552&transaction_id=123456789

Example Responses

Success

HTTP Code: 202

Body: <empty>

Error (Invalid Type)

HTTP Code: 422

Body:

Error (Invalid amount)

HTTP Code: 422

Body:

Error (Invalid currency)

HTTP Code: 422

Body:

Implementation Options

There are multiple options for using this URL to track click updates or conversions. All options perform the same function.

iFrame

This is a piece of code that is placed directly on a page after a user converts at various defined events (install, registration, deposit). It fires the request as the page loads.

JavaScript

The conversion URL can be requested directly from JavaScript running on the user’s browser. This is useful if the user’s browser page does not change once they have converted. A script can be added to your offer page’s code to update Intelitics on the conversion. This can be done asynchronously as well, so it does not block the user or affect the load speed of your page.

Server to Server

This URL can also be requested directly from any server. However, since the request is not being sent from the user’s browser, Intelitics will not be able to record metadata information and session specific values from the user (e.g. IP address, geolocation information, referrer URL).

Did this answer your question?