Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Once implemented, no further client-side changes are needed. Publishers can activate new demand sources, add or shape the data they share with their partners, set business rules, multipliers and even exceptions all through a centralised web application. These changes are executed instantly and do not need any intervention from webmasters web admins or app developers.

Implementing for using Gateway features or Direct Ad Server features is the same. Below you can find links to the various repositories with examples and code.

...

Adhese offers an open-source JavaScript SDK for implementation in web-based environments. This can be used stand-alone , but also integrates with various existing JS frameworks and wrappers. Developers pick the parts they need to keep the code as lightweight as possible.

...

An open-source native Android and iOS SDK are freely available. Mobile apps can implement the Adhese instance as a pure API as well, giving and give them full control over the user experience.

...

Any publisher can implement their Adhese instance as a pure API, calling the ad server endpoints directly from their mobile app, CMS system, Connected TV app, ... In one request, they receive campaigns for a number of several placements that can be visualised according to the device and context.

...

  • The most common implementation method: JSON or JSONP.
    The JSON or JSONP method bundles all advertisements in one request and visualise the creatives in the reserved spots on your website. With this method, it is easy to take into account the moment consider when an ad has an actual change to be seen (‘viewability’). JSON or JSONP is the most suitable method to use in a responsive environment.
  • 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 on the implementing page.

Examples You can be found find examples on the Implementation of the Adhese Ad Tags page.

...

Migrating from an existing ad server to Adhese can be accomplished in various ways, depending on the customer's 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 standard campaign, serving the legacy tags as third-party ads.  One hundred per cent of the inventory is sent to these campaigns to provide continuity. New campaigns are booked in Adhese , and, if necessary, 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 to the legacy ad server. This You can be done do this on a per-campaign basis or by sending send 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.