Standard Banner

Required Files Structure

When building banners with HTML5 technology, you should follow Adform’s specifications for HTML5 banners.

Each HTML5 banner prepared for the Adform system should be archived as a ZIP file. This ZIP file contains:

• A metadata file called manifest.json. The manifest.json file defines banner parameters such as name, description, dimensions, events, click tags, and source. These parameters are parsed and registered in the Adform system once the banner’s ZIP file is uploaded to assets.
{
    „version”: „1.0”,

    „title”: „300×250 Example Banner”,
    „description”: „optional string”,

    „width” : „300”,
    „height”: „250”,

„events”: {
        „enabled”: 1,
        „list”: {
            „1”: „myEventName1”,
            „2”: „myEventName2”,
            „3”: „myEventName3”
        }
    },

    „clicktags”: {
        „clickTAG”: „https://www.test.com”,
        „clickTAG2”: „http://www.adform.com”
    },

    „source”: „yourbanner.html”
}

Events for a banner could be enabled – 1 or disabled – 0. If you use custom events, please define them in an events list section on a manifest.json file. Your banner might contain multiple clickTAG instances. If so, please define all of them in a clickTAGs section on a manifest.json file.

• An HTML source file with the same name as defined in a manifest.json file. It is recommended to use only one HTML source per banner.
Important: A manifest.json file and a defined main HTML source should be located in a root directory of a ZIP file. Otherwise, the system will not be able to extract the zipped content correctly and you will receive an error on ZIP upload. Also, a total banner weight is measured when the content is unzipped.
• JavaScript sources like jQuery, GreenSock animation libraries and components, etc., if they are used in a banner. Libraries can be included as local assets or as external sources.
• Other assets like images, fonts, XML files, etc., that could be taken from local directories or from external paths.