Dashboard Guide

A tour of the CADENCE dashboard: workspaces, projects, experiments, and how to navigate between them.

Workspaces

A workspace is your team's home in CADENCE. Everything lives inside a workspace: projects, experiments, goals, and team members.

  • Each workspace has a unique slug used in URLs (e.g., /dashboard/acme-corp)
  • Members have roles: Owner, Admin, or Member
  • Subscription tier is shown in the top-right corner of the navbar (Free, Pro, etc.)

When you sign up, you create your first workspace during onboarding.

Projects

Projects are testing environments within a workspace. Think of them as separate products, apps, or domains.

  • Each project has its own SDK key — This is how the SDK knows which experiments to load
  • Organize by product or team — e.g., "Marketing Site," "Mobile App," "Checkout Flow"
  • Navigate: Dashboard > [Workspace] to see all projects

SDK key management

Your SDK key is generated when a project is created. It's displayed once — copy and save it immediately.

SDK keys are shown once

If you lose your SDK key, you'll need to regenerate one from the project settings. The old key will stop working.

The SDK key is safe to include in client-side code. It only grants:

  • Read access to experiment and feature flag configuration
  • Write access to events (exposures, conversions, custom events)

It does NOT grant access to your Supabase database or admin functions.

Creating an experiment

  1. Navigate to a project and click New Experiment
  2. Fill in the details:
    • Name — Use kebab-case (e.g., hero-headline-test). This is what you pass to getVariant().
    • Hypothesis — What you expect to happen and why
    • Business goal (optional) — Links the experiment to Impact View
    • Variants — At least two: a control and one or more treatments
    • Traffic allocation — What percentage of users enter the experiment (0–100%)
    • Traffic weights — How traffic is split between variants (must sum to 100%)
  3. Click Create Experiment to save it as a draft
  4. Start the experiment to make it available via the SDK

Experiment status

| Status | Meaning | |--------|---------| | Draft | Created but not active. The SDK won't return this experiment. | | Running | Active. Users are being assigned to variants. | | Completed | Stopped with a decision. Results are final. | | Archived | Hidden from the main list. Can be viewed in archives. |

Experiment detail page

Click an experiment to see its detail page:

  • Variant breakdown — Side-by-side conversion rates for each variant
  • Daily metrics chart — Conversion rate trends over time (auto-updates every 30 seconds)
  • Statistical analysis — p-value, lift percentage, confidence intervals
  • Sample size — Exposures and conversions per variant
  • Actions — Stop the experiment, ship the winner, or archive it
  • Visual Editor — Open the Visual Editor for any variant to add visual mutations

Events page

Navigate to Projects > [Project] > Events to see raw event data:

  • Filter by event type (exposure, custom, conversion)
  • See user IDs, session IDs, timestamps, and properties
  • Useful for debugging event tracking

Navigation

The dashboard navbar includes these sections:

| Link | What it does | |------|-------------| | Projects | List all projects in the workspace | | Goals | Create and manage business goals for Impact View | | Impact View | Executive-friendly view of testing impact | | Calendar | Schedule tests and manage your testing roadmap | | Templates | Save and reuse experiment configurations | | Backlog | Prioritized list of test ideas |

Next steps