Adserver tags (SSL/HTTPS)
Please keep in mind that HTTPS-tags always have to be included in your delivery. All linked parts in your HTTPS-tag (JavaScript, Images, CSS, etc.) need to be placed on HTTPSservers and must not reload data from unsafe HTTP Servers (e.g. streaming). Not only when advertising material in question is substituted or only existent in physical form but also when it comes to other tracking codes, the capability of the tags for HTTPS always has to be ensured.
SSL-compatible ads within the Mountain Travel Audience Platform, if they fulfil the following requirements:
• Every ad interaction has to be SSL compatible (“HTTPS”). All servers included have to be fully SSL certified.
• The ad tag should know automatically, that it is being called by the HTTP or HTTPS protocol. It should also automatically adjust its reaction, so it is SSL compatible
• A provider has to receive a special certification in order to publish ads within SSL compatible publisher inventory.
Impression Pixels / Tracking Pixels
Please be aware of the fact that every delivery of physical advertising material containing an impression pixel has to be specified for both HTTP and HTTPS. This also includes other tracking pixels.