Pixel Information

Updated 2 months ago by Aaron J Mitchell


The purpose of a pixel is to track events such as conversions. Pixels usually come in the form of an iFrame, image, or postback, and Maximus supports each of those three types.


How does this pixel work with Maximus?

After a user sees and clicks an ad creative on a top-tier publisher, the user is redirected to the native network. The native network redirects to Maximus. Maximus then redirects the user to the campaign's weighted link. The page that loads is the offer page where the user can order a product. The confirmation page after ordering contains a pixel that tells Maximus that a conversion has happened.


What happens behind the scenes?

When a user reaches Maximus and clicks an ad, an ID is assigned to the click. This click id is funneled along to the weighted link, either in the tracking token {clickid} or automatically as s5=click_id&max_cid=clickid.

The click id is a critical component to the reliability of the pixel. If the click id can be passed, there is a 100% chance of the sales tracking back to the click. If the click id cannot be passed back, Maximus tries to identify the user via a cookie. This is less reliable as it is possible for the user to clear their cookie settings, use different devices, or browse privately.

As mentioned previously, there are three pixel types that Maximus supports: iFrame, image, and postback. iFrame and image pixels both load an invisible 1x1 pixel on the confirmation page. Maximus offers both global and campaign level pixels. The campaign level pixel is required if the click id cannot be passed to the pixel.

Postback pixels are the most reliable if all systems can pass the click id throughout the entire sales funnel. Postback pixels do not require anything to be loaded on the user’s browser and are supported by most third party tracking systems.

To access the pixel, this can be done by clicking Pixel Set Up when viewing the campaign details for a campaign.

CPA campaigns and CPC campaigns vary but function similarly. Click here to read our CPA vs CPC documentation.

From the Settings page you can add conversions that you see in your external system but Maximus has not tracked. If you see more than a few conversions not tracking in Maximus, please reach out to our LiveChat support team for assistance. Click here to learn more about adding conversions.


iFrame pixel:

When placing a pixel on your confirmation (Thank You) page, #s5# should be equal to your tracking system’s token for the Maximus Click ID and #price# should be a number equal to the value of the conversion.
<iframe src="https://rpptrk.com/p/?cid=#s5#&payout=#price#" height="1" width="1"></iframe>

You can use either a static payout value (if you know the conversion will be a set amount) or if you use a third party system like an advertiser network and have a variable available you can place that value here also.

We can update previous conversions if the payout changes and you want to retroactively change the conversion payout.

An example iframe pixel once values are passed through in this case looks like:

<iframe src="https://rpptrk.com/p/?cid=b4a922a6-9fc1-4ecb-ba90-f2fde1490aa0&payout=50" height="1" width="1"></iframe>

Postbacks can be sent directly to the same URL:

https://rpptrk.com/p/?cid=#s5#&payout=#price#


Global iFrame pixel:

If you do not want to place a pixel for each campaign, or you are unable to pass click id through the funnel, you can use the global iframe pixel without clickid:

<iframe src="https://rpptrk.com/p/?payout=#price#" height="1" width="1"></iframe>

An example iframe pixel in this case looks like:

<iframe src="https://rpptrk.com/p/?payout=40" height="1" width="1"></iframe>

By not including the click id (cid), Maximus will determine which click belongs to the conversion by using the user's last click. Maximus must have access to the web user's browser in order to find the click, so postback or server-to-server pixels will not work.

If you use the global iframe pixel without click ID, there is a potential that the conversion may not record for the right campaign.

Maximus will look at the last click the user made prior to the pixel firing to determine the click. It is possible that a small percentage of users will click Campaign A and then Campaign B, but convert on Campaign A’s sales funnel. In this case, Maximus will see this as a conversion to Campaign B. To eliminate this possibility, you can still pass a link id or, even better, pass a click id for the most reliable conversion tracking.


Campaign Level iFrame pixel:

If your system requires you to place a campaign specific pixel, you can use either of the pixels below. We recommend passing the click ID in all cases as it is most reliable.

Most reliable:

<iframe src="https://rpptrk.com/p/?cid=MAXIMUS_CLICK_ID_GOES_HERE&lid=198028f0-5167-4f81-be17-79007d943f6d&payout=#price#" height="1" width="1"> </iframe>

Less reliable:

<iframe src="https://rpptrk.com/p/?lid=198028f0-5167-4f81-be17-79007d943f6d&payout=#price#" height="1" width="1"> </iframe>





Tracking System Set Up


Everflow

To set up tracking inside Everflow, navigate to your offer by using the left side menu and select Manage. On the offer page, navigate to the Postbacks menu option.


In the first section, Conversion, click on the Add Postback button.

