What you need before launching your own ad exchange: a practical checklist

Getting an exchange platform is the easy part, whether you build one or run a white-label platform. What decides whether the business works is everything around it. This is the checklist we would want to go through before the first bid request arrives. It is not exhaustive, and it is not legal or financial advice, but if you cannot tick most of these boxes, you are not ready to launch.

1. Business basics

  • A legal entity and contracts. You will sign agreements with supply partners and demand partners. Have templates ready, reviewed by a lawyer who knows advertising: payment terms, discrepancy handling, invalid traffic, data protection, termination.
  • A clear model. Do you earn a margin on each transaction, a fee, or both? Decide how you will explain it to partners, because they will ask.
  • Data protection. Bid requests can carry personal data, so privacy law applies. Know your role and your partners' roles, and make sure consent signals are passed along correctly.
  • Your brand. A name, a domain, a website and a contact address that partners can find. On a white-label platform this is the brand your partners will see.

2. Partners

  • Supply and demand that match. A list of SSPs and DSPs you can realistically sign, with the formats, geos and verticals each one has or wants. A DSP that buys only video in one region is useless if all your supply is display somewhere else.
  • Quality requirements. Decide what you will not accept: unauthorised supply, unclear traffic sources, prohibited content. Put it in the contracts.
  • A testing plan. New partners should start small and be measured before they get full traffic.

3. Technical integration

  • Specifications per partner. Which OpenRTB version each partner uses, which fields they require or ignore, which formats they support, and which auction type they expect.
  • Endpoints and settings. For every partner: endpoint URLs, timeouts, floors, allowed formats and how much traffic they want to receive. Keep this documented outside the platform as well.
  • Notifications. Agree how wins, losses and billable events are reported and which price macros each partner sends or expects. Most later disputes start here.
  • Test traffic. Run test requests end to end before real money flows: request, bid, win, render, billing event, statistics.

4. Transparency

  • sellers.json. As an advertising system, you should publish a sellers.json file at the root of your domain listing your sellers, so buyers can see who they are buying from.
  • ads.txt and app-ads.txt. The publishers behind your supply need lines authorising your exchange. Prepare the exact lines and instructions for your supply partners to pass on.
  • The supply chain object. Pass on the schain you receive and add your own node, so buyers can see the full path.

Buyers check these things. Getting them wrong is one of the quickest ways to lose demand.

5. Money

  • Which numbers you bill on. Agree with each partner which statistics count when numbers differ, and what difference is acceptable before it is investigated.
  • Cash flow. Demand partners and supply partners rarely pay on the same schedule. Know how you will cover the gap.
  • Daily financial checks. Revenue, cost and margin per partner, checked daily in your financial statistics. Problems found at month end are expensive.

6. Operations

  • Someone watching the numbers. Requests, bid rates, win rates, timeouts and revenue by partner. Sudden changes usually mean a broken integration or bad traffic.
  • An invalid traffic policy. How you detect it, who decides to block a source, and how it is handled financially with both sides.
  • A support routine. Partners will contact you with questions and problems. Decide who answers, how fast, and how platform issues are passed to your provider's technical support.
  • A change log. Record every change to endpoints, floors and partner settings. When numbers move, the first question is always "what changed?".

7. People

Even with a white-label platform that is hosted and maintained for you, you need people for:

  • business development, to sign and keep partners;
  • ad operations, to configure, test and monitor them;
  • finance, to invoice, pay and reconcile.

In a small company these can be the same two or three people. They should still go through the platform training together, so that everybody knows where the settings and the statistics live.

Before you flip the switch

Run through the list once more with your first partners in mind. Start with a few partners you know well, prove that requests, bids, statistics and invoices line up, then grow. An exchange that launches small and clean grows faster than one that launches big and messy, because buyers and sellers remember both.

Thinking about running an exchange on a white-label platform? See what we provide.

Want to talk about your own setup? Get in touch with the Xendiz team.