Owner analytics diligence: access, evidence, and scope

Request evidence by decision, not by dashboard

Define the decision and material claims first: audience quality, revenue durability, acquisition dependence, update impact, or partnership readiness. Map each claim to the smallest dataset: daily DAU and new users, cohort retention, session time, acquisition sources, payer conversion, revenue, refunds, product sales, technical performance, or funnel events. Record the metric definition, time zone, filters, period, and export time.

Roblox limits analytics access to the owner and group members with sufficient permissions. Prefer a supervised review, a role with the minimum necessary permission, or dated exports. API keys must have only needed scopes and should not be pasted into chat, email, or a document. Access proves permission to view; it does not prove that the selected range or definition supports the claim.

Worked example: verifying “growth is organic”

A public curve shows CCU doubling over four weeks. The owner says growth is organic. Ask for acquisition by source over the same four weeks and the matched prior period, plus new-user D1/D7 retention and spend by cohort. Suppose the export shows Sponsored Ads fell from 60% to 20% of new users while Home and Search grew, and new-user retention stayed within a stable band. The claim now has support, though “organic” still needs a stated source definition.

If only a cropped revenue screenshot is supplied, it cannot resolve acquisition or cohort quality. Record the claim as unverified and request the specific export. If the owner cannot share it, the business decision must price that uncertainty rather than silently replace missing data with public CCU.

Run a minimum-access review

Keep a request log so both sides know which claims have been verified.

1. List material claims and the decision each affects.
2. Map every claim to a metric, period, filter, and source.
3. Use supervised review, narrow roles, or dated exports.
4. Reconcile totals across statements, analytics, and public observations.
5. Remove access when the review ends and record unresolved items.

Security and evidence failures

Do not request passwords, cookies, recovery codes, or unrestricted keys. Avoid forwarding tax, identity, or player-level information beyond the people who need it. A screen recording can show a dashboard state but may omit filters, time zone, refunds, or later corrections; preserve the export and context.

Private data is not automatically correct or comparable. Changes in metric definitions, attribution, cohort maturity, and time zones can break a comparison. Separate source facts from your inference, and let missing evidence reduce confidence rather than become a zero.

Decision record

For each verified claim, note the authorized reviewer, access method, export time, filters, definition, and retention policy. Keep unresolved claims visible. At closure, remove temporary access and record that revocation without copying secrets into the diligence file.

Primary sources

• Roblox Analytics dashboard
• Roblox API keys
• Roblox Analytics