{"__v":0,"_id":"58494889baeedf0f0052a4f4","category":{"__v":1,"_id":"56858d693703ed1700e420b2","pages":["5685a6b93703ed1700e420d4"],"project":"564621e00c30fb2100ba3814","version":"564621e10c30fb2100ba3817","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-12-31T20:17:45.077Z","from_sync":false,"order":2,"slug":"dsp-resources","title":"DSP Resources"},"parentDoc":null,"project":"564621e00c30fb2100ba3814","user":"564621d275c83f0d00e9d52d","version":{"__v":14,"_id":"564621e10c30fb2100ba3817","project":"564621e00c30fb2100ba3814","createdAt":"2015-11-13T17:46:09.275Z","releaseDate":"2015-11-13T17:46:09.275Z","categories":["564621e10c30fb2100ba3818","564624cf0c30fb2100ba3822","564628d69f3f550d00fa3db6","564dafeeda00e82b00ed601d","564daff8fc36dc3700882b95","564db0ccda00e82b00ed601f","564dcf87d3320b0d0028ca10","5661a6e436398e0d00f79566","568585153703ed1700e420b0","56858767d96a760d00545da6","56858d693703ed1700e420b2","56858d8d22c41b0d00e4666c","56859e9c009a8d0d00797130","5685a6453703ed1700e420d3"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-12-08T11:48:25.086Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":7,"body":"[block:callout]\n{\n  \"type\": \"danger\",\n  \"title\": \"Starting with 1st January 2017 MobFox will discard bids/ads with no secure markup\",\n  \"body\": \"Apple is making a push to secure HTTP connections from within their app environment by introducing and enforcing Apple's ATS (Application Transport Security) protocol.\\n\\nMobFox will check the markup and discard insecure bids if the publisher requested secure ads.\\n\\nPlease update your DSP/Network to support secure ads and serve only ATS compliant markup.\"\n}\n[/block]\nThe MobFox SSP will scan your markup and discard bids containing insecure markup. We are doing this to avoid render rate problems and in favour for other bids with secure markup to be able to win.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"What does this mean for your bid response and markup?\"\n}\n[/block]\nMobFox will include the **imp.secure** RTB attribute to indicate if the ad markup should be secure. In that case please make sure to comply with the below.\n\n## For Banner Ads (HTML markup)\nAll **src=\"\"** attribute values need to be loaded using **https URLs** only.\n\n## For Video Ads (VAST markup)\nThese items need to use **https URLs** in your VAST XML:\n* All Impressions\n* All Media Files\n* All Events\n* The VASTAdTagURI in case of a VAST Wrapper\n\n## For Native Ads (JSON markup)\n* All images need to use **https URLs**.\n* All impressions need to use **https URLs**.\n\n**Summary: All URLs (but not the click) must use HTTPs in order to be valid and secure markup**\n\nShould you have questions please don't hesitate to contact us at [mobfox-support:::at:::mobfox.com](mailto:mobfox-support@mobfox.com).\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Best practice\"\n}\n[/block]\nServing all URLs as **https URLs** will always be valid and working in secure and insecure environments.","excerpt":"What it means for you as a demand partner working with MobFox","slug":"demand-side-secure-ads","type":"basic","title":"Secure Ads"}

Secure Ads

What it means for you as a demand partner working with MobFox

[block:callout] { "type": "danger", "title": "Starting with 1st January 2017 MobFox will discard bids/ads with no secure markup", "body": "Apple is making a push to secure HTTP connections from within their app environment by introducing and enforcing Apple's ATS (Application Transport Security) protocol.\n\nMobFox will check the markup and discard insecure bids if the publisher requested secure ads.\n\nPlease update your DSP/Network to support secure ads and serve only ATS compliant markup." } [/block] The MobFox SSP will scan your markup and discard bids containing insecure markup. We are doing this to avoid render rate problems and in favour for other bids with secure markup to be able to win. [block:api-header] { "type": "basic", "title": "What does this mean for your bid response and markup?" } [/block] MobFox will include the **imp.secure** RTB attribute to indicate if the ad markup should be secure. In that case please make sure to comply with the below. ## For Banner Ads (HTML markup) All **src=""** attribute values need to be loaded using **https URLs** only. ## For Video Ads (VAST markup) These items need to use **https URLs** in your VAST XML: * All Impressions * All Media Files * All Events * The VASTAdTagURI in case of a VAST Wrapper ## For Native Ads (JSON markup) * All images need to use **https URLs**. * All impressions need to use **https URLs**. **Summary: All URLs (but not the click) must use HTTPs in order to be valid and secure markup** Should you have questions please don't hesitate to contact us at [mobfox-support@mobfox.com](mailto:mobfox-support@mobfox.com). [block:api-header] { "type": "basic", "title": "Best practice" } [/block] Serving all URLs as **https URLs** will always be valid and working in secure and insecure environments.