This is an Admin guide for operating ShuffleKit, not for building a game. The Admin area is restricted to authorised accounts. It includes production and user data, so work from a need-to-know mindset, avoid sharing screenshots with personal data, and use destructive controls only after confirming their target.
Start with Overview
Overview collects system health and product signals, including feature-interest responses when they exist. Use it to notice a change worth investigating; do not treat a single headline metric as the explanation. Pick a period, form a specific question, then use Funnel, Onboarding, AI Usage, or Support to find the evidence behind it.
Investigate the funnel and replays
Open Funnel to see the curated visitor-to-signup-to-onboarding-to-subscription path. Switch time ranges, choose the data source, or use a custom date range before comparing periods. The summary shows visitor count plus signup, onboarding, and conversion rates; select a funnel step to see the sessions that reached it.
The Funnel page's Session replays button opens the replay drawer. It loads session recordings on demand and shows start URL, duration, active time, clicks, keypresses, console-error count, and whether the recording is live. Choose the watch action to open the recording in PostHog.
Use a replay to answer one bounded product question—for example, why people abandon a template-selection step—then record the finding. Deleting a session's funnel events or deleting a recording removes operational evidence, so verify the exact session and use the action only for a genuine removal need.
Monitor onboarding, AI, and the demo
- Onboarding reports the guided first-game flow and tours. Use it to locate a drop-off, then confirm the cause with the relevant funnel step or replay.
- AI Usage breaks down text and image use, cost, tokens, models, aspect ratios, and tools. Compare trends before changing limits or prompts; an isolated spike is not automatically a defect.
- Demo manages the product demonstration. Select the intended project, review the current demo snapshot and preview, and confirm the target before publishing or resetting demo/playtable state. Demo changes are visible beyond the Admin screen.
Work the support inbox
Support is the inbound operational inbox. Search by customer email or message; filter by reply state, ticket state, or topic (Bug, Feature, Account, Billing, or Other); and choose an ordering such as needs-reply first. The list supports keyboard navigation with j/k or arrow keys, and Escape closes an open conversation.
Open a conversation, read the thread, and write a concise reply. Drafts are preserved while navigating. Attach files only when they are necessary and safe to share, then send the reply and update the ticket to the appropriate open or resolved state. Do not paste secrets, reset links, payment details, or other customers' information into a response.
Close the loop
Route each operational observation back to a decision: a product issue becomes a scoped fix, a repeated support question becomes clearer documentation, and validated interest may guide the roadmap. The user-facing tutorials cover the tools customers can use; this guide explains the internal controls that keep those tools reliable.
