Pixel implementation

Event integration

If you already have an account with a safety tool, you can easily grab a pixel from your account and implement into StreamRail. You can also use a pixel in order to track your stats and data.
Click on Event Integration under Manage and create a new Event integration.
Give your event a relevant name (usually the name of the environment is mentioned in the name).
Select the event Method (IMG pixel, JS tag, iframe).
Select the percentage of the Impressions you would like to scan.
Paste the pixel you copied from your brand safety tool account to the URL/Script Tag text box.

You can set this pixel as either global or local. For further information please see below.

Global account vs. Traffic Channel

To configure the pixel as a global one so it will scan the Impressions of your entire StreamRail account, under Event integration tab, select “Yes” next to “Global Event” and choose the relevant environment. Then, go to System settings under Settings and attach your global pixel at the account level.
If you want to use this pixel as a local one meaning to use on specific suppliers, follow the below steps:
1. First, create your pixel under Event integration tab.
2. Navigate to the relevant Traffic Channel you wish to scan.
3. Scroll down to the “Event Integration” section and add the pixel by clicking on “Add Integration”. Start typing the name of the Event Integration, and the relevant events will automatically pop up in a list for your convenience.
Please note: in case you would like to change the percentage of the scanned Impressions on this specific Traffic Channel, click on “Custom sample” and then select the relevant %.

In order to deliver the Traffic Channel’s ID or Name in the pixel, the pixel must contain the following Macros, which are replaced automatically from the Traffic Channel data, according to your needs:
[SR_TRAFFIC_CHANNEL_NAME]
[SR_TRAFFIC_CHANNEL_ID]
[SR_TRAFFIC_CHANNEL_COST]

The same applies to data on the Ad Source, and these macros are replaced automatically from the Ad Source data:
[SR_AD_SOURCE_NAME]
[SR_AD_SOURCE_ID]
[SR_AD_SOURCE_RATE]
[SR_AD_SOURCE_COST]
[SR_ADVERTISER_ID]

The following macros must be added to the tag you provide your publisher, as well as the pixel, accordingly:

[WIDTH]
[HEIGHT]
[PAGE_URL]
[DPAGE_URL]
[DOMAIN]
[DDOMAIN]
[HEIGHT]
[USER_LON]
[USER_LAT]
[IP]
[APP_NAME]
[BUNDLE_ID]
[IFA]
[SUB_ID]
[SR_ORGANIZATION_ID]
[SID]
[USER_AGENT]
[UA]
[SR_PUBLISHER_ID]
[CB]
[DO_NOT_TRACK]

In order to add a parameter to the pixel which is not in the Traffic Channel’s data, the pixel must contain a custom parameter, which will be replaced automatically from the custom parameter (param1, param2, param3) passed through the Traffic Channel, accordingly:
[SR_CUSTOM_PARAM_1]
[SR_CUSTOM_PARAM_2]
[SR_CUSTOM_PARAM_3]
[SR_CUSTOM_PARAM_4]
[SR_CUSTOM_PARAM_5]
[SR_CUSTOM_PARAM_6]
[SR_CUSTOM_PARAM_7]
[SR_CUSTOM_PARAM_8]
[SR_CUSTOM_PARAM_9]

Sample usage:
http://my.pixel.com?foo=[SR_AD_SOURCE_ID]&bar=[SR_CUSTOM_PARAM_1]