Creative States
CityScreen Context runs two separate state machines for creative approval, one per flow. Each has its own values and triggers, and a creative is in one of them.
This page is reference material. It is for employees who review creatives and need to explain what a state means. See the section overview for which flow you are in.
Moderation request states
A moderation request is created by a demand partner submitting a creative it intends to bid with.
| State | Final | Meaning |
|---|---|---|
|
no |
Waiting for a decision. This is the only state in which an employee can act, in which the demand partner can resubmit, and in which the request can be renamed or scoped. |
|
yes |
Approved. A campaign and its advertisements exist and the creative can win. |
|
yes |
Refused, with a reason that has been sent to the demand partner. |
|
yes |
Out of service. Either the demand partner withdrew it, or its media file stopped being usable. |
Transitions
| From | To | Trigger |
|---|---|---|
— |
|
A demand partner submits a creative.
The request is created in |
|
|
An employee approves. Where the organization uses employee positions, this happens when the last position votes and none of them rejected. It also happens with no employee involved at all if the demand partner is on the organization’s automatic approval list. |
|
|
An employee rejects with a reason. Where the organization uses positions, this happens when the last position votes and at least one of them rejected. |
|
|
Either the demand partner withdraws the submission, or the periodic media check finds the file unreachable or of the wrong content type.
The media check also tells the demand partner the creative was rejected, even though the state written is |
|
|
The demand partner withdraws the submission. Withdrawal is not blocked by the request already being final. |
Once a request leaves NEW, employee review is refused.
Reviewing a request to the state it is already in does nothing.
Where the state is written
For most integrations the state is written the moment the employee’s decision is processed.
For one content-management integration the decision is passed to the external system first, and the moderation request moves to CONFIRMED or REJECTED when that system reports back, so it shows NEW until then.
See supported partners for which integration this is.
The creative underneath
Every moderation request carries a creative, and that creative has a status of its own from the second state machine below. On this flow the request drives the creative’s status:
-
When the request is confirmed, its creatives are set to
CONFIRMED. -
When the request is rejected, any creative still in
APPROVINGis set toREJECTEDand given the decline reason. -
When the media check deactivates a request, its creatives are withdrawn.
Layout statuses
A layout is a creative submitted through the automated guaranteed path. It is reviewed on its own and never produces a moderation request.
| Status | Final | Meaning |
|---|---|---|
|
no |
Waiting for a decision. |
|
no |
Sent back to the demand partner with a comment. The partner is expected to correct or withdraw. |
|
yes |
Approved. The layout can be bound to an automated guaranteed advertisement. The demand partner is told the layout is reserved. |
|
yes |
Refused, with a comment. |
|
yes |
Withdrawn by the demand partner. |
The interface groups these into three tabs: approving covers APPROVING and REVIEWING, confirmed covers CONFIRMED, and rejected covers REJECTED and CANCELLED.
Transitions an employee can make
| From | To | Trigger |
|---|---|---|
|
|
An employee confirms. Where the organization uses positions, when the last position votes and every one of them confirmed. |
|
|
An employee sends it back with a comment, or — where positions are used — the combined verdict contains a send-back and no rejection. |
|
|
An employee rejects with a comment, or the combined verdict contains at least one rejection. |
|
|
An employee rejects a layout that had been sent back. |
A comment is required on both REJECTED and REVIEWING.
CONFIRMED, REJECTED and CANCELLED are final, and employees make no other transitions.
Transitions the demand partner can make
| From | To | Trigger |
|---|---|---|
— |
|
The demand partner submits a new layout, either by calling the platform or through the platform’s regular pull from the partner. |
Any status |
|
The demand partner resubmits under the same identifier, asking for approval. The layout returns to the queue and every recorded verdict on it is discarded. |
Any status |
|
The demand partner resubmits under the same identifier, flagging the layout as under review on its own side. |
Any status |
|
The demand partner withdraws the layout. |
A demand partner may ask for these three, and a layout submitted as already confirmed or already rejected is refused.
A layout the demand partner resubmits under the same identifier returns to the review queue with its recorded verdicts cleared.
Automatic confirmation
A layout from a demand partner on the organization’s automatic approval list goes straight to CONFIRMED when it is first created, with no employee involved and no verdicts recorded.