Supported Partners

When a slot on an enabled organization’s face comes up under a private deal, the platform asks HiveStack what to play for that screen and maps the creative it names to a campaign, creating one the first time it sees it. The platform also keeps a list of the creatives HiveStack has available for the relevant screens, so that the live answer resolves to something already known. Delivery outcomes are reported back to HiveStack over its own callbacks.

A face is addressed by its screen ID on these calls — HiveStack’s own identifier, stored on the face solely so that HiveStack can be asked about it in its own terms. A face without one cannot be offered. See Inventory for the screen ID.

The shape is the same as HiveStack’s: a live ad-decision call per opportunity, a list of available assets kept ahead of time, and outcome reporting over Vistar’s own proof-of-play callback. The platform records the price Vistar reports on its proof-of-play response.

Vistar requires an additional per-organization setting — the network identifier it authenticates against — entered alongside the URL and token on the organization’s connection settings.

The shape is the same again: a live creative request per opportunity, a regular sync of the creatives VIOOH holds for each face, and play confirmations sent back to VIOOH. A face is addressed by its VIOOH asset ID, stored on the face; a face without one is not offered.

VIOOH requires two additional per-organization settings — the VIOOH market and a separate key for play confirmations — entered alongside the URL and token on the organization’s connection settings.

COT is the one demand partner that talks in both directions.

Inbound, COT calls the platform, authenticating with the organization’s access token exactly as any other partner would. Over that surface it reads the organization’s players and their reported issues, submits creatives for review, sets and clears a long-running schedule, and reads back billing proofs and photo captures.

Outbound, the platform calls COT for a short playlist covering the immediate future, and pushes the review verdict on each creative COT submitted.

COT serves organizations whose server type is CityScreen.

Once a creative is approved, the platform creates the corresponding advertisement in KIS, amends it when it changes, and deletes it when the campaign stops. Every call is scoped by identifiers agreed with KIS.

The operator loads the catalog by import, and the faces in the file are the faces the platform knows. Creatives submitted without a face list have faces chosen for them by matching the aspect ratio of the media.

The platform pulls the face catalog from SpinetiX, and pushes each approved creative to SpinetiX for its own review, then polls for the verdicts. There are two reviews in the chain: a creative confirmed on this platform can still be refused by SpinetiX.

In the other direction, SpinetiX players ask the platform what to play, the same way any player does, and the request goes through the same auction — see Auction.

As with KIS, creatives submitted without a face list have faces chosen for them by aspect ratio.

The platform pulls the catalog, creates campaigns in CubicVision when creatives are approved, pauses and resumes them as their state changes, amends the faces they run on, pulls their moderation status back, and pulls confirmed ad plays for reconciliation.

Two behaviors are unique to it among the server types described here.

In the other direction, CubicVision asks the platform what to play, the same way any player does.