Private-Deal Reporting

Private-deal delivery has its own statistics screen, separate from the rest of the platform’s reporting. It answers two questions: what ran, and what commission the platform is owed for it.

This page is for an organization’s employees. The screen is not gated by employee role — owner, admin, manager, moderator and viewer all reach the same figures — and everything on it is scoped to your own organization. A viewer restricted to one legal entity sees only the faces attached to that entity.

Where the figures live

Private-deal statistics sit on their own screen in the client cabinet, alongside the statistics for the platform’s other non-auction delivery path. The screen carries a total for the selected period in its header, and two tabs of private-deal data beneath it.

Summary

One row per campaign and demand partner, with the number of ad plays and the total commission for each. This is the tab to read when you want to know how a partner performed over a month.

Ad plays

One row per confirmed ad play, listing when it played, on which face, for which campaign and partner, how it was delivered, and the commission on it. This is the tab to read when you are reconciling a specific day or a specific face against a partner’s own figures.

The interface labels these records impressions. They are ad plays — screen events — and Reporting explains how that differs from an impression in the industry sense.

Both tabs are read-only and take the same filters.

Period

A date-and-time range, accurate to the minute. It opens on the last seven days.

Demand partner

One or more of the partners registered for your organization.

Campaign

One or more campaigns. Private-deal campaigns are created by the platform when a partner’s creative first appears, so their names come from the partner.

Face

One or more faces.

Delivery type

Whether the play came from a live request or from a reserve playlist. The interface labels the two short and reserve. See Delivery for what each means.

What a row means

One row on the ad-plays tab is one play of one advertisement on one face at one moment, as reported back by your content management system and matched to a private-deal request or a reserve playlist.

The record is written by the reconciliation described in Delivery. A play appears shortly after it happened. Repeated reports of the same play are counted once, so a playout log pulled twice over overlapping windows produces no double counting.

The money figure the interface shows against a private-deal play is the platform’s commission, and the media price is not shown. See Fees and commission for how the platform’s commission is configured, and Settlement outside the platform below.

Settlement outside the platform

Private deals settle between the operator and the partner outside the platform, so CS Context writes no financial transaction for a private-deal ad play.

Specifically:

  • Your organization’s balance does not move when a private-deal ad play is recorded.

  • The financial transactions list contains no private-deal rows.

  • The private-deal total in the statistics header is a sum of the column beneath it for the filtered period.

The platform’s own commission on private-deal delivery is settled through the commercial arrangement between you and the platform operator.

What gets billed sets all of the platform’s accounting models beside each other — per-play financial transactions for real-time bidding, a whole-campaign price for automated guaranteed, settlement outside the platform for private deals — and is the page to read if the question is "why is this revenue not where I expected it".

Private deals in the settlement reports

Private-deal delivery reaches the platform’s generated XLSX reports. A direct settlement report produced for your organization carries private-deal rows alongside the real-time bidding rows: one row per campaign, partner, face and advertisement duration, with the play count and the total commission. The bid column on those rows is zero, because there is no bid.

The indirect and programmatic guaranteed variants carry no private-deal rows.

If you need a private-deal period on paper, request a direct report for the period from the reports screen. Generated reports are removed after their retention window; see Reports.

Reconciling with a partner

Two systems counted the same plays, and they will not agree exactly. The differences are expected, and knowing which is which saves time.

What you will see Why

The partner counts a play CS Context does not have.

The play was reported to the platform after the request had already been settled as failed — most often because the report window the partner itself set had expired. See the report window.

CS Context counts a play the partner does not.

The notice of the outcome did not reach the partner. The play is recorded on our side regardless; the record is written from your content management system’s log and does not wait for the partner’s acknowledgement.

The first play of a new creative is missing on both sides.

The opportunity that first introduced a creative is not filled — the creative is imported instead. See Creatives arrive from the partner.

The money figures do not compare at all.

They are different quantities. The partner is reporting media spend; CS Context is reporting the platform’s commission.

When the gap is larger than these explain, the place to look is your content management system’s playout log for the period, since that is the source the platform’s records are built from.