▪️Pixel tool (Postbacks / Callbacks)

Types of pixels

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

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

• Facebook/Instagram API - Server-Side Conversion Tracking

• TikTok API - Server-Side Conversion Tracking

S2S HTTPS Pixel is calling any specified URL with a set of dynamically appended parameters based on the affiliate request. FB/Instagram API and TikTok API pixels are sending events to the social media platforms using Conversions API.

Pixel triggering events/actions

Each of the pixels can be triggered on the following events/actions (considering the necessary data was reported to TAP). Affiliates can set more than one pixel definition (triggered on same or different events).

• Lead - will be triggered when a new registration is reported to the affiliate platform;

• Qualified Lead - will be triggered when a new registration has passed the deal qualifications (only for CPL deals);

• FTD - will be triggered when a new FTD (First-Time Deposit) is reported to the affiliate platform;

• QFTD - will be triggered when a new FTD passes all qualifications (only for CPA deals)

How to create pixel defintion

1. Go to 'Pixel Definitions' tab in the affiliate profile and click 'Create'

2. Write a Name for the pixel

3. Choose the Deal you want to relate the pixel to. You can choose Global for any deal, or a specific deal among the different deals configured for the affiliate. Pixels will be fired only for players that are assigned to a deal (any deal or a specific deal, according to the pixel definition).

4. Choose the Action on which to trigger the pixel

5. Choose the Type of Pixel and fill in the necessary information.

Server-to-server pixels (S2S)

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_id}} - is part of TAP'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.

Additional Parameters

Available for S2S HTTPS pixels

Pixel URLs can include Default supported parametrs or Custom parameters. TAP will collect any additional parameters the affiliate is sending, so later they can passed back in the pixel.

For Default parameters supported by TAP, explanations can be found in 'List of Default parameters' below or when hovering over the parameter in the Pixel Definition modal. Parameters without any explanations will be those collected by TAP from all clicks ever made on the affiliate's tracing links. From the example below, custom parameter is for {{click_id}}.

List of Default parameters

{{deal_id}} - ID of the deal that is matched to the customer brand, country, source id, campaign id {{deal_group_id}} - ID of the deal group that was set in the original link used by customer {{deal_group_name}} - Name of the deal group {{campaign_id}} - Campaign ID if it was specified in the original link used by customer {{campaign_name}} - Campaign name that corresponds to campaign_id {{brand_id}} - ID of the brand {{brand_name}} - Name of the brand {{link_id}} - ID of the destination link to which customer was redirected {{link_name}} - Link name that corresponds to link_id {{asset_id}} - ID of the media asset if it was specified in the original link used by customer {{asset_name}} - Media asset name that corresponds to asset_id {{asset_type}} - Media asset type that corresponds to asset_id (e.g. email, banner etc.) {{country_code}} - 2 symbol country code of the customer used in registration {{source_id}} - Optional source_id if it was specified in the original link used by customer {{registration_id}} - Unique ID of registration in Affiliation system {{customer_id}} - ID of the customer as it's known in the destination platform {{payout}} - Payout amount for CPA or CPL deals {{payout_currency}} - 3 symbols currency code of the payout amount {{utm_source}} - Additional parameter passed by affiliate {{utm_medium}} - Additional parameter passed by affiliate {{utm_campaign}} - Additional parameter passed by affiliate {{afp}} - Additional parameter passed by affiliate {{afp1}} - Additional parameter passed by affiliate {{afp2}} - Additional parameter passed by affiliate {{afp3}} - Additional parameter passed by affiliate {{afp4}} - Additional parameter passed by affiliate {{afp5}} - Additional parameter passed by affiliate {{afp6}} - Additional parameter passed by affiliate {{afp7}} - Additional parameter passed by affiliate {{afp8}} - Additional parameter passed by affiliate {{afp9}} - Additional parameter passed by affiliate {{deposit}} - Total deposits known to affiliate system at the moment of sending pixel {{registration_date}} - User registration date in unix epoch format {{first_deposit_amount}} - User first deposit amount

If you are an affiliate, go to "Pixels" and click "Create". A creation model will open for you to fill the necessary information.

Facebook/Instagram API

This feature allows the affiliate platform to send conversion events directly to Facebook or Instagram (via the Conversions API). By sharing this data, you help Facebook Ads or/and Instagram Ads systems optimize campaigns more accurately, resulting in better performance and reporting.

As Instagram is a part of the Meta ecosystem, the setup for Facebook Ads Pixel will also apply to Instagram Ads. The same Pixel ID and configuration used for Facebook will track conversions and events on Instagram as well. Affiliate doesn't need a separate integration just for Instagram, as long as: - Affiliate's Instagram campaigns are running under the same Meta Business account (and linked to the same Pixel/Data Source) - Any server-side events sent via the Facebook Conversions API will automatically work for both Facebook and Instagram traffic.

How to set Facebook/Instagram API pixel

1. Follow the steps for creating a pixel and choose pixel type FB/Instagram API

2. Set the following details:

• Facebook Pixel ID: Your unique Pixel (Data Source) ID in Facebook (e.g., 1234567890).

• Facebook Access Token: A valid token granting permission to send conversion events on your behalf. Access token is obtainable via your Facebook Business Manager or Events Manager setting

If you are an affiliate, go to "Pixels" and click "Create". A creation model will open for you to fill the necessary information.

How Facebook/Instagram API pixel works

1. When user clicks on affiliate's Facebook ads, fbclid parameter is automatically appended to the URL of affiliate's tracking link.

2. TAP system captures the fbclid

3. Upon event triggering (e.g. user registration or FTD), the affiliate platform sends the event (including the relevant fbclid) directly to Facebook's Conversion API

4. Facebook matches the conversion to the correct ad click.

TikTok API

The setup process follows the same logic as Facebook/Instagram API Pixel, with the only difference being the specific parameters required for this pixel type.

To configure your TikTok API pixel in TAP, follow the steps for creating the pixel, select the relevant pixel type and set the following details:

• Pixel code : Your unique Pixel code/ID in TikTok (e.g., 1234567890).

• Access token: A valid token granting permission to send conversion events on your behalf. Access token can be generated in TikTok Business Center (Events Manager or Developer Tools)

  

  If you are an affiliate, go to "Pixels" and click "Create". A creation model will open for you to fill the necessary information.