Product events.
On this device only.

Internal development view. Automatic recording is opt-in and starts with your next actions. Existing drafts and completed steps are not backfilled. Explicit local issue reports can be saved while automatic recording is off.

Event validation

0 rejected event writes. Retained events pass schema and request/outcome checks.

This is a bounded debugging sample, not a conversion dashboard. Pausing, clearing, storage failure or retention can leave an incomplete sequence. No 24-hour completion rate is calculated.

Event revisions follow requested material versions; retries keep their event revision. The export’s own exportRevision is separate. “Unmapped” means no matching generation was recorded in this journal. In-memory records must be exported before reloading.

Recent records

No local events recorded yet. Enable recording and use the maker, or explicitly save a local issue report.

{
  "schema": 1,
  "scope": "local-debug-only",
  "automaticRecording": false,
  "memoryOnly": false,
  "omittedEvents": 0,
  "invalidAttempts": 0,
  "events": []
}

What is stored?

Allowlisted event names, random task and attempt identifiers, material versions, tile counts, broad browser categories and normalized page paths. No photo, video, fingerprint, filename, account, query string, free-text feedback or raw error message is collected.

Up to 500 records are retained for 7 days. 0 records have been omitted by retention or capacity. The local recording preference remains until you change it or clear browser site data. Privacy details.

Generation success, system-share handoff, a download request and your own TikTok confirmations are separate events. App behavior and operation order still need physical-device validation.