Search Results

This article can also be found on our website. Adhese offers a robust consentless advertising capability, ensuring that you can continue to offer effective advertising campaigns to advertisers while fully respecting user privacy and adhering to strict data pro...

Ad blockers are browser plugins that prevent websites from requesting or loading ads. Depending on how they work Adhese will not be able to deliver ads, display ads or track ad impressions. Ad blockers can work in different ways: Ad requests are filtered out ...

Prebid is a free and fully open source header bidding solution available to any publisher, dedicated to header bidding in the ad tech industry.Header bidding allows publishers to create a short delay in ad serving to obtain bids from multiple demand partners b...

The Adhese TypeScript SDK simplifies ad integration across web environments by handling the underlying request and response logic, allowing you to implement ad placements without dealing with low-level API calls. At the same time, the SDK remains flexible: it...

The network panel will show all resources that are downloaded or uploaded the moment you visit a website. The most common use cases for Adhese users are: Making sure the necessary ad request(s) are being executed Inspecting the properties of an individual re...

Implementations that run on the Adhese SDK have 2 extra options for debugging. URL parameter By adding "?adhese_debug=true" to the URL of the page you can tell the SDK to print Adhese related messages in the browser console. Devtools The SDK contains a d...

Endpoint overview Requesting ads Name Path Response Type # of returned ads JSON 'GET'  /json/ Default JSON response One per requested position JSON 'POST' /json/ Default JSON response One per requested position AD (almost deprec...

Sequencing The sequence parameter can be used in advar templates to sort ads within the request response, and is therefore only relevant for stack implementations where multiple ads are returned for one placement.  Some examples are: VAST Adpods  Digital ...

What is Digital Out of Home? Digital Out of Home (DOOH) is digital advertising shown on screens in physical, public spaces - think digital billboards along a motorway, screens in shopping malls and supermarkets, displays in lifts and lobbies, transit and airp...

The headsup endpoint returns all the materials for the campaigns running on the requested DOOH position. It can be used by the DOOH screens to retrieve and cache all materials at the beginning of the day to avoid delays by having to download materials during t...

The stack endpoint allows you to request one position for which Adhese will return a list of ads. There are 2 versions:  /m/stack/: returns a limited amount of ads /e/stack/: returns an unlimited1 amount of ads2 1 The adserver rules still apply and will...

The JSON endpoint is the foundation of every display integration with Adhese. It gives you direct access to the ad server and Gateway without an SDK or library: you build the request, and Adhese returns the ads as JSON. Any environment that can send an HTTPS r...

Display advertising with Adhese can be delivered through several integration routes, ranging from a drop-in web SDK to a fully server-side API. All routes ultimately talk to the same adserver engine, so the choice of integration method is about how your platfo...

What is VAST? VAST - the Video Ad Serving Template - is the standard IAB introduced to make video and audio ad serving work across players from different vendors. It uses an XML schema to carry an ad's metadata from the ad server to the video or audio player. ...

The AD endpoint is used for integrations that can't parse a JSON response and require the response in a specific markup instead. It is typically used for video and audio setups, where ads are requested by media players and follow the VAST protocol in XML. The...