Fill out the relevant information for Affiliate, and everything else should populate for the offer correctly. For Delivery Method select either HTML or Postback. We recommend postback but you can use whichever method you prefer.

The Postback should look like:

https://rpptrk.com/p/?cid={sub5}&payout={payout_amount}

If you want to use Pixel HTML, it should look like:

<iframe src="https://rpptrk.com/p/?cid={sub5}&payout={payout_amount}" height="1" width="1"></iframe>


Append to your Weighted Link(s)

Depending on which subX variable you use, you can change the above pixel/postback. Using sub5 as an example, append the following to your weighted link in Maximus:

sub5={clickid}




Cake

When using Cake as your tracking system, Maximus automatically sends the required click id to Cake via the s5 token. On the campaign card, the postback pixel as well as the iFrame pixel can be placed for extra reliability.

The Pixel HTML should be:

<iframe src="https://rpptrk.com/p/?cid=#s5#&payout=#price#" height="1" width="1"></iframe>

The Postback URL should be:

https://rpptrk.com/p/?cid=#s5#&payout=#price#

Append to your Weighted Link(s)

You do not need to append anything to your weighted links as Maximus automatically adds s5={clickid} to your links.




Voluum

It is recommended to set up a new traffic source when using Voluum. This new traffic source will map the Maximus link to your Voluum instance. Offers are then built to utilize the {varX} tracking macro to pass to the campaign’s actual landing page. Voluum will then be able to fire a postback pixel based on the {varX} macro as well.

There are some cases where the variables will not work and we recommend trying the externalid value if possible.

In this situation, the Maximus traffic source postback should look like:

https://rpptrk.com/p/?cid={externalid}&payout={payout}

Add the parameter as max_cid and the placeholder as {max_cid} for the external id.

Below is a visual of the traffic source set up in Voluum. The traffic source postback URL should be the postback url from your Maximus campaigns.

This will only work if your Voluum pixel is already firing.


{var1} in this example will based on which {varX} is used when setting up the advanced parameters.


The max_cid is passed to all Maximus links. When setting up the traffic source, use max_cid in an available “var” field. In this example “var1” is used and the toggle for Track is ‘enabled’. The parameter {var1} should coordinate with the postback url {var1}. If you choose {var7} then the postback URL should also be {var7}.

Also, if you are passing the click id through Voluum to another system to fire conversions, your offer setup should also pass the click id as {varX}.

Append to your Weighted Link(s)

Depending on which varX variable you use (or externalid), you can change the above pixel/postback. Using externalid as an example, append the following to your weighted link in Maximus:

externalid={clickid}

If you use varX (var1 for example) add this to your weighted link:

var1={clickid}



HitPath

In HitPath, access the Pixels card from campaign actions. The format should be set to Postback and the postback URL is:

https://rpptrk.com/?/cid=xxc1xx&payout=xxpayoutxx

Append to your Weighted Link(s)

c1={clickid}



HasOffers

Setting up the postback pixel is done from the campaign screen. The code type should be set to Postback URL and the code is

https://rpptrk.com/p/?cid={aff_sub5}&payout={payout}

Append to your Weighted Link(s)

aff_sub5={clickid}




Custom Website

Maximus will send a click id along in any URL parameter required. This can be set when adding the weighted link. The pixels can be placed directly on the confirmation/thank you pages and this pixel can be accessed when clicking ‘Pixel Set up’ on the campaign details page.

There are a number of simple ways to accept/ pass click ids to increase reliability. It is also reasonable to use the cookie functionality of Maximus to ease the setup process.




Google Tag Manager

Using Google Tag Manager for pixel set up is currently not recommended, but it is possible to use with some success.

In order to avoid the pixel being flagged as malware, the tag type will need to be Custom Image. The image URL that will be used is:

https://rpptrk.com/p/?payout=#price#&i=1

Replace #price# in the image url with the numerical value.


Triggers can be setup as normal for GTM. Triggers can be setup for Form Submission or specific to a URL (like a Thank You/confirmation page).




Troubleshooting

Nearly all pixel problems are caused by a missed step in the process. Please be sure to verify all of the setup processes have been followed.

▸ Voluum: Verify the traffic source and offers share the same {varX} token

▸ Cake: Verify click id is being looked for in s5

▸ GTM: Verify an image pixel is used

▸ HitPath: Verify that the click id is being looked for in the C2 values and that the weighted link is passing on the click id.

▸ HasOffers: Verify that click id is being looked for in aff_sub5 in both postback pixel and the weighted link setup.

There are also tools such as http://redirectdirective.com or http://wheregoes.com that can help you trace redirect problems.


How did we do?