Measurement
Part of Measuring gaming creator work with a metric dictionary and attribution kept apart from cause
A gaming creator dashboard built on four controlled sheets and fixed windows
Build a gaming creator reporting dashboard in England with controlled source exports, clear metric definitions, fixed windows, exception notes and decision owners.
Build the dashboard on four controlled sheets: source, content register, calculations and reporting view. The top view should identify the question, reporting period, included content, primary result, comparison and data freshness. Frame it around a monthly decision meeting, not a wall of platform cards, and let everything else explain or challenge that result.
This method works in an ordinary spreadsheet. It does not recommend or claim to have tested a dashboard product. YouTube and Google Analytics records are global; the ICO guidance applies across the UK. Pages were checked on 5 September 2026.
What to take away
- Build the dashboard around a monthly decision meeting, not a wall of platform cards.
- Keep raw platform exports unchanged in a source sheet and add a content register with stable IDs.
- Define fields before formulas, including platform label, meaning, unit, scope, calculation, source and limitation.
- Use one row per content-period pair to avoid comparing new uploads with accumulated archives.
- Show data quality flags on the first screen and end with decisions and owners.
Create four controlled sheets
Keep raw platform exports unchanged in a source sheet. Add a content register with stable IDs, game, format, publication time, duration, sponsor and campaign. Put calculations on a separate sheet, then expose only approved measures on the reporting view.
Four Controlled Sheets
- Source: raw platform exports unchanged
- Content register: stable IDs and campaign
- Calculations: separate sheet
- Reporting view: approved measures only
The minimum columns are set out below. Platform labels keep their export names so the mapping stays auditable.
| Sheet | Required columns |
|---|---|
| Source | file_id, origin, report name, account, filters, start, end, time zone, extracted at, operator, storage path |
| Content register | content_id, title, platform, format, published at, duration_seconds, sponsor, campaign_code |
| Calculations | content_id, period_label, period_start, period_end, reporting_age_days, measure_id, value, source_file_id |
A content register row might read: c-001, Friday night stream, YouTube, live stream, 2026-05-02T19:00Z, 7200, Sponsor A, SPONA-Q2. A calculation cell can use a SUMIFS formula keyed on content_id and period_label, for example =SUMIFS(value, content_id, $A2, period_label, $B2).
Add an extraction log. For each file, note its origin, report name, account, filters, start and end, time zone, extraction timestamp, operator and storage path. A corrected export becomes a new row rather than replacing the evidence behind an issued report.
Define fields before formulas
For each dashboard measure, write its platform label, plain-English meaning, unit, scope, calculation, source and limitation. Keep views, unique viewers and concurrent viewers separate. Define whether income is estimated, invoiced, received, VAT-inclusive or net of refunds.
For UK creators, VAT treatment depends on registration status, the place of the customer and whether the platform acts as agent or principal. Check the current HMRC registration threshold before treating platform income as outside the scope.
YouTube's video reach record defines impressions, click-through rate, views, unique viewers, average view duration and watch time. Copying those labels reduces the risk of a local term changing the meaning.
Live rows need their own fields. YouTube lists stream health, concurrent viewers, peak concurrents, chat rate and duration in its live analytics page. Do not append a live peak to archive views as if they share a unit.
Use one row per content-period pair
Give every video, Short or stream a stable content ID. Add the reporting age, such as first 24 hours, first seven days or calendar month. This prevents a new upload with two days of exposure being compared with an archive that has accumulated for a year.
Worked example: a Short published on 1 March 2026 and a stream published on 25 March 2026 can each be measured over their first 7 days. The rows are c-101, first 7 days, 2026-03-01 to 2026-03-07, reporting age 7 days and c-205, first 7 days, 2026-03-25 to 2026-03-31, reporting age 7 days.
Each row carries the same exposure window, so the older upload's longer archive does not inflate the comparison.
YouTube Advanced Mode can compare content groups and equal lifespans, according to its current tips. Export the comparison actually used, including its filters, rather than rebuilding a remembered view later.
Add campaign evidence without overjoining
Create a campaign dictionary before publishing links. Fix lowercase values for source, medium, campaign and content. Record the exact destination and owner. Reject a link that reuses a code from another sponsor or mixes spaces, hyphens and different spellings.
Google Analytics documents manual tagging and the dimensions attached to common parameters in its traffic-source guidance. Tagged sessions and events belong beside platform viewing data, not inside the view total.
Keep sponsor sales in a reconciliation sheet. Match only on the agreed code, event or transaction rule, remove cancellations where required and preserve the buyer's source file. If order-level information is unnecessary, request an aggregate.
Show data quality on the first screen
| Flag | Trigger | Owner |
|---|---|---|
| Provisional revenue | Not invoiced or not received | Finance lead |
| Delayed retention | Platform retention data older than the reporting window | Analyst |
| Missing geography | Country field blank or below coverage threshold | Analyst |
| Broken tags | Campaign code missing from tagged sessions | Campaign manager |
| Changed definitions | Measure label or formula differs from the last issued version | Dashboard owner |
| Buyer-supplied figures | Sponsor sends aggregate or edited sales data | Partnerships lead |
Add the extraction age beside the headline result. A neat chart should not conceal an incomplete source.
The ICO's storage and access technologies guidance covers analytics, tags, link decoration, consent and applicable exceptions. Ask a qualified reviewer to assess the real setup before collecting or combining visitor information.
End with decisions and owners
The final block should show repeat, revise, investigate or stop, followed by the reason, owner, deadline and next measurement window. Link the conclusion to the content IDs and evidence files used.
Freeze an issued version as PDF or protected output while retaining the calculation workbook. On the next close, add new extracts and document formula changes. A reproducible dashboard is more useful than a live screen whose historical result cannot be reconstructed.
Before you act
- Create four controlled sheetssource, content register, calculations and reporting view.
- Add an extraction log with origin, report name, account, filters, dates, time zone, timestamp, operator and storage path.
- Define each measure's platform label, meaning, unit, scope, calculation, source and limitation.
- Give every video, Short or stream a stable content ID and add reporting age.
- Create a campaign dictionary with fixed lowercase values for source, medium, campaign and content.
- Freeze an issued version as PDF or protected output while retaining the calculation workbook.
Common questions
Why should live rows have their own fields?
See the live rows note under Define fields before formulas. Live peaks and archive views do not share a unit, so they stay in separate fields.
How should campaign evidence be added without overjoining?
Create a campaign dictionary before publishing links. Fix lowercase values for source, medium, campaign and content. Record the exact destination and owner. Reject a link that reuses a code from another sponsor or mixes spaces, hyphens and different spellings. Tagged sessions and events belong beside platform viewing data, not inside the view total.
What should the final block of the dashboard show?
The final block should show repeat, revise, investigate or stop, followed by the reason, owner, deadline and next measurement window. Link the conclusion to the content IDs and evidence files used. This ensures decisions are tied to evidence and have clear ownership.
