Search Results

Adhese has a content cache system that facilitates video ad delivery in two ways: It allows prebid offers to be made on video ads by providing a URL containing the VAST markup of the ad that won the bid. Once a video ad is requested, it is retrieved via the...

If an issue is too severe or urgent to be resolved through a regular customer service request, an incident can be reported via the Adhese Customer Service Portal.By default, the request will be raised on behalf of the person who is creating the incident. The...

Adhese determines share via priority. The end date of a booking also increases priority: the earlier the end date, the higher the priority and the larger the share. Two bookings with the same priority setting, but with different end dates will result in the bo...

Additional configuration is required for inventory categories other than Display to be available in the Campaign Manager interface. If you would like the other categories to be available in the Campaign Manager interface, please contact Support. At publicatio...

Send audience segments to Adhese for targeted ad delivery on publisher-owned inventory. Files are exported to Adhese's secure S3 bucket. Adhese connection Overview You can send audience segments from Adobe Experience Platform to Adhese and use them for targ...

This guide explains how to create advertiser companies, invoicing companies, and brands in Adhese through the Campaign API, and how to connect (map) users to those companies and brands. All endpoints live under the Adhese API and are versioned with a /v1 pref...

Media Partners Media partners is the overarching term for an advertiser or debtor. Media partners have media brands associated with them. Create a Media Partner POST /v1/media-partners Creates a media partner (advertiser company, invoicing company, or both, d...

Connect users to media partners A user mapping grants a user access to a company/brand combination. Each mapping entry requires an advertiserCompanyId and a brandId; invoiceCompanyId is optional. Create a user mapping POST /v1/user-mapping Request body — Crea...

In order to get access to the API's of Adhese, you require a service account, your service account lets your backend system call the Adhese API without a user login. It uses the OAuth 2.0 client credentials flow: you exchange a client ID and secret for a short...

API Usage This page provides info on where to find detailed explanation on the Adhese APIs. See this guide on how to gain access to the APIs. It is intended as a starting point for developers and users who need to integrate with the API. Adhese stores its de...

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...

Bookings Bookings determine that what, where, how and when of ad delivery. Get a booking GET /v1/bookings/{bookingId} Returns a single bookings' details by booking ID. Request body Parameter In Required Type Description InternalId path Yes integer The booking'...