{"id":"555627c4ea5e120d001884fb","name":"Flite Help Center","subdomain":"helpflite","versions":[{"_id":"555627c4ea5e120d001884fe","releaseDate":"2015-05-15T17:07:16.918Z","is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"}],"doc_slug":"","current_version":{"version_clean":"1.0.0","version":"1.0"},"oauth":{"enabled":false},"api":{"name":"","url":"","contenttype":"form","auth":"","explorer":true,"jwt":false,"authextra":[],"headers":[],"object_definitions":[]},"apiAlt":[],"plan_details":{"name":"Developer Hub","is_active":true,"cost":59,"versions":10000,"custom_domain":true,"custom_pages":true,"whitelabel":false,"errors":false,"password":true,"landing_page":true,"themebuilder":true,"stylesheet":true,"javascript":false,"html":true,"extra_html":false,"admins":true,"apps":true},"apps":{"enabled":false},"intercom":"","intercom_secure_emailonly":false,"flags":{"allow_hub2":false,"hub2":false,"migrationRun":false,"oauth":false,"swagger":false,"correctnewlines":false,"speedyRender":false,"ssl":false},"asset_base_url":""}

{"__v":2,"_id":"567b49ca7c40060d00560436","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-24T01:26:34.587Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"examples":{"codes":[]},"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":28,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Overview\"\n}\n[/block]\nThe Actions panel within Design Studio HTML5 allows for marketers to configure triggers and actions within creative builds. These triggers and actions can be scheduled or user-initiated and result in creative transitions or metrics logging. This article will specifically cover how the fire pixel action can be leveraged by ad operations professionals for third party event notations and data registration.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Introduction\"\n}\n[/block]\nWithin the Design Studio, there are many layers that form your creative build. If the intent is to \"fire-off\" a third party pixel based on a user initiated event, the creative build must reference this intent within the specific layers and their associated triggers and actions.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Process\"\n}\n[/block]\nWithin the design studio select the desired layer that will be associated with the third party pixel trigger and action. Once the layer has been selected, load the Actions panel and select the intended user initiated trigger.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/TVEtUYi7T3qJERxPwLoz\",\n        \"Screen+Shot+2015-09-16+at+8.09.20+AM.png\",\n        \"274\",\n        \"403\",\n        \"#7094b1\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nOnce the Trigger has been defined, you will asociate the Fire Pixel event within the Actions Panel.\n\nPasting a URL directly into the URL field (like below) will apply that 3rd Party tracking pixel to every ad tag generated from the ad unit.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/HTNL55WBRZSySog8H3U8\",\n        \"Screen+Shot+2015-09-28+at+10.03.50+AM.png\",\n        \"318\",\n        \"190\",\n        \"#509ee0\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nAssociating a Flite Variable with the *Fire Pixel* URL field (like below) will allow for the ad trafficking team to change the 3rd party tracking URL within the Traffic module at the placement level.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/jrAEovjRx2c64D09QnUS\",\n        \"Screen+Shot+2015-09-28+at+10.04.05+AM.png\",\n        \"347\",\n        \"187\",\n        \"#5c7593\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"ad-ops-fire-pixel-for-traffickers","type":"basic","title":"Fire Pixel for Traffickers"}

Fire Pixel for Traffickers

[block:api-header] { "type": "basic", "title": "Overview" } [/block] The Actions panel within Design Studio HTML5 allows for marketers to configure triggers and actions within creative builds. These triggers and actions can be scheduled or user-initiated and result in creative transitions or metrics logging. This article will specifically cover how the fire pixel action can be leveraged by ad operations professionals for third party event notations and data registration. [block:api-header] { "type": "basic", "title": "Introduction" } [/block] Within the Design Studio, there are many layers that form your creative build. If the intent is to "fire-off" a third party pixel based on a user initiated event, the creative build must reference this intent within the specific layers and their associated triggers and actions. [block:api-header] { "type": "basic", "title": "Process" } [/block] Within the design studio select the desired layer that will be associated with the third party pixel trigger and action. Once the layer has been selected, load the Actions panel and select the intended user initiated trigger. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/TVEtUYi7T3qJERxPwLoz", "Screen+Shot+2015-09-16+at+8.09.20+AM.png", "274", "403", "#7094b1", "" ] } ] } [/block] Once the Trigger has been defined, you will asociate the Fire Pixel event within the Actions Panel. Pasting a URL directly into the URL field (like below) will apply that 3rd Party tracking pixel to every ad tag generated from the ad unit. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/HTNL55WBRZSySog8H3U8", "Screen+Shot+2015-09-28+at+10.03.50+AM.png", "318", "190", "#509ee0", "" ] } ] } [/block] Associating a Flite Variable with the *Fire Pixel* URL field (like below) will allow for the ad trafficking team to change the 3rd party tracking URL within the Traffic module at the placement level. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/jrAEovjRx2c64D09QnUS", "Screen+Shot+2015-09-28+at+10.04.05+AM.png", "347", "187", "#5c7593", "" ] } ] } [/block]