CS Context features

CS Context pulls the screen-and-face catalog from the media owner's CMS on an hourly schedule and reconciles it automatically, so nobody has to enter inventory by hand.

4 settings on a face — format, camera flag, screen ID and legal entity — are edited in CS Context and survive each sync run; everything else is mirrored from the CMS and overwritten on every sync run.

Disabling a face withdraws it from sale: the face is removed from the partner catalog and ad requests for it are refused. Archiving clears it from the working list without losing history.

Read-only, per-integration attributes reported by the CMS — a store number, a venue code, a partner reference — are stored on the face and shown as extra report columns.

Each screen's time zone comes from its coordinates. Operating hours are mirrored from the CMS and published to demand partners, and CS Context does not filter the auction by them.

An RTB price list names the faces it covers, the demand partners allowed in through allow- or block-list priority groups, and the floor price. An organization with no price list sells nothing.

Seen at RTS-Decaux Kazakhstan

CS Context rescales the floor price to the requested slot length, and the floor calculation can draw on saturation data pulled from the CMS as one of its inputs.

An RTB price list can run in waterfall mode. Every admitted demand partner is asked at once, and the first usable answer wins at the amount it bid, with no price comparison and no ranking of partners.

On an RTB price list in auction mode, the highest bid wins and pays a clearing price derived from the runner-up's bid and the floor price. Every creative that can win has already been approved.

Seen at RTS-Decaux Kazakhstan

Every campaign carries a face list in whitelist or blacklist mode, checked on every ad request before a bid is considered. An employee can change the scope afterwards.

A demand partner proposes a budget and an hourly play allowance on named faces. Once reserved, the campaign pre-empts auction bids and draws down its budget and play count until either runs out.

Programmatic guaranteed campaigns are priced from a dedicated programmatic guaranteed price list. The price list is frozen onto the campaign when the campaign is reserved, so later edits to it do not change the campaign.

An automated guaranteed campaign reserves a frequency of plays on named faces over a period. The reservation is checked against each face's measured capacity before it is accepted.

Automated guaranteed campaigns are priced from a per-face grid of creative-length, frequency and price rows published in advance. A combination the grid does not price cannot be booked.

CS Context pushes a reserved automated guaranteed campaign to the CMS. A push retries automatically after a server error and, after a terminal failure, waits for an employee to press Retry.

Before a booking is accepted, CS Context asks the CMS for fresh, window-specific saturation data and checks the reservation against what the face can still deliver over the exact period booked.

CS Context computes and stores the booked volume and reports delivered ad plays against it for manual comparison.

A private deal hands a classic slot to one named partner's own ad server, which chooses the creative and sets the price; CS Context records the delivery and applies its commission.

Each private-deal opportunity is a live round trip to the partner's ad server, with an optional report-by deadline. A periodic pull of the CMS playout log is the authority for what is recorded as delivered.

Private-deal plays get a read-only statistics screen — by campaign, partner and individual play — showing ad plays and the platform's commission. The media price is not shown, because the platform never holds it.

An organization enables a platform-registered demand partner with its own connection details, then admits it into a price list. Both steps are necessary before the partner is offered a slot.

Seen at Icon DOOH

CS Context includes ready-made adapters for named demand partners (Hivestack, Vistar, COT) and content management systems (KIS, SpinetiX, CubicVision), and a generic SSP protocol for any partner that speaks it directly.

Seen at Big Tree

Owners, admins, managers and moderators review each submitted creative against the organization's own requirements and approve or reject it with a required reason. They can restrict approvals to particular faces.

Named demand partners' creatives are confirmed on arrival, with no human review and no sign-off from employee positions; file integrity checks still run, and the technical requirements are not checked on this path.

A rejected moderation request carries one unattributed free-text reason merging the reasons of all rejecting positions. Resubmitting to a pending request resets its verdicts, and a decided request needs a new creative.

Technical requirements are free text, published at organization level (with up to 10 attached PDFs) and separately per face; reviewers read them, and the platform does not check creatives against them.

In the only automatic creative check, every aspect ratio among the faces an automated guaranteed campaign is bound to must have a matching media file. It checks coverage only and does not run on RTB creatives.

Each confirmed ad play, meaning a single playback on one face, gets one row; audience estimates from the CMS are stored with it and are not multiplied into the count. Billing starts at a confirmed play.

CS Context writes off an ad request not confirmed within the window (2 hours by default), and it can never be confirmed afterward by any path. The demand partner is told the opportunity was not shown.

Where the CMS supplies one, CS Context stores a photograph taken while the advertisement played — up to 3 permanent images per ad/face pairing (morning, noon, evening), kept indefinitely.

CS Context builds downloadable XLSX reports of delivered plays per period and sales channel in the background. Regenerating a report replaces the earlier one of the same type, and reports are retained for 30 days.

Every confirmed real-time bidding sale writes a paired credit/debit record at the moment delivery is confirmed. Records are never edited or deleted, and a correction is always a new, opposite record.

RTB records a financial transaction per confirmed play, programmatic guaranteed records the whole budget at activation, automated guaranteed records a campaign-level price, and private deals record nothing in-platform.

An organization manages its own employees under 5 roles — owner, admin, manager, moderator, viewer — each with access to a fixed, documented set of interface screens. One login belongs to exactly one organization.

Every creative moderation request goes to every review position (legal, brand safety, and so on) at once, and a single rejection from any of them rejects the whole request.

Billing identity is recorded as one organization profile or several legal entities, each with its own tax details and attached faces, so revenue and inventory stay separate by legal entity.

Most changes to the organization's objects are logged with the user who made each change, the time and the values before and after it. The log can be filtered by period, user, object type and action.

CS Context sends in-app notifications when a report is ready, a moderation request comes in or a sync fails; each employee also manages 2 configurable email subscriptions for themselves.