▪️Pixel tool (Postbacks / Callbacks)

Smartico offers 5 different types of Pixels (also called Postbacks or Callbacks):

• S2S HTTPS - Server to Server pixel call with GET method

• Image Pixel - Client) Image loaded in the browser of the user

• iFrame - iFrame loaded in the browser of the user

• Client JS Block - Custom JavaScript code executed in the browser of the user

• Facebook pixel - Facebook calls for retargeting of AD campaigns

Client Postback (Image, Frame, JS, Facebook) are used by placing HTML code within a browser page, it requires deeper integration from the client side and proper coordination with TAP tech support. Pay attention that TAP might not be aware of financial results in real time, those the effect of client side integration might be limited. We will try to deliver the Postback to the browser next time player logs-in to the platform, this's also the reason why you should have our script embedded on all internal pages (or main page only like lobby), so we can deliver the Postback once we know about some relevant fact.

In contrast, S2S Pixel is calling any specified URL with a set of dynamically appended parameters based on the affiliate request.

Each of our pixels can be triggered on the following events (considering Smartico got the data to send the pixel)

• Lead Registration

• Lead Qualified (usually for CPL deals)

• First-Time Deposit (FTD)

• Qualified First Time Deposit (QFTD)

So you can choose any event to trigger pixel sending.

Server-to-server pixels

Server-to-server pixels are defined as URLs that link to the server location with a set of dynamically appended parameters based on the affiliate request.

A typical server-side pixel might look similar to the following:

https://pixelserver.com?click_id={{afp}}&lead_id={{registration_id}}

Where:

• {{registration_is}} - is part of Smartico's internal parameters supported out of the box.

• {{afp}} - is an example of a dynamic custom parameter used by the affiliate to fit dynamic data like click_id in a PPC campaign etc. The affiliate usually wants the such parameter to be fired back to them under “click_id”.

Smartico will collect any additional parameters the affiliate is sending, later those parameters can be used with postback pixels. (see example above “click_id”)

All those parameters will be visible in the pixel URL build tools, so you can safely choose any from the dropdown list, they will appear after Smartico standardly supported dynamic parameters.

Parameters with comments are part of Smartico default supported values. Parameters without any comments will be those collected by Smartico from all clicks this affiliate ever made.

How to create pixel defintion

1. Pick a Name for the pixel Choose the Deal you want to relate the pixel to.

2. You can choose Global for any deal, or a specific deal among the different deals configured for the affiliate.

3. Choose the Action on which to trigger the pixel

• Lead - will be triggered/fired when a new registration comes and is matching the deal for which the pixel is configured to.

• Qualified Lead - triggered when a new registration that passed the qualifications comes (for CPL deals only)

• FTD - triggered when a new FTD matching the deal happens.

• Qualified FTD - triggered when a new FTD passes all qualifications (for CPA) and matches the deal.

4. Create the Pixel URL (for S2S, iFrame, and Image pixels only)

You can concatenate many attributes to your link by adding or removing them and using placeholders from the Smartico platform, like campaign name, deal name, affiliate parameters, device type, country, etc.

Placing JavaScript code on your website

This steps are needed only in case you are planning to use Client Pixels.

On every page which authorized user can access you need to place the following JavaScript code

const AFF_LIB_LOCATION = 'https://libs.smartico.ai/aff-client-pixel.js';

(function(d, r, b, h, s){h=d.getElementsByTagName('head')[0];s =
d.createElement('script'); s.onload=b;s.src=r;h.appendChild(s);}) (document, 
AFF_LIB_LOCATION, function() {});

_sm_aff_client_pixel.init({
   server: 'wss://api.yourdomain.som/websocket',
   // place here ID of the brand as it's registration in the Smartico Affiliation system
   brandId: 12345,
   // place here ID of the end-user the way it's reported in the registrations/sales files
   playerId: 'id-of-the-player'
});

How the Client Pixel logic works

Let's assume you have setup an Image pixel with the URL 'https://pixelserver.com?click_id={{afp}}&lead_id={{registration_id}}' that should be triggered on FTD.

1. The visitor is clicking on the tracking link and going through the Affiliation system to your registration page

2. He has completed the registration

3. He did a deposit

4. Registration and Deposit is reported from your system to the Affiliation system (usually using CSV files called Registrations and Sales)

5. The affiliation system is processing registration and deposit.

6. Because it's FTD, the Affiliation system is registering a need to send a Pixel and keeping it in the queue.

7. If the end-use is still online on your website, where JavaScript mentioned above is placed, then the Affiliation system will trigger the loading of the "Image pixel" with the URL like https://pixelserver.com?click_id=123456&lead_id=7890

8. If the end-user is not online anymore, the pixel will stay in the queue and will be triggered next time when user will come to your side and login