Creator discovery platforms service standards: six measures

What to take away

Creator discovery platforms service standards start from six observable events: provenance completion, correction propagation, access revocation, incident acknowledgement, accessible task completion and export integrity.
Every measure card carries a decision purpose, event, population, numerator and denominator, clock rules, timezone, query version, owner, blank threshold, escalation and recovery proof.
Each card is written against something the platform actually stores: a creator record, a shortlist or a campaign export.
Keep thresholds blank until your own baseline exists; the worked example below shows a filled card.
Meeting every buyer-set threshold proves nothing about creator authenticity, reach or campaign performance.

What every measure card must contain

Every card starts with a decision purpose and the event being measured, then the eligible population, numerator and denominator or unit, and clock start, pause and stop rules.

Timezone, period, exclusions, source system and query version follow. So do missing or late data treatment, the owner, a blank threshold, an escalation route and a recovery proof.

Required measure-card fields

Decision purpose
Event
Eligible population
Numerator and denominator or unit
Clock start, pause and stop
Timezone and period
Exclusions
Source system and query version

GOV.UK's performance-metric guidance starts from a service purpose and asks for meaningful data sources. It governs public services, so read it as method, not an imposed SLA: for a creator discovery platform that means naming the event log behind a creator record, a correction or an export.

Exclude records covered by documented synthetic tests and withdrawn records, which those dossiers keep separate from live data.

Six measures on one grid

Measure	Clock starts	Clock stops
Provenance completion	Record enters admitted-evidence review	Required fields present and verified
Correction propagation	Valid correction decision recorded	Update verified across named recipients
Access revocation	Removal instruction approved	Access paths verified inactive
Incident acknowledgement	Incident received in the agreed channel	Named incident owner acknowledges
Accessible task completion	Authorised user begins the specified task	Task ends without a blocking defect
Export integrity	Approved export closes	Reconciliation query returns

What each measure looks like on a creator discovery platform

Provenance completionthe source of the creator record — platform API, media kit or manual entry — plus its audience, permission and claim evidence, all verified.
Correction propagationa corrected rate, audience figure or disclosure status reaching every shortlist, saved search and live campaign list holding that record.
Access revocationevery agency seat, client login and API token that pulls creator records or campaign briefs verified inactive after a removal instruction.
Incident acknowledgementreceipt and acknowledgement by the named owner when a platform or data incident touches creator records or campaign data.
Accessible task completiona named task such as building a shortlist or exporting a campaign list finishing without a blocking defect.
Export integritythe exported creator list matching the platform snapshot field by field, including corrections and suppressions.

Example card with filled values

The number below is illustrative only.

Decision purpose: can this record enter shortlisting? Event: record enters admitted-evidence review. Population: records submitted in the month. Numerator: eligible records holding source, permission, definition, claim status and timestamp. Denominator: all eligible submitted records. Clock: none. Owner: evidence custodian. Threshold: 95 per cent complete within two working days, illustrative figure. Escalation: shortlisting pauses for that record. Recovery proof: corrected record plus a repeated register query.

Failure blocks progression, so the reviewer investigates missing fields before anything moves.

Provenance completion flow

Record enters admitted-evidence review
Check source, permission, definition, claim status, timestamp
Exclude synthetic tests and withdrawn records
Block progression if missing fields
Investigate missing fields
Correct record and repeat query

Set the card against a real contract. CreatorIQ, Traackr and Modash sell seat-based access, so revocation and export terms sit in the licence. Read the contract questions about data and exit before calling a threshold fair, and ask which of the six events above the platform's own reporting can produce.

Correction propagation and revocation clocks

Correction propagation measures elapsed time from an approved correction decision to a verified update across named recipients. Exclude rejected requests with a recorded reason. The ICO's accuracy guidance covers source, status and correction challenges; check its under-review status first.

Revocation counts every access path, not just logins. Population: accounts and tokens in scope, including the API connections that pull creator records and audience data. Numerator: paths verified inactive by the stop event. Owner: security lead. Escalation: contain the account and review exposure. Recovery proof: an independent access attempt plus the log record.

NCSC cloud audit guidance lists what a customer can ask about log availability, content, format and retention. It does not confirm your configuration.

Incident acknowledgement and export integrity

Incident acknowledgement measures elapsed time from recorded receipt to acknowledgement by the named incident owner. Define severity classes in writing first. A protected case log is the evidence.

Export integrity compares the export with the source snapshot field by field, including corrections, suppressions and history. Failure blocks closure; recovery means a corrected export and a rerun comparison.

Check the advertising side too: advertising checks for creator campaigns covers incentive labels and disclosure outside any service standard.

UK rules in one block

GOV.UK metric guidance, the ICO accuracy principle and NCSC audit principles answer different questions, so read them once. They apply UK-wide, not only in England. The ASA's CAP Code governs ad identification and disclosure in creator campaigns. The CMA covers competition and consumer law when comparing vendors, and Companies House confirms a supplier's registration. On campaign data, the ICO states that contextual advertising more readily enables compliance both with the PECR requirements and with UK GDPR obligations than other types of targeted advertising, and it is reviewing its approach to enforcing PECR regulation 6 consent rules.

Before you act

Work through these five points, then set thresholds.

Review the exact workflow and service edition first.
Keep the earlier result when definitions change.
Check the ICO guidance's under-review status before relying on it.
Record reproducible conditions for assistive-technology testing.
Block export closure until reconciliation passes.

Common questions

What fields must every measure card contain?

A decision purpose, the event and its eligible population. Add a numerator and denominator or unit, clock rules, timezone, period, exclusions and the source query version. Finish with owner, blank threshold, escalation and recovery proof.

How do I set a threshold without a baseline?

Run the query for one full period and record the result as your baseline. Set the threshold at or slightly above it, then review after a quarter. The 95 per cent figure in the example is illustrative only.

What does incident acknowledgement not tell me?

It times receipt to acknowledgement by the named owner. It says nothing about whether the incident was prevented or resolved well. Severity definitions, pauses and the timezone still need filling in.

Which UK guidance should I read first?

Start with the GOV.UK performance-metric guidance for method, then the ICO accuracy principle for correction duties. Add the NCSC audit principle for the revocation and incident cards.