Creator Review: inspect an uploaded dataset
Run a temporary inspection of creator activity, identify the page’s at-risk group and compare uploaded identities with saved profiles.
This guide describes the available features. Your account role, assigned modules, signed contract and network plan determine which controls you can use. Reading a guide does not change your access.
Start here
- Prepare a .xlsx or .csv creator dataset with recognised Creator ID or Username fields.
- Choose Creator data file and select Inspect Dataset.
- Review Total Creators, At-Risk, Healthy and Matched to Profile in Inspection Summary.
- Search Creator Report and use Show at-risk only to focus the table.
- Check Last LIVE and Diamonds L30D together before deciding what follow-up is needed.
A fresh inspection, not an import
This screen processes the selected file for the current inspection. The uploaded dataset is not saved as a reporting import, and every upload produces a fresh inspection. Opening the page again without the file does not restore the prior report.
Matching a row to an existing profile can enrich its displayed username, name and image. It does not create a missing creator or overwrite monthly leaderboard history. Use the monthly import tools for persistent performance reporting.
Prepare the columns
Expected columns are Creator ID, Username, Group (Agency), Creator Network Manager, Last LIVE and Diamonds in L30D. At least a recognised Creator ID or Username must resolve for a row to be usable. The parser tries headers in the first row, then the second if no valid rows are found.
Preserve readable date and diamond values. The importer handles several common date representations, but ambiguous or unrecognised Last LIVE values can be treated as missing. Prefer a clear source date format and inspect the resulting date in the report. XLSX support also requires the server’s spreadsheet-reading capability; if the page reports a missing extension, contact the administrator.
Understand the at-risk rule
L30D means the last 30 days. This report flags a creator when Diamonds L30D is below 10,000 and Last LIVE is at least 60 days ago, missing or unrecognised. Both the diamond condition and the inactivity/missing-date condition matter. A row with at least 10,000 diamonds is not flagged by this particular rule.
Healthy means the row did not match this report’s rule; it is not a comprehensive assessment of creator wellbeing, conduct or future performance. This temporary rule also differs from the monthly score used in Creator Retention & Risk Radar.
Inspect and narrow the report
Inspection Summary reports total valid rows, the number flagged, the remainder and the number matched to a saved profile. A low match count suggests identifiers differ from your saved directory or the file includes people not yet recorded in the account.
Creator Report lets you search creator, group or manager, sort columns, and toggle Show at-risk only. Read the actual Last LIVE date and Diamonds L30D in a flagged row before contacting the creator; an incomplete export may explain the result.
Upload errors and starting again
Unsupported file types must be re-exported as .xlsx or .csv. No valid rows reports the requirement for Creator ID or Username and can show detected headers to help you correct the source file. An invalid session token requires a reload and a new inspection.
To review another file, choose it and Inspect Dataset again. There is no saved-case workflow, monthly write-back or automatic message to creators in this screen.
Frequently asked questions
Will Inspect Dataset update my creator records?
No. It displays a temporary inspection and may match existing profiles for display, without importing the dataset into saved monthly history.
Why is a blank Last LIVE flagged?
A missing or unrecognised date counts as inactivity for this rule when Diamonds L30D is below 10,000.
What does Matched to Profile mean?
The uploaded row was matched to an existing account creator identity, using Creator ID or username.
Why did the report disappear when I returned?
Inspection results belong to the upload request rather than a saved report. Upload the source file again to inspect it.
Still stuck? Note the page name, the step you tried and the exact message shown. Managers and sub-users should contact their network owner; owners should contact their platform administrator. Never include passwords, webhook URLs, recovery links or private identity documents in a general support message.