{"__v":4,"_id":"567b43334cde0321001e1182","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:58:27.815Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"examples":{"codes":[]},"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":7,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Digital Ad Specs\"\n}\n[/block]\nAd Specifications are technical requirements and format specifications for an inventory provider or advertising medium.\n\nThese technical requirements and format specifications often directly relate to the following attributes:\n\n  * Dimensions\n  * File size\n  * Animation length\n  * Creative types accepted (static image, rich media, custom formats, etc.)\n  * Third party vendor approval\n  * Coding or ad tagging attributes (including click functionality and z-index values)\n  * Creative asset delivery instructions (required lead time prior to launch)\n\nThese advertising specifications can vary for a single inventory provider based on many factors, such as: \n\n  * Desktop versus Mobile inventory\n  * Standard versus Expandable ad builds\n  * Direct versus Programmatic inventory purchasing\n\nThe Flite design and trafficking tools have no embedded advertising specifications, however our image proxy does have an individual file size limitation of 2MB per asset uploaded into a Flite ad. The Flite Design Studio allows for designs to create ad units with various functionality, coding attributes, and dimensions. The Flite ad tag is the same size and length regardless of creative's file weight (40kb ad build versus 400kb ad build).\n\nIf you are a Flite publisher client, then your ad builds should abide by your own publisher ad specs; these ad specs can be general or client/sale specific. Often direct purchases have more ad spec flexibility than programmatic sales.\n\nIf you are a brand client, creative agency, or media buyer that leverages Flite, please inquire regarding ad specs from each inventory provider on the campaign's media plan. Often programmatic buys are more stringent and ad specs are \"seller member\" specific. Flite advises that creatives are built to the lowest common denominator within the media plan's ad specs. This ensures that a single creative build can be trafficked across every inventory provider on the campaign plan; reducing the number of creative builds needed for a campaign launch.\n\nThe iAB has [documentation](http://www.iab.net/media/file/HTML5DAv101.pdf) and [file weight recommendations](http://www.iab.net/guidelines/508676/508767/displayguidelines) for HTML5 creative builds; in general, file weight specs for HTML5 ad unit are subject to the relationship between the media buyer and the inventory provider's operational team.\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Building Towards Inventory Reach\"\n}\n[/block]\nIf you are a brand client, creative agency, or media buyer that leverages Flite, we recommend consulting the media plan and inquire regarding inventory reach (based on creative dimensions).\n\ni.e. *If you are tasked with building a mobile interstitial creative*: Your inventory provider or media buying team may inform you that a 300x250 Mobile interstitial will have a larger inventory reach than a full-screen 320x480 creative build.","excerpt":"","slug":"ad-ops-ad-specs","type":"basic","title":"Ad Specifications"}

Design Studio

Campaign Studio

Report Studio

Metrics

Flite Console

Ad Ops

Component Studio

Ad Specifications

[block:api-header] { "type": "basic", "title": "Digital Ad Specs" } [/block] Ad Specifications are technical requirements and format specifications for an inventory provider or advertising medium. These technical requirements and format specifications often directly relate to the following attributes: * Dimensions * File size * Animation length * Creative types accepted (static image, rich media, custom formats, etc.) * Third party vendor approval * Coding or ad tagging attributes (including click functionality and z-index values) * Creative asset delivery instructions (required lead time prior to launch) These advertising specifications can vary for a single inventory provider based on many factors, such as: * Desktop versus Mobile inventory * Standard versus Expandable ad builds * Direct versus Programmatic inventory purchasing The Flite design and trafficking tools have no embedded advertising specifications, however our image proxy does have an individual file size limitation of 2MB per asset uploaded into a Flite ad. The Flite Design Studio allows for designs to create ad units with various functionality, coding attributes, and dimensions. The Flite ad tag is the same size and length regardless of creative's file weight (40kb ad build versus 400kb ad build). If you are a Flite publisher client, then your ad builds should abide by your own publisher ad specs; these ad specs can be general or client/sale specific. Often direct purchases have more ad spec flexibility than programmatic sales. If you are a brand client, creative agency, or media buyer that leverages Flite, please inquire regarding ad specs from each inventory provider on the campaign's media plan. Often programmatic buys are more stringent and ad specs are "seller member" specific. Flite advises that creatives are built to the lowest common denominator within the media plan's ad specs. This ensures that a single creative build can be trafficked across every inventory provider on the campaign plan; reducing the number of creative builds needed for a campaign launch. The iAB has [documentation](http://www.iab.net/media/file/HTML5DAv101.pdf) and [file weight recommendations](http://www.iab.net/guidelines/508676/508767/displayguidelines) for HTML5 creative builds; in general, file weight specs for HTML5 ad unit are subject to the relationship between the media buyer and the inventory provider's operational team. [block:api-header] { "type": "basic", "title": "Building Towards Inventory Reach" } [/block] If you are a brand client, creative agency, or media buyer that leverages Flite, we recommend consulting the media plan and inquire regarding inventory reach (based on creative dimensions). i.e. *If you are tasked with building a mobile interstitial creative*: Your inventory provider or media buying team may inform you that a 300x250 Mobile interstitial will have a larger inventory reach than a full-screen 320x480 creative build.