Output, winners and ad spend by designer and by creative producer, with self-initiated briefs tracked on their own. Source: the “Creative performance (DEV-215)” sheet · data through the week ending Oct 4, 2026.
Team output per week. “Originals” are new concepts; “Localized” are language adaptations.
| Week | Total | Originals | Localized | Static | Video | Own briefs | Δ vs prev |
|---|
Source: designersWeekly tab, rolled up to a team total.
Creatives delivered per week since tracking began.
Source: designersWeekly tab, rolled up to a team total.
Full months in the sheet. October is still in progress and will appear once its weeks are rolled up.
| Month | Created | Originals | Localized | Winners | Success rate | Ad spend | Designers |
|---|
Source: designers & creativeProducers tabs, rolled up to team totals.
Who built the creatives. A designer can author both originals and localized adaptations.
Click a column header to sort. Success rate = winners ÷ created.
| Designer | Created | Originals | Localized | Winners | Success rate | Ad spend |
|---|
Source: designers tab (monthly).
Each panel is one designer’s creatives per week across the five September weeks. Each panel is scaled to that designer’s own range and the weekly count is labelled on every bar; the last week is highlighted. August is left out — weekly tracking there was still sparse.
Source: designersWeekly tab.
Who briefed and shipped the creatives. Spend is attributed to the producer who ran the brief.
Click a header to sort. Success rate = winners ÷ created.
| Producer | Created | Originals | Localized | Winners | Success rate | Ad spend |
|---|
Source: creativeProducers tab (monthly).
Spend behind each producer’s creatives in the selected month.
Source: creativeProducers tab (monthly).
An own brief is a task a designer both invents and executes — the brief’s producer and the designer are the same person (the initials repeat, e.g. vm / vm for Василий). These sit outside the normal production queue, so they are counted on their own from the weekly sheet.
Self-initiated tasks per designer across the tracked weeks.
| Designer | Own briefs | Weeks active | Since |
|---|
Source: designersWeekly · Own Briefs column.
Team self-initiated output per week.
Source: designersWeekly · Own Briefs column.
The creatives carrying the most ad spend in each week (45-day spend window). Duplicate uploads of the same creative are merged into one row. The headline signal is whether the number of top-spenders is growing week over week.
How many creatives carried top spend each week — the number to watch is whether this is trending up.
Source: topSpend45dSummary tab (weekly totals).
Top-spend creatives credited to each creative producer, week by week. Most recent week first in the total.
Source: topSpend45dSummary tab.
Top-spend creatives credited to each designer, week by week.
Source: topSpend45dSummary tab.
— top-spend creatives this week, numbered and sorted by 45-day spend. An own brief tag marks creatives where producer and designer are the same person.
| # | Creative | 45-day spend | Producer | Designer | Languages | Copies |
|---|
Source: topSpend45d tab.
These are items the pipeline couldn’t fully attribute, so some creatives may be miscredited or left as unknown above. Unparsable — the file name doesn’t follow the naming convention. Winner unresolved — a winning ad couldn’t be matched back to a creative. Issue without naming — a Jira task with no creative name. In CW, not in Jira — a creative in CampaignsWell with no matching Jira task.
Total items flagged across all periods.
Source: discrepancies tab.
| Period | Scope | Issue | Creative / name | Source |
|---|
Source: discrepancies tab.
Read-only snapshot pulled from the “Creative performance (DEV-215)” sheet · built for the weekly creative review.