SSL Compliance

Vaida
Vaida
  • Updated

HTML5 Studio allows you to upload any kind of third-party HTML5 ad (an HTML5 ad that you created using other authoring tool) and test various features that are supported by our Ad Server.

Problem

Most of the publishers and programmatic ad exchanges are now using SSL-only environments, which means that all the components that come together with an ad and the ad server itself have to be SSL-friendly. There are some instances when users are loading various 3rd party JavaScript libraries from popular CDNs or assets from various unknown servers.  All of the requests have to be done via secured SSL channels, which means that an ad will be rejected by the publisher or programmatic exchange if you are using SSL non-friendly URLs.

Goal

URLs, that link to external resources, have to be made SSL-friendly: https:// or // has to be used instead of http://. This process has to be time-efficient as it is hard to manually scan through the source of each ad.

Workflow

SSL compliance can be achieved as a part of general ad compliance. It can be done by Creative Agency or Media Agency. We highly recommend managing compliance as early in the Ad lifecycle as possible. Therefore, HTML5 Studio is publicly available to any Creative Agency and it does not require credentials to access most of the features. It is worth noting that HTML5 Studio accepts content that is not necessarily built with the HTML5 Studio and allows to amend it if needed:

  1. Upload .ZIP file, that contains the ad, to the Studio.

    tutorial_1.png
  2. If asked, indicate correct banner category and format.

  3. If system is not able to detect correct width and height, make sure to indicate them as well.

    tutorial_2.png
  4. After you are done with the previous step, you will be given an option to add a Global clickTag on top of the banner. It is worth noting that this feature only works when your ad does not contain any other features that require user interaction (such as close or navigation buttons). That is because Global clickTAG is applied on top of the whole ad, which means that any click on the ad will initiate the Global clickTag feature leaving other components inactive.

    tutorial_3.png
  5. Export the Ad. (If you have Media Agency credentials to the Adform Platform, you can use the Upload feature that is next to Export and then you will be able to push the Ad directly to the campaign).

    tutorial_4.png
  6. If HTML5 Studio detects SSL non-friendly URLs, it will show the following dialog box (otherwise, it will proceed to export your ad):

    tutorial_5.png
  7. Click on Fix it and Studio will try to automatically fix all of the faulty URLs. If every URL is fixed, it will proceed to export your ad. Otherwise, it will populate a dialog box with a list of URLs that were not fixed (Studio does not fix URLs for servers that do not support SSL or it does not guarantee that those servers really support SSL).

    tutorial_6.png
  8. If Studio was unable to fix some URLs, close the dialog box, open file browser from the left side panel and click on the file that contains faulty URLs. Consequently, Studio will open Code Editor of the file that needs to have its URLs fixed. When in the source code, seek for the faulty URLs (you might find Ctrl + F shortcut to be more convenient) and provide the correct one instead. After fixing URLs, click Save and repeat the Export action to download the compliant version of an Ad.

    tutorial_7.png

Caution

If the particular resource resides on the server that does not support SSL (https), it will not be possible to fix those URLs. Always try to open the specific 3rd party resource in your browser with https instead of http to ensure that server really supports SSL. Adform recommends hosting all assets and resources on Adform's servers as we both support SSL and ensure load-balanced and geographically distributed delivery of content.

Was this article helpful?

/
How we can make it better?

Thank you for your feedback!