{"__v":5,"_id":"56d0c60b1ecc471500f179ef","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":"56808da12b1d200d003c43a2","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":"2016-02-26T21:39:23.369Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"examples":{"codes":[]},"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":29,"body":"Flite tags can be uploaded into the Atlas ad server as \"Custom Creative Concepts.\"\n\nIn order to upload a single Flite tag into the Atlas server, the Flite tag will need to be saved within a text editor and associated with an HTML extension (i.e. FliteAdtag.html).\n\nWith the Flite tag saved and correctly formatted we can move into the Atlas UI.\n\nWithin Atlas, select your intended Campaign and drill-down into the \"Ads\" panel.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/NON2iaGhQhCgQxHyEx5o\",\n        \"Ads+Panel.png\",\n        \"225\",\n        \"320\",\n        \"#496072\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nWithin the Ads panel: Create and Name a new Creative Concept (represented by the green \"+\" button within the UI).\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/miIWU0IRt693CNuEyqVA\",\n        \"Create+new+creative+Concept.png\",\n        \"309\",\n        \"217\",\n        \"#60998e\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nUpload and associate your Flite HTML file from your local machine's file directory.\n\nSave your Creative Concept and Select Dimensions for your Flite create when prompted by the Atlas tool.\n\nAdditionally, you will need to:\n\n- Create a Destination URL or Landing Page. \n- Save and Name this URL string within your Atlas account. \n- Once this Destination URL landing page has been registered, you will need to associate with the uploaded Flite Creative Concept\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/3I22uGlRTRi7uzyLtquX\",\n        \"Atlas+Step1+2.gif\",\n        \"973\",\n        \"643\",\n        \"#4aa7ba\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nAfter uploading and saving the custom Creative Concept:\n\n- Select the Flite Ad that has successfully been uploaded into the Atlas platform\n- On the \"Review\" page, select the \"Preview\" button\n- Within the Preview test bed verify the Flite creative render and click out functionality\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://www.filepicker.io/api/file/L92S4hZqQmqf7R7o4Bnj\",\n        \"Atlas+Step2+2.gif\",\n        \"982\",\n        \"541\",\n        \"#539ea2\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n**Link Tags**\n\nIf there is a need for utilization of Link tags, this can be accomplished via the use of the <noscript> portion of the Flite ad tag.\n\n- Strip-out the image source and click out URLs\n- Prepend the URL string with the intended protocol (HTTP: or HTTPS:)\n- Test each URL string in a browser window to verify the landing page and image URL are functioning as intended and resolving","excerpt":"","slug":"ad-ops-uploading-flite-tags-into-atlas","type":"basic","title":"Uploading Flite Tags into Atlas"}

Uploading Flite Tags into Atlas


Flite tags can be uploaded into the Atlas ad server as "Custom Creative Concepts." In order to upload a single Flite tag into the Atlas server, the Flite tag will need to be saved within a text editor and associated with an HTML extension (i.e. FliteAdtag.html). With the Flite tag saved and correctly formatted we can move into the Atlas UI. Within Atlas, select your intended Campaign and drill-down into the "Ads" panel. [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/NON2iaGhQhCgQxHyEx5o", "Ads+Panel.png", "225", "320", "#496072", "" ] } ] } [/block] Within the Ads panel: Create and Name a new Creative Concept (represented by the green "+" button within the UI). [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/miIWU0IRt693CNuEyqVA", "Create+new+creative+Concept.png", "309", "217", "#60998e", "" ] } ] } [/block] Upload and associate your Flite HTML file from your local machine's file directory. Save your Creative Concept and Select Dimensions for your Flite create when prompted by the Atlas tool. Additionally, you will need to: - Create a Destination URL or Landing Page. - Save and Name this URL string within your Atlas account. - Once this Destination URL landing page has been registered, you will need to associate with the uploaded Flite Creative Concept [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/3I22uGlRTRi7uzyLtquX", "Atlas+Step1+2.gif", "973", "643", "#4aa7ba", "" ] } ] } [/block] After uploading and saving the custom Creative Concept: - Select the Flite Ad that has successfully been uploaded into the Atlas platform - On the "Review" page, select the "Preview" button - Within the Preview test bed verify the Flite creative render and click out functionality [block:image] { "images": [ { "image": [ "https://www.filepicker.io/api/file/L92S4hZqQmqf7R7o4Bnj", "Atlas+Step2+2.gif", "982", "541", "#539ea2", "" ] } ] } [/block] **Link Tags** If there is a need for utilization of Link tags, this can be accomplished via the use of the <noscript> portion of the Flite ad tag. - Strip-out the image source and click out URLs - Prepend the URL string with the intended protocol (HTTP: or HTTPS:) - Test each URL string in a browser window to verify the landing page and image URL are functioning as intended and resolving