Mini Tech Update

More Transparency and More Revenue

Since Adbank 1.0 has been deployed, Dr Fodé, Conor, Tyler, and the rest of the development team have been working hard on key updates to the adbank platform, based on some excellent feedback by advertisers, publishers, and viewers.

For this tech update, the development team has been building more transparency through features that allow the Advertiser to track the ad codes distributed to the Publisher.

In the 1.0 version, the Advertiser didn’t have any information about where the banners were distributed, except the Publisher sites URL’s when the Advertiser used manual matching.

The Advertiser will now have the ability to see where the ads are distributed and if the invocation code is used on a Publisher’s website. Adbank adserver will provide the URL of the external pages where the ad placement occurred.

To increase their revenue, Publishers can use this function to use the single Ad Placement code to load banners from multiple sources — Adbank as well as other platforms — so if one of the sources doesn’t produce / return the banner, the other source is used.

To facilitate the interoperability with an Advertiser’s external adserver, in addition to HTTP 302 redirect support, we improved the integration between our Revive AdServer and the external Ad Platforms in order to deliver “external tag”.

The new architecture moves towards the non-blocking approach, where the External Ad Platform isn’t called by Revive AdServer, but by using the messaging middleware.

Want to know more about the adbank tech? Find out about the patent update here. The BLADE browser extension here. The token ecosystem update here. And adbank 1.0 here.

Stay up to date by joining the Telegram channel here.