Managing Demand Partners
A demand partner has to pass two gates before it can buy anything. The platform operator registers it once, platform-wide. Each organization then enables it for itself, with its own connection details.
Neither gate substitutes for the other. A registered partner no organization has enabled buys nothing; an enabled partner whose registry row is switched off buys nothing either.
The first gate is registration, done once by the platform operator. This page is for the owner, admin and manager employees of an organization, who work the second gate. A viewer sees the connection settings and cannot change them.
Registering a partner
Registering a partner is platform administrator work. It creates one row in a registry shared by every organization on the installation. The partner’s identity and system type are fixed at that moment. Once the row exists, the partner appears in every organization’s list of demand partners, switched off. See Integrations for what the system type decides and Supported partners for the types behind the named partners.
Switching a partner off platform-wide
The platform operator can switch a partner off for the whole installation at once. Every organization’s selling to that partner stops immediately, without touching anyone’s connection settings.
Closing a partner’s access to an exchange-supplied organization
For an organization whose faces come from a connected exchange, the platform operator can also close one partner’s access to that organization alone. The partner is then left out of that organization’s auctions and no longer sees the organization or its faces in the catalog it reads. This switch belongs to the platform operator and exists for exchange-supplied organizations.
Enabling a partner for an organization
An organization enables partners for itself in the client cabinet, under Settings, on the agencies screen. Every active registry row appears there as its own block.
Each block holds:
| Setting | Meaning |
|---|---|
Enabled |
Whether this organization sells to this partner at all. Clearing it leaves the connection details in place and stops the partner being asked. |
URL |
The base address the platform calls on the partner’s side. Everything the platform sends the partner — bid requests, win notices, play reports, moderation verdicts — goes to this address. |
Guaranteed URL |
A second base address, used for automated guaranteed campaign traffic. Left blank, the partner is not notified about automated guaranteed campaigns at all. |
Token |
The credential the partner issued to you, which the platform presents to the partner on every call. |
Additional fields |
Extra settings a particular system type needs — a network identifier, for instance. Which fields appear, and which are mandatory, depends on the type. |
Saving requires the owner, admin or manager role. Deleting a block removes the organization’s settings for that partner entirely, and the settings have to be entered again to bring it back; clearing Enabled keeps them.
Before you enable a partner, confirm who is asking.
| The token here is the one the platform sends outward. The token a partner sends inward, to read your inventory or submit a creative, is the organization’s own access token, shown on the same screen. See Access tokens. |
Organizations the platform sells for
Where an organization’s inventory is sold through the platform operator’s own demand relationships, the platform-level settings for a partner are used when the organization has none of its own. The platform operator maintains those once, and they serve every organization in that position. Such an organization sells to a partner while the platform-level settings for that partner are enabled.
Every other organization uses its own settings.
Allowing and blocking inside a price list
Enabling a partner makes it available to the organization. Which of its enabled partners actually see a given face is decided by the price list covering that face, and a price list expresses this in one of two shapes.
- An allow list
-
The priority group names the partners it contains. Only those partners are asked.
- A block list
-
The priority group is marked as an exclusion and names the partners to leave out. Every other partner the organization has enabled is asked.
Both shapes are set on the price list, per priority group, and RTB price lists covers how they are edited.
Where the settings are enforced
Two places enforce them.
- When a face is checked against its price list during the auction
-
The platform resolves the price list for the face and turns each of its priority groups into a list of partners to ask. Whichever shape the group takes, the result is filtered on both gates at once: the partner’s registry row must be active and the organization must have it enabled. A booking-only partner is never asked in an auction. If nothing survives the filter, the request ends with an error. See Auction, step 4.
- At the door, when the partner calls the platform
-
A partner reading inventory, submitting a creative or pulling statistics presents the organization’s access token under its own provider id. The call is accepted only if that organization has that partner enabled. Disabling a partner therefore closes its read access at the same moment it stops the bid requests, without any credential being revoked.
| Change | Takes effect at | Symptom for the partner |
|---|---|---|
Registry row deactivated |
Both points |
Stops being asked; inbound calls stop being answered. |
Organization disables the partner |
Both points |
The same, for that organization only. |
Partner removed from a price list’s allow list |
The request loop only |
Stops being asked for the faces that price list covers; inbound calls still work. |
Connection settings deleted |
The request loop only |
Stops being asked; inbound calls stop being answered. |
When a partner is not bidding
Work down the two gates before suspecting the partner.
-
Is the registry row active? Nothing below matters if it is not.
-
Has the organization enabled it, and are the URL and token filled in?
-
Does the price list covering the face admit it — named in an allow list, or absent from the block list?
-
Does its system type take part in bidding at all? A booking-only partner is not asked at slot time.
-
Is it answering inside the time budget? A partner that answers late is left out of that auction. See Timing budget.