Forensiq has a few input criterias which are mandatory, and every pixel should include all of them. Following are the mandatory input criterias:
1) ‘Org’ – The pixel requires an Org Id, which is unique for each Forensiq account. The Org Id is a 20-character random string provided by your Account Representative at Forensiq.
2) ‘fmt’ – The “fmt” (short for Format) parameter should be hard coded as either “banner” or “video” depending on the ad format.
3) ‘rt’ – The “rt” (short for Request Type) parameter will have one of the following values:
a) Event – Display ad impression
Location – Directly inside of the iframe of the ad
JS Request Type – display (&rt=display)
Image Request Type – displayImg (&rt=displayImg)
b) Event – Conversation or Sale
Location – Confirmation Page
JS Request Type – action (&rt=action)
Image Request Type – actionImg (&rt=actionImg)
c) Event – Landing page visit or click event
Location – Landing page or redirect page
JS Request Type – click (&rt=click)
Image Request Type – clickImg (&rt=clickImg)
4) ‘p’ – This parameter indicates the ID of the Traffic Channel you are scanning. When implementing into the pixel, make sure it looks like this:
5) ‘&sl=1’ – This indicates to Forensiq to score this pixel, and to appear on their platform. This is a static macro, and should appear in every pixel.
6) ‘dmn’ – this is the domain/bundleid, and should receive the value by adding
Example for JS desktop pixel:
Notice the ‘fmt’ is set to “video”, to indicate a video ad, and ‘rt’ is set to “display”, to indicate a display ad impression request type.
Example for IMG desktop pixel: