{"__v":9,"_id":"567b4369ee052b1700dbd9eb","category":{"__v":33,"_id":"55566892150ba30d00f4e206","pages":["567b42903241c20d00b73091","567b429b17368a0d009a6e64","567b42a717368a0d009a6e66","567b42b24cde0321001e117f","567b4312ee052b1700dbd9e9","567b4322b56bac0d0019d8e8","567b43334cde0321001e1182","567b434b3241c20d00b73094","567b43594cde0321001e1184","567b4369ee052b1700dbd9eb","567b43774cde0321001e1186","567b438793919f0d00c97ae1","567b439693919f0d00c97ae3","567b43a3b56bac0d0019d8ea","567b43c13241c20d00b73096","567b43d4ee052b1700dbd9ed","567b43e5ee052b1700dbd9ef","567b43f317368a0d009a6e69","567b44053241c20d00b73098","567b4416b56bac0d0019d8ec","567b442893919f0d00c97ae6","567b49494cde0321001e118e","567b49584cde0321001e1190","567b49713241c20d00b7309f","567b498693919f0d00c97aea","567b49984cde0321001e1192","567b49a817368a0d009a6e71","567b49ca7c40060d00560436","5681b7a4aad86d0d00b9f276","5682d73a6d21130d00a705db","5682dfb77af9120d007ac2b4","568ee501bdb9260d00149d6c","56d0c60b1ecc471500f179ef"],"project":"555627c4ea5e120d001884fb","version":"555627c4ea5e120d001884fe","reference":false,"createdAt":"2015-05-15T21:43:46.368Z","from_sync":false,"order":5,"slug":"ad-ops","title":"Ad Ops"},"project":"555627c4ea5e120d001884fb","user":"55562799ea5e120d001884f8","version":{"__v":10,"_id":"555627c4ea5e120d001884fe","project":"555627c4ea5e120d001884fb","hasDoc":true,"hasReference":true,"createdAt":"2015-05-15T17:07:16.918Z","releaseDate":"2015-05-15T17:07:16.918Z","categories":["555627c5ea5e120d001884ff","55562a5526e9bc0d0044ea47","555653821026001900d72a3c","5556685c1026001900d72a85","5556687626e9bc0d0044ec04","555668821026001900d72a87","55566892150ba30d00f4e206","555668b826e9bc0d0044ec05","55e0fb6026f51b0d009b1746","567b3b3017368a0d009a6e54"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"createdAt":"2015-12-24T00:59:21.152Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"examples":{"codes":[]},"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":11,"body":"* [Impression Pixel Tag Implementation](#impression-pixel-tag-implementation)\n* [Click Tracking Tag Implementation](#click-tracking-tag-implementation)\n* [Click Redirect Implementation](#click-redirect-implementation)\n* [JavaScript Survey Tag Implementation](#javascript-survey-tag-implementation)\n\n---\n\n**Flite platform can support the following 3rd party tag formats:**\n\n  * Impression pixel tags: allow 3rd party to track ad impressions\n  * Click tracking tags: allow 3rd party to track ad clicks\n  * Click redirects: allow 3rd party to control landing page and track ad clicks simultaneously\n  * Brand study impression pixel tags: allow 3rd party Brand Research Vendors to track ad impressions for Brand study purpose \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Impression Pixel Tag Implementation\"\n}\n[/block]\nFlite platform can support almost all 3rd party impression pixel tags.\n\nThe cache-busting macro format we support are as follow and these are not case-sensitive in our console:\n\n  * [timestamp]\n  * [randnum]\n  * %n\n  * %%CACHEBUSTER%%\n  * ${REQUESTID}\n  * [CACHEBUSTER]\n\nAdditionally, Flite supports most commonly used replacement macros for cache busting, including [timestamp], [random], [randnum], %n, %%CACHEBUSTER%%, and ${REQUESTID}. The rule for supported cache busting macros is as follows:\n\n[*], #{*}, ${*} and %%*%% variations, where * = cachebuster, timestamp, requestid, randnum, or random. The algorithm is not case-sensitive.\n\nAny of these strings will be replaced with a timestamp when the pixel is fired.\n\nImplementation of impression pixel tags are simple and straightforward. Copy the tracking pixel URL string and paste directly into either of the two Tracking Pixel fields within Traffic module: Tag Defaults or Placements settings. Flite supports impression pixels with *HTTP://* protocol, *HTTPS://* protocol, and protocol relative URL strings starting with *//*.\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"RECOMMENDATION\",\n  \"body\": \"Flite recommends changing all impression tracking URLs and Initial Script tags to relative protocol prior to pasting or uploading into the Flite trafficking UI (remove *http:* or *https:*).\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/7ob8BiFZQbq4P47V6ItB\",\n        \"Screen+Shot+2015-08-31+at+9.02.33+AM.png\",\n        \"642\",\n        \"64\",\n        \"#833c18\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nTag Defaults tab is a global setting that would allow you to track impressions of the ad on ALL placements. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/zlzrsi0DTPWSWwDjvUU7\",\n        \"UpdatedTagDefaultImpressionPixel.jpg\",\n        \"900\",\n        \"373\",\n        \"#da3668\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nPlacements tab allows you to implement unique (1x1) impression pixel tags per placement.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/eTHBk9SBSRK1x2LKJ9p8\",\n        \"UpdatedPlacementImpressionPixel.jpg\",\n        \"900\",\n        \"388\",\n        \"#dc396a\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nIf you have more than one tracking tag, click on the Green + button to add up to 5 impression tracking tags in the Tag Defaults setting.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/CahXsLAyQVj7Nn6AQzwD\",\n        \"AddImpressionTrackingFields.jpg\",\n        \"427\",\n        \"452\",\n        \"#2c5b83\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Click Tracking Tag Implementation\"\n}\n[/block]\nImplementing click tracking tags in Flite would append the click tracking tag to the clickthru URL(s) within the ad as a prefix to the URLs, which allows you to track clicks on the ad. There will be manual configuration to the click tracking tags required in order for click tracking tags to work properly.\n\nEach configuration is different per vendor:\n\n  * DoubleClick: ?\n  * Mediaplex: ?mpro=\n  * Sizmek/MediaMind (Eyeblaster): &rtu=\n  * Atlas: ?h=\n\nFor other vendor not listed, please have clients check with their vendor's documentation for how to accept external redirects in their click tags.\n\n## Sample Tags \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/P61aXMxQToeB6nOT8qod\",\n        \"Screen+Shot+2015-10-08+at+12.03.57+PM.png\",\n        \"1003\",\n        \"302\",\n        \"#345df5\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nImplementation of the Click Tracking tag can be done in either the Click Tracking URL field in Tag Defaults section…\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/eSDKr2byTxehlCkAz2qH\",\n        \"Click_Tracking_Tag_Defaults.jpg\",\n        \"409\",\n        \"377\",\n        \"#2d5a82\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nor in the Click Tracking field per placement level in Placements section.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/FwM0z7HvTMxr76ljVTig\",\n        \"Click_Tracking_Placements.jpg\",\n        \"398\",\n        \"393\",\n        \"#da3d6e\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Click Redirect Implementation\"\n}\n[/block]\nThe most commonly used click tracking method is implementing click trackers as click redirects. Click redirects can be treated as a normal click through URL. You can either add the redirect to the ad or create a click variable to implement unique click redirect per placement. When an ad is clicked, the click redirect will ping its ad server first to record the click event, and then redirect to the landing page.\n\n**Implementing click redirect within an ad** \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/CrmZg21yRrewJEp1DxQB\",\n        \"6.jpg\",\n        \"846\",\n        \"560\",\n        \"#435f79\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Please visit [Click Variables](doc:ad-ops-using-click-variables) section on how to create a click variable.\",\n  \"title\": \"NOTE\"\n}\n[/block]\n**Implementing click redirect using click variable on Placement level** \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/Av66I7oEQYSK1CmFmkG0\",\n        \"Click_Variable_Placements.jpg\",\n        \"900\",\n        \"440\",\n        \"#bc476a\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"JavaScript Survey Tag Implementation\"\n}\n[/block]\nFlite platform can support most 3rd party JavaScript tags and fire-off these tags prior to loading the Flite ad unit onto a page; within the Flite platform, these JS tags are known as Initial Script calls.\n\nThese JS vendor tags include comScore, Vizu, Adsafe, InsightExpress, Dimestore, DataLogix, Adometry, Safecount/DynamicLogic. Flite supports impression pixels with *HTTP://* protocol, *HTTPS://* protocol, and agnostic protocol *//*javascriptsurveyvendorURL.com.\n\nFlite recommends that all JavaScript urls that are associated with the Initial Script field are set with an agnostic protocol rather than HTTP: or HTTPS:. Additionally, in order to populate the outlined vendor parameters, we recommend consulting the [supported macros help page](doc:ad-ops-third-party-macros-in-flite) to allow for dynamic population of campaign-level JS survey tagging.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/DWRsOMwSYCp2GH0rjgLw\",\n        \"Initial+Script.png\",\n        \"820\",\n        \"501\",\n        \"#356085\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"ad-ops-third-party-tracking-tags","type":"basic","title":"Third-Party Tracking Tags"}

Design Studio

Campaign Studio

Report Studio

Metrics

Flite Console

Ad Ops

Component Studio

Third-Party Tracking Tags

* [Impression Pixel Tag Implementation](#impression-pixel-tag-implementation) * [Click Tracking Tag Implementation](#click-tracking-tag-implementation) * [Click Redirect Implementation](#click-redirect-implementation) * [JavaScript Survey Tag Implementation](#javascript-survey-tag-implementation) --- **Flite platform can support the following 3rd party tag formats:** * Impression pixel tags: allow 3rd party to track ad impressions * Click tracking tags: allow 3rd party to track ad clicks * Click redirects: allow 3rd party to control landing page and track ad clicks simultaneously * Brand study impression pixel tags: allow 3rd party Brand Research Vendors to track ad impressions for Brand study purpose [block:api-header] { "type": "basic", "title": "Impression Pixel Tag Implementation" } [/block] Flite platform can support almost all 3rd party impression pixel tags. The cache-busting macro format we support are as follow and these are not case-sensitive in our console: * [timestamp] * [randnum] * %n * %%CACHEBUSTER%% * ${REQUESTID} * [CACHEBUSTER] Additionally, Flite supports most commonly used replacement macros for cache busting, including [timestamp], [random], [randnum], %n, %%CACHEBUSTER%%, and ${REQUESTID}. The rule for supported cache busting macros is as follows: [*], #{*}, ${*} and %%*%% variations, where * = cachebuster, timestamp, requestid, randnum, or random. The algorithm is not case-sensitive. Any of these strings will be replaced with a timestamp when the pixel is fired. Implementation of impression pixel tags are simple and straightforward. Copy the tracking pixel URL string and paste directly into either of the two Tracking Pixel fields within Traffic module: Tag Defaults or Placements settings. Flite supports impression pixels with *HTTP://* protocol, *HTTPS://* protocol, and protocol relative URL strings starting with *//*. [block:callout] { "type": "warning", "title": "RECOMMENDATION", "body": "Flite recommends changing all impression tracking URLs and Initial Script tags to relative protocol prior to pasting or uploading into the Flite trafficking UI (remove *http:* or *https:*)." } [/block] [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/7ob8BiFZQbq4P47V6ItB", "Screen+Shot+2015-08-31+at+9.02.33+AM.png", "642", "64", "#833c18", "" ] } ] } [/block] Tag Defaults tab is a global setting that would allow you to track impressions of the ad on ALL placements. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/zlzrsi0DTPWSWwDjvUU7", "UpdatedTagDefaultImpressionPixel.jpg", "900", "373", "#da3668", "" ] } ] } [/block] Placements tab allows you to implement unique (1x1) impression pixel tags per placement. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/eTHBk9SBSRK1x2LKJ9p8", "UpdatedPlacementImpressionPixel.jpg", "900", "388", "#dc396a", "" ] } ] } [/block] If you have more than one tracking tag, click on the Green + button to add up to 5 impression tracking tags in the Tag Defaults setting. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/CahXsLAyQVj7Nn6AQzwD", "AddImpressionTrackingFields.jpg", "427", "452", "#2c5b83", "" ] } ] } [/block] [block:api-header] { "type": "basic", "title": "Click Tracking Tag Implementation" } [/block] Implementing click tracking tags in Flite would append the click tracking tag to the clickthru URL(s) within the ad as a prefix to the URLs, which allows you to track clicks on the ad. There will be manual configuration to the click tracking tags required in order for click tracking tags to work properly. Each configuration is different per vendor: * DoubleClick: ? * Mediaplex: ?mpro= * Sizmek/MediaMind (Eyeblaster): &rtu= * Atlas: ?h= For other vendor not listed, please have clients check with their vendor's documentation for how to accept external redirects in their click tags. ## Sample Tags [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/P61aXMxQToeB6nOT8qod", "Screen+Shot+2015-10-08+at+12.03.57+PM.png", "1003", "302", "#345df5", "" ] } ] } [/block] Implementation of the Click Tracking tag can be done in either the Click Tracking URL field in Tag Defaults section… [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/eSDKr2byTxehlCkAz2qH", "Click_Tracking_Tag_Defaults.jpg", "409", "377", "#2d5a82", "" ] } ] } [/block] or in the Click Tracking field per placement level in Placements section. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/FwM0z7HvTMxr76ljVTig", "Click_Tracking_Placements.jpg", "398", "393", "#da3d6e", "" ] } ] } [/block] [block:api-header] { "type": "basic", "title": "Click Redirect Implementation" } [/block] The most commonly used click tracking method is implementing click trackers as click redirects. Click redirects can be treated as a normal click through URL. You can either add the redirect to the ad or create a click variable to implement unique click redirect per placement. When an ad is clicked, the click redirect will ping its ad server first to record the click event, and then redirect to the landing page. **Implementing click redirect within an ad** [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/CrmZg21yRrewJEp1DxQB", "6.jpg", "846", "560", "#435f79", "" ] } ] } [/block] [block:callout] { "type": "info", "body": "Please visit [Click Variables](doc:ad-ops-using-click-variables) section on how to create a click variable.", "title": "NOTE" } [/block] **Implementing click redirect using click variable on Placement level** [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/Av66I7oEQYSK1CmFmkG0", "Click_Variable_Placements.jpg", "900", "440", "#bc476a", "" ] } ] } [/block] [block:api-header] { "type": "basic", "title": "JavaScript Survey Tag Implementation" } [/block] Flite platform can support most 3rd party JavaScript tags and fire-off these tags prior to loading the Flite ad unit onto a page; within the Flite platform, these JS tags are known as Initial Script calls. These JS vendor tags include comScore, Vizu, Adsafe, InsightExpress, Dimestore, DataLogix, Adometry, Safecount/DynamicLogic. Flite supports impression pixels with *HTTP://* protocol, *HTTPS://* protocol, and agnostic protocol *//*javascriptsurveyvendorURL.com. Flite recommends that all JavaScript urls that are associated with the Initial Script field are set with an agnostic protocol rather than HTTP: or HTTPS:. Additionally, in order to populate the outlined vendor parameters, we recommend consulting the [supported macros help page](doc:ad-ops-third-party-macros-in-flite) to allow for dynamic population of campaign-level JS survey tagging. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/DWRsOMwSYCp2GH0rjgLw", "Initial+Script.png", "820", "501", "#356085", "" ] } ] } [/block]