Skip to main content
All CollectionsPartner Guidance
How a Partner can set their Pixels
How a Partner can set their Pixels

As a Partner in Intelitics, learn how to place your pixels in the platform

A
Written by Andrew Alvarado
Updated over a year ago

For reporting insights and dynamic postback options, as a partner you are able to pass up to 5 dynamic subid parameters in your tracking link: s1, s2, s3, s4, s5

Prior to running a campaign, as a partner you can place multiple server-to-server “pixels” within the platform on the following potential conversion events:

  • Install - Called once on every install in the system event for a unique clickID

  • Registration - Called once on every registration event in the system for a unique clickID

  • Deposit - Called on every deposit event in the system for a unique clickID

  • Qualified Deposit - Called once when a clickID's deposit event is "Qualified". This is in relation to the agreement set on the offer level. If a qualification is set, the event will only trigger once the condition is met. If the agreement does not have a qualification in place, every First Time Depositor (FTD) will be counted as "Qualified"

These partner pixels are fired immediately when the Intelitics system processes the appropriate transaction. We sometimes call a partner’s pixel a “piggyback pixel” or webhook, as it relies on the Intelitics smart pixel first.

If a dynamic variable needs to be returned to the partner in order for a pixel to function properly, you may reference these using the aforementioned subID parameters.

The URLs saved here will be called when the conversion event occurs, utilizing the optional SubIDs stored in the click data.

For knowing which subIDs to utilize, please see Recommended Tracking Link SubID Structure

On the offers page, view the “pixels” tab and click “+ pixel”

  1. Select the conversion event, this tells the platform when to fire the partners pixel

  2. Enter your pixel URL, pass the correct variables used the specified placeholders. Intelitics uses "%" character in their token values. Please use this character when placing the token value as shown in the example above.

Did this answer your question?