You are here: Publishers > Getting started with OpenX Mobile > iOS App Transport Security (ATS)

iOS App Transport Security (ATS)

Last updated on June 15, 2017

App Transport Security (ATS) is an iOS app default setting which prevents apps from making non-secure connections. At the time of this publication, Apple has not yet required secure connections (see Apple iOS release documentation). Using non-secure connections is currently recommended by OpenX in order to avoid any negative revenue impact, until further notice from Apple about a deadline for ATS compliance with secure ads. If you have any questions, please contact your OpenX Account Manager.

If you decide to enable ATS for your app, review and implement the changes described here for tag-based and server-to-server integrations. If you are using the OpenX Mobile SDK or OpenX Mobile BidderOpenX's header bidding solution. Bidder enables publishers to realize the true value of their direct and indirect inventory in real time. "Bidder" can also mean a program designed to bid in real time on inventory in the OpenX Ad Exchange. for Apps, see ATS support in iOS SDK or ATS support in Bidder for Apps.

Important: Please contact your OpenX representative if you have not yet been migrated to an SSL-enabled delivery domain (one that ends in .openx.net).
Example: example-d.openx.net

Tag-based integrations

If your app serves ads via a tag-based integration, you can make your OpenX requests SSL-compliant by:

  1. Changing all references of HTTP to HTTPS.
  2. Ensuring you have an SSL-enabled delivery domain.

Example

After src=", this tag uses http, which is not SSL-compliant.

<script type="text/javascript" src="http://ox-d.your-instance.servedbyopenx.com/ma/1.0/jstag"></script>

​This tag becomes SSL-compliant after you change http to https and migrate to an SSL-enabled delivery domain, as shown below.

<script type="text/javascript" src="https://example-d.openx.net/ma/1.0/jstag"></script>​

Server-to-server (API) integrations

If your app serves ads via a server-to-server (S2S), or API integration, you can make your OpenX requests SSL-compliant by:

  1. Changing your request protocol from HTTP to HTTPS.
  2. Ensuring your have an SSL-enabled delivery domain.

Example

This request protocol is not SSL-compliant.

http://ox-d.your-instance.servedbyopenx.com/ma/1.0/​arj?auid=123456789​

This request protocol becomes SSL-compliant after you change http to https and migrate to an SSL-enabled delivery domain, as shown below.

https://example-d.openx.net/ma/1.0/​arj?auid=123456789​

This topic applies to Ad Exchange. This topic applies to Ad Server.

Feedback form