Skip to navigationSkip to content

Support for publishers

Top publisher support and yield optimization services

Investing in your success

district m invests in your success, and we’re committed to helping ensure performance at each stage of our relationship. Our technoligy and solutions are built for publishers by publishers, and so we approach each integration with keen insights on what’s needed to succeed. district m’s team of experts are always available to help you get the best performance out of our programmatic publisher solutions by providing you with yield management and optimization, world class support and thorough quality control.

F.A.Q.

To make the right decisions, you need to have the right answers to your questions - that's we've assembled some of our most frequenly asked questions here. If you still have unanswered, reach out to one of our experts for more guidance!

What is an end point?

An end point is a URL that you can call which will return a response.

In the header bidding world, an end point is usually called from the browser with parameters (size of placement, auction id, callback function, etc) and returns a response containing an ad information (ad url, price, etc).

Single Call

Some exchanges offer the possibility to call an end point and request multiple placements into one single call. This reduces the number of calls in a page.

What is a wrapper?

A wrapper is a container that let publishers put ad impressions up for simultaneous bids by multiple groups of buyers.

Client-side wrapper
A client-side wrapper will call one or many exchanges (SSPs and/or DSPs) via end points from the browser of the user. Each exchange will perform a second-price auction. The wrapper will compare the final result of each exchange second-price auction and select the highest value.

Benefits

  • Control partners directly on page or via UI
  • Open source solutions available
  • Free if implemented by the publisher
  • Easy to implement a new source of demand

Server-side solutions
A server-side solution will call one or many exchanges (SSPs and/or DSPs) from a server. They will each compete from a single second-price auction.

Benefits

  • A single second-price auction which increases yield
  • Better control on timeout
  • Reduction of number of calls
  • Transparency on bid landscape

Why are there differences between my ad server numbers and third party numbers?

In the ecosystem of internet ads, there will always be differences between the primary and the third party ad server. When the publisher's ad server returns the third party ad, it is considered rendered, thus, an impression is counted. The third party creative then begins to render and is then impacted by variables such as user match times, user bid times, connectivity, or simply the user leaves the page before the actual ad has time to display and get counted as an impression.

What kind of transparency do programmatic buyers have when buying inventory?

Transparency mostly depends on the source of inventory and the system(s) used to buy that inventory. The industry is moving towards full URL transparency, but some publishers may choose to make their inventory semi-transparent (domain only) or fully blind (usually user matching only). Some systems will allow full reporting after the campaign is complete, and some systems restrict this data per agreements made with their exchanges and publishers.

Access to our platforms

Let's talk about Tech!