Update for Buying Networks: With the release of our latest version of the Atomx UI (Version 188, June 13, 2017), advertisers now manually decide if their creatives should be running on HTTPS or HTTP traffic. Why did we add this option? Because HTTP on HTTPS is not allowed anymore. More details you find here ->  https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content

atomx-http_vs_https
Manually decide if your creative should be running on HTTPS traffic.

Why using HTTPS in the first place?

A recent announcement by Google (urging website owners to switch to the HTTPS or else their site ranking will take a hit) drives more regular domain owners towards HTTPS. Starting with the latest release of Google Chrome v.56, any web site that is not running HTTPS causes a message appearing in the navigation bar: “Not Secure” on pages that collect passwords or credit cards. But this is only part 1 of a staged rollout that encourages websites to get rid of HTTP. In an upcoming release Google Chrome will label all non-HTTPS pages in incognito mode as “Not secure”. Step 3 will be that Chrome will label all plain HTTP pages as “Not secure”.

 


The problem plain old HTTP:  traffic data is not encrypted. It can be intercepted by 3rd parties to gather data being passed between the publisher and the advertiser. Preferred collector items: logins, passwords and credit card information. This problem can be avoided by using a secure version called HTTPS. It involves the use of an SSL certificate (secure sockets layer) which creates a secure encrypted connection between the web server and the web browser. Without HTTPS, any data passed is insecure. HTTPS was first used by sites where sensitive data is passed across the connection such as banks and e-commerce portals.