SSL Compliance: Fixing Non-Secure HTTP Assets in HTML5 Banners

SSL (Secure Sockets Layer) compliance is a mandatory requirement for digital advertising. All major ad servers (Google Ads, Campaign Manager 360, DV360, Xandr) require creatives to load via secure connections. If your creative contains a single non-secure asset, it will fail QC.

What is SSL Non-Compliance?

If your `index.html` references a resource (an image, stylesheet, script, or font) using a plain `http://` URL instead of `https://`, it is considered non-compliant. When served on secure publisher websites, mixed-content errors will cause browsers to block the ad asset, resulting in a blank creative space.

Resolving SSL Compliance Errors

Open your index files and search for the string "http://". Replace any instances with "https://". For example, change:

<script src="http://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js"></script>

to:

<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js"></script>

Alternatively, use **protocol-relative URLs** (like src="//ajax.googleapis.com..."), which automatically inherit the host document's security context.