Building Agency Analytics & Performance

Dashboards are decision interfaces.

A useful dashboard tells a named owner what changed, whether to care, why it happened, and what decision comes next.

The agency does not need one giant screen of metrics. It needs governed views for different decisions: creator investment, content learning, campaign delivery, pipeline action, financial control, capacity and data trust. Every number must retain its definition, grain, source, time window and limitations.

Dashboard value

Trusted metric × relevant context × accountable owner × decision threshold × drill-through evidence

Core rule: if no one can name the action a chart may trigger, it is decoration—not an operating metric.

Section 1

Start with Decisions, Not Available Data

Decision brief

Decision and accountable owner
Cadence and deadline
Options the owner can choose
Evidence and comparison required
Material threshold or exception
Necessary drill-through detail
Known uncertainty and human judgment
Follow-up action and record

Agency decision families

Which creators receive more, different or less service?
Which content patterns should be repeated or stopped?
Which campaigns need intervention or change control?
Which brand opportunities deserve action?
Where are margin, collection or payout risks?
Which workflow or role is the bottleneck?
Which controls or data sources cannot be trusted?
What portfolio concentration must be reduced?

Strategic

Portfolio choices

Monthly/quarterly investment, service, category, platform and concentration decisions.

Operational

Exceptions now

Daily/weekly overdue work, capacity, campaign, approval and creator-health interventions.

Control

Trust and exposure

Finance, rights, access, quality, data failures and reconciliations that require action.

Section 2

Define Data Grain and Stable IDs

Metrics become unreliable when creator, account, content, campaign and transaction are mixed in the same row. Define each entity, its grain and authoritative owner before joining data.

Entity	Grain	Key	Typical authority
Creator	One stable creator identity	Creator ID	CMS / creator master
Platform account	One creator on one platform/account	Account ID + creator ID	Authorized platform/account registry
Content item	One published/delivered output	Content ID + account ID	Content workflow / platform source
Campaign	One commercial initiative	Campaign ID + brand/opportunity ID	Campaign system
Creator participation	One creator in one campaign	Participation ID + creator/campaign IDs	Campaign system
Deliverable	One contracted output	Deliverable ID + participation ID	Campaign/content system
Financial event	One invoice, receipt, payout, cost or adjustment	Transaction ID + linked business IDs	Accounting/settlement system
Work item	One operational unit in a workflow	Work ID + related object ID	Work management system
Metric observation	One value for entity, metric, period and source	Entity + metric + timestamp/window	Analytics layer

Names, handles, campaign titles and invoice numbers are attributes—not reliable cross-system keys. Map them to stable internal IDs and retain effective dates for changing relationships.

Section 3

Give Every Metric a Written Contract

Definition field	Required answer
Business question	What decision does this metric support, and who owns that decision?
Name and meaning	Plain-language definition, interpretation and prohibited interpretation.
Formula	Numerator, denominator, aggregation method, units, currency and rounding.
Grain	Creator, account, content item, campaign, deliverable, transaction, team or time period.
Scope	Included/excluded platforms, statuses, entities, tests, internal work and adjustments.
Time	Event timestamp, reporting window, time zone, late-arriving data and period-close policy.
Source	Authoritative system/field, transformation lineage, refresh schedule and steward.
Quality	Coverage, freshness, confidence, known bias and reconciliation/control checks.
Threshold	Target/baseline, exception rule, expected action and escalation owner.
Version	Effective date, change history and comparability impact when definition changes.

Rate metric

Eligible events meeting condition ÷ defined eligible population

Change metric

(Current comparable value − prior comparable value) ÷ prior comparable value

Do not change a formula in place and preserve the same historical label. Version the definition and disclose where comparisons break.

Section 4

Build a Balanced Creator Portfolio Dashboard

Lifecycle

Stage / tier

Effective date

Relationship

Health / response

Owner evidence

Audience

Reach / quality

By platform

Content

Output / signal

By objective

Commercial

Demand / wins

Rate and fit

Economics

Revenue / contribution

Cash context

Operations

Service / workload

Exceptions

Risk

Rights / account

Review due

Portfolio cuts

Lifecycle and service tier
Cohort/start date
Creator category and market
Platform and format
Relationship owner/team
Commercial model
Revenue/contribution band
Risk and data-confidence band

Human decision remains

Invest, redesign, pause or exit
Separate early-stage tests from mature creators
Interpret platform/content context
Balance creator relationship and economics
Understand one-time events
Check whether service caused the outcome
Avoid penalizing missing/immature data
Record reason and next review

Never collapse creator value into one opaque score. Show the components, their dates and confidence; use a person accountable for the portfolio decision.

Section 5

Measure Content at the Correct Objective and Maturity

Question	Useful measures	Context required
Was it delivered?	Output, on-time, publish success, first-pass and revision count	Work type, complexity, dependencies and review path
Was it seen?	Qualified views/reach/impressions and distribution trajectory	Platform definition, observation window, paid/organic and audience size
Did it hold attention?	Watch time, completion/retention and meaningful consumption	Duration, format, platform and cohort benchmark
Did people respond?	Saves, shares, comments, follows, clicks or other objective action	Denominator, fraud/moderation, CTA and maturity
Did it create value?	Qualified lead, sale, campaign result, reusable asset or strategic learning	Attribution method, window, rights and incremental basis
Should we repeat it?	Pattern performance, cost, reliability and creator/audience fit	Sample size, variance, novelty and competing explanations

Snapshot metrics at consistent maturity windows—such as 24 hours, 7 days or 30 days where appropriate—and label the observation time. Never compare a fresh post with a mature one silently.

Section 6

Connect Campaign Delivery, Outcomes, and Commercial Close

Delivery/control view

Campaigns and deliverables by stage/age
Brief completeness and start gates
On-time delivery and at-risk deadlines
Approval cycle time and revision causes
Open changes and scope leakage
Publishing proof and rights expiries
Incidents and unresolved obligations
Report/invoice/settlement closure

Outcome/economics view

Objective-specific outcome metrics
Creator/content contribution with context
Contracted, delivered and approved value
Direct creator/vendor/production cost
Contribution and margin by campaign/cohort
Invoice, collection and payout timing
Client feedback and renewal action
Data coverage and attribution limitations

Campaign contribution

Recognized campaign revenue − creator cost − vendor/production cost − allocated direct delivery cost

Section 7

Build a Commercial Dashboard from Buyer Evidence

Pipeline

Value by stage

Evidence-weighted

Movement

Stage conversion

Cohort-based

Velocity

Time in stage

Active vs waiting

Coverage

Committee / next step

Owner + date

Matching

Shortlist outcomes

Reason/feedback

Win/loss

Cause / segment

No-decision separate

Renewal

Due / qualified

Relationship context

Concentration

Brand / category

Revenue/pipeline

Do not multiply opportunity value by a subjective probability and call it cash forecast. Keep pipeline, delivery, invoicing, collection and cash forecasts distinct.

Section 8

Separate Revenue, Margin, Cash, and Creator Obligations

Performance

Economic value

Recognized revenue, direct cost, contribution, margin and unit economics under governed accounting definitions.

Cash

Timing and liquidity

Invoiced, collected, receivable age, payout due, working-capital gap and forecast confidence.

Control

Reconciliation

Contract/campaign/statement/ledger linkage, unmatched items, manual adjustments and approval exceptions.

Contribution margin

(Recognized revenue − defined direct costs) ÷ recognized revenue

Creator amount outstanding

Approved creator earnings − valid deductions/adjustments − payments completed

Working-capital gap

Cash paid/committed before related client cash collected

Dashboard calculations do not replace the accounting ledger, creator statement or approved tax treatment. Reconcile to authoritative finance records and expose timing/definition differences.

Section 9

Measure the Operating System, Not Employee Busyness

Flow and capacity

Ready demand and work in progress
Lead/cycle time by work type
Stage age and waiting time
On-time completion and plan accuracy
Capacity/load by role and queue
Bottleneck, blocked and expedite volume
Handoff/reopen rate
Coverage and key-person dependency

Quality and control

First-pass quality and revision cause
Review SLA and decision latency
Post-release error/escape severity
Approval and control-gate coverage
Access/payment/change exceptions
Incident detection and closure
Creator/brand complaint resolution
Automation failure and human override

Use team/process measures to improve work design and service reliability. Avoid simplistic individual surveillance metrics that reward task volume, discourage help or ignore complexity.

Section 10

Put Data Quality on the Dashboard

Completeness

Required fields

By source/object

Validity

Allowed/consistent

Rule failures

Uniqueness

Duplicate rate

Identity collisions

Freshness

Age / last sync

SLA breach

Coverage

Observed / eligible

Platform/cohort

Reconcile

Matched totals

Difference

Pipeline

Load / failures

Retry backlog

Confidence

Band / reason

Known limitations

Source-to-ingest

Compare source counts/totals, extraction windows and failed pages/files/API requests.

Ingest-to-model

Test keys, duplicates, relationships, allowed values, transformations and late-arriving events.

Model-to-dashboard

Reconcile representative totals, filters, currency/time handling and metric definition versions.

Dashboard-to-decision

Record material exceptions, steward, correction due date and whether decisions must pause.

Section 11

Compare Like with Like and Show Uncertainty

Comparison controls

Same platform metric definition
Same content/account/campaign grain
Same observation and attribution window
Comparable format, duration and objective
Organic/paid distribution separated
Cohort and creator-stage context
Currency and time-zone policy
Minimum sample/coverage

Uncertainty signals

Freshness timestamp
Coverage percentage
Confidence band
Provisional/closed period
Estimated/verified flag
Partial platform source
Attribution method
Known exclusions and breaks

Normalized index

Entity value ÷ relevant comparable-cohort benchmark × 100

A normalized index improves comparability only if the cohort is meaningful and sufficiently populated. Always allow drill-through to the raw platform-specific measures.

Section 12

Govern Dashboard Access, Sensitive Fields, and Exports

Access design

Role and purpose-based views
Creator/client/team-level row restrictions
Sensitive financial/identity fields separated
Aggregate/minimize where detail is unnecessary
Named accounts and strong authentication
View, edit, export and administer separated
Joiner/mover/leaver controls
Periodic access review

Export and sharing controls

Authorized business purpose and recipient
Minimum necessary fields/period
Watermark/expiry where appropriate
Bulk export approval threshold
Audit log and anomaly alert
Secure transfer and retention expectation
External dashboard segregation
Revocation and incident path

Dashboard convenience does not override privacy, confidentiality, contractual or security obligations. Obtain qualified review appropriate to the data and jurisdictions involved.

Section 13

Turn Dashboards into a Decision Cadence

Daily exceptions

Operational owners act on overdue, blocked, failed-sync, high-risk or deadline-critical exceptions—without rebuilding reports manually.

Weekly operating

Review delivery, campaigns, capacity, quality, cash gates and creator/brand risks; record owner, action and due date.

Monthly portfolio

Decide creator tiers, investments, commercial focus, weak-fit work, unit economics and concentration using comparable evidence.

Monthly data control

Review reconciliation, freshness, coverage, definition changes, access/export exceptions and high-impact corrections.

Quarterly strategy

Reassess objectives, cohorts, target economics, platform/category exposure and whether dashboard metrics still serve decisions.

Review output

Decision + reason + owner + due date + expected result + re-check date

Section 14

Build the First Useful Dashboard in 30 Days

Week 1

Choose decisions

Select three recurring high-value decisions
Name owners, cadence and actions
Inventory source systems and known gaps
Draft metric contracts and acceptance criteria

Week 2

Model and reconcile

Define entity grain and stable IDs
Build minimum transformations
Reconcile samples and control totals
Add freshness, coverage and confidence

Week 3

Prototype with users

Build exception-first views and drill-through
Run actual decision meetings
Remove charts that trigger no action
Correct definitions and access

Week 4

Operationalize

Publish dictionary and ownership
Set refresh/incident support process
Train by decision role
Version release and prioritize the next decision

Ship one trusted decision loop before a company-wide dashboard. Broader coverage built on weak identity, definitions or reconciliation multiplies confusion.

Section 15

Common Dashboard Failure Modes

Starting with chart types

Start with a recurring decision, evidence needed, owner and action threshold.

Followers become creator performance

Use a balanced scorecard tied to stage and objective; audience size is context, not a verdict.

Cross-platform metrics are added directly

Preserve platform definitions and normalize only when the comparison is defensible.

Revenue equals cash

Separate contracted, delivered, recognized, invoiced, collected and settled states.

One average hides the portfolio

Show distributions, cohorts, concentration, outliers and data coverage.

Missing means zero

Distinguish zero, unavailable, not applicable, not yet mature and failed collection.

Dashboard has no drill-through

Every number should trace to governed detail records and source evidence.

Targets create gaming

Pair outcome measures with quality, risk and process health; review unintended behavior.

Refresh looks live but is stale

Display last successful refresh, observation window and partial-source warnings.

Everyone can export everything

Apply least privilege, sensitive-field controls, aggregation and monitored exports.

Section 16

Agency Dashboard Readiness Checklist

Decision

Every view has decision, owner and cadence
Metrics have thresholds and expected actions
Drill-through supports diagnosis
Human judgment and uncertainty remain visible

Model

Entity grain and stable IDs are defined
Authoritative source exists per object/field
Metric contracts are versioned
Platform/time/currency comparisons are controlled

Trust

Freshness, coverage and confidence are displayed
Source/model/dashboard totals reconcile
Missing is distinct from zero
Data incidents have owners and pause rules

Governance

Access and exports follow least privilege
Metric and data stewards are named
Decision cadence produces recorded actions
Changes are tested, versioned and communicated

SAIKO ANALYTICS RULE

Build dashboards around decisions, then earn trust through definitions, context, reconciliation, and visible uncertainty.

The best agency dashboard connects stable creator and business objects to governed metrics, shows what requires action, and lets every number trace back to source evidence.

“A dashboard should shorten the distance from evidence to a better decision—not increase the distance between the team and reality.”

SAIKO Agency Operations Playbook • MCN Guide #59

Ready to scale your creator strategy in China?

Explore All MCN Guides →