Pixel Integration

Pixel is small code by mtrackit which is embedded on page with certain parameters

Pixel Tracking

A single pixel of mTrackIt needs to be dropped on the conversion page of the advertiser for the purpose of tracking of conversions.

This allows the advertiser to track and report conversions to publishers in real time (mTrackIt will trigger the relevant postbacks to the publishers based on the tracking and attribution process).

The pixel is a simple image based pixel which can be placed on the ThankYou page of the advertiser (in case of a sale transaction for example).

Pixel URL

https://pixel.mtrackit.com/1.gif?revenue_amount={revenue_amount}&cost_amount={cost_amount}&order_id={order_id}&event_datetime={event_datetime}&cust_field1={}& cust_field2={}&cust_field3={}&cust_field4={}&cust_field5={}&event={}&transaction_id={}

Typically the pixel tracking code is embedded into conversion pages using the below HTML code

<img src="MTRACKIT-PIXEL-URL-GOES-HERE" style="position:absolute; visibility:hidden">

Parameters are used to collect additional data associated with the conversion for reconciliation purposes.

URL Parameters

Parameters	Descriptions
revenue_amount	revenue generated due to transaction being attributed (Sale revenue)
cost_amount	Cost incurred for the customer due to the attribution
order_id	Order ID received as part of Pixel Request and will be generated after placing the order
cust_field1	Custom field for adding additional parameters
cust_field2	Custom field for adding additional parameters
cust_field3	Custom field for adding additional parameters
cust_field4	Custom field for adding additional parameters
cust_field5	Custom field for adding additional parameters
event	Event tags can be passed here for identification of subsections for same client / product
transaction_id	Unique ID which refers to same as sent in click redirection query string parameters. (Optional)

Transaction id is necessary parameter if pixel url is being used as postbacks.

Note:

1. All querystring parameters should be url-encoded which makes it easier to send as it is over the internet.

2. Maximum acceptable length for any indivdual parameter is 255 characters.