Skip to end of metadata
Go to start of metadata

Implementation methods

Ad tags are the basis of the ad serving technology as they enable the measurement and delivery of targeted campaigns.

There are several ways to integrate the Adhese ad tag into your platforms:

  • Classic or legacy method: tag.js 
    The legacy method puts JavaScript functions into containers. The request to the ad server results in a document.write instruction in the implementing page. This is the most common implementation method.
  • Alternative methods with JSON or JSONP 
    This method makes it possible to bundle all advertisements in one request and visualize the creative in the right place. With this method it is easy to take into account the moment when the creative has a true change to be seen (‘viewability’). JSON or JSONP is the most suitable method to use in a responsive environment.
  • Video integration
    Adhese provides a SDK at Github that allows you to integrate pre-, mid-, and post-roll video ads in an HTML-based video player. The Adhese SDK is compliant to the standards of VAST 2, VAST 3, and VAST 4. Refer to Video ad serving for more information about video ad serving and VAST.

Migration

Migrating from an existing ad server to Adhese can be accomplished in various ways, depending on the requirements of the customer.

One approach is to focus on getting the Adhese tags up and running. Based on the inventory setup, all tags are made available. Existing tags of the legacy ad server can be implemented in Adhese as a normal campaign, serving the legacy tags as third-party ads. A hundred percent of the inventory is sent to these campaigns to provide continuity. New campaigns can be booked in Adhese and, if necessary, they can take priority over the legacy tags. Eventually, the legacy campaigns stop running as no more traffic is needed and all new or updated campaigns are booked in Adhese directly.

Another approach is to postpone tagging and start booking new campaigns in Adhese. Adhese tags or third-party tags can then be uploaded in the legacy ad server. This can be done on a per-campaign basis or by sending 100% of traffic to these Adhese campaigns in the legacy system. As tags are being distributed across the customer's network, they will show the same Adhese creatives but are either called directly through the Adhese tags or passing through the tags of the legacy ad server.

  • No labels