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 Project ID — 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

Project ID & SDK key

Each project has a Project ID (e.g., proj_Ax8mK2pQr4nB) shown on the dashboard project cards and in Project Settings. This is the recommended way to connect the SDK to your site.

An SDK key (64-character hex string) is also available under Advanced in project settings. Both work, but Project ID is shorter and easier to use.

Safe for client-side code

Both the Project ID and SDK key are safe to include in client-side code. They only grant read access to experiment configuration and write access to anonymous events. They do NOT grant access to your database or admin functions.

If you need to rotate your SDK key, use the Regenerate Key button in project settings. The old key will stop working immediately.

Creating an experiment

  1. Navigate to a project and click Create Experiment
  2. Fill in the details:
    • Name — Use kebab-case (e.g., hero-headline-test). This is what you pass to getVariant().
    • Description — Brief description of what you're testing
    • Hypothesis — What you expect to happen and why
    • Business goal (optional) — Links the experiment to Impact View
    • Target URL (optional) — The page URL for the Visual Editor. Required for visual experiments.
    • Variants — At least two: a control and one or more treatments
    • Traffic allocation — What percentage of users enter the experiment (10–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. | | Paused | Temporarily stopped. Can be resumed to continue collecting data. | | 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 the event monitor. Events from your SDK integration (exposures, conversions, custom events) are being collected and stored. Detailed event analytics and filtering will be available in a future release.

For now, use your browser's Network tab to debug event delivery — look for requests to /api/sdk/[key]/events.

This Week

Navigate to Dashboard > This Week to see everything that needs your attention right now. This is the primary ritual view — all velocity notification emails link here.

Needs a Decision — Experiments with slots ending this week or overdue. Each card has inline Ship Winner, Keep Control, and Extend buttons so you can resolve without navigating elsewhere.

In Progress — Running experiments that don't need action yet, with progress bars showing days elapsed vs. total slot duration.

Up Next — The next 2 open slots. If a slot has no experiment assigned, CADENCE recommends the top backlog idea by priority score.

Backlog Queue — Top 5 ideas ranked by ICE score for quick scheduling.

Use the week navigation arrows to review past weeks (what was resolved vs. missed) or see future scheduled slots.

Notification preferences

Navigate to Settings > Notifications to control which emails you receive and when.

  • Ritual Schedule — Choose which day and time you receive your weekly digest (e.g., Monday at 8 AM Eastern)
  • Notification Types — Toggle velocity reminders (slot starting, decision deadlines), planning alerts (backlog running low), and results notifications independently

Navigation

The dashboard navbar includes these sections:

| Link | What it does | |------|-------------| | This Week | Weekly ritual view — decisions needed, running tests, upcoming slots | | 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 | Browse pre-built test ideas with suggested variants and metrics | | Backlog | Prioritized list of test ideas |

Next steps