Skip to main content
The dashboard lives at app.traffical.io. It’s where you create projects, define parameters, run experiments, watch metrics, and manage everything that doesn’t fit in code. This is a tour. Each section links to a deeper walkthrough.

​
The hierarchy

The URL structure mirrors the hierarchy: organization → project → resource. 
app.traffical.io/{orgKey}                          ← org-level: API keys, billing, members
app.traffical.io/{orgKey}/{projectKey}             ← project-level: everything below
app.traffical.io/{orgKey}/{projectKey}/parameters
app.traffical.io/{orgKey}/{projectKey}/layers
app.traffical.io/{orgKey}/{projectKey}/events
app.traffical.io/{orgKey}/{projectKey}/metrics
app.traffical.io/{orgKey}/{projectKey}/definitions
app.traffical.io/{orgKey}/{projectKey}/pipeline
app.traffical.io/{orgKey}/{projectKey}/decisions
app.traffical.io/{orgKey}/{projectKey}/settings
The sidebar follows the same structure.
Dashboard home placeholder

​
What’s where

​
Organization

API keys

Create and revoke traffical_sk_... keys (SDK or management scope) per project + environment.

Billing

Plan, usage, invoices.

Members

Invite teammates, manage roles.

System

Org-wide settings.

​
Project

Parameters

All parameters in the project — synced (from CLI) and dashboard-only.

Layers & policies

Where experiments are configured. The bulk of day-to-day work.

Events

Event definitions, property schemas, the event explorer.

Definitions

Entities, assignments, facts — for warehouse-native metrics.

Metrics

Metric definitions and their results.

Pipeline

Pipeline runs, freshness, costs.

Decisions

Audit log of every policy lifecycle change.

Settings

Warehouse connection, SDK sync, hashing config, maintenance.

​
Day-to-day flow

Most teams work like this:
  1. Author parameters in code via .traffical/config.yaml and traffical push.
  2. Create policies in the dashboard — that’s where experiments are configured.
  3. Watch metrics during the experiment — visit the policy detail page.
  4. Promote the winner — update the parameter default and mark the policy complete.
Parameters live in code (the source of truth). Policies live in the dashboard (because they change frequently and need approval workflows). Events and metric definitions can live in either, depending on team preference.

​
Roles

RoleCan
AdminEverything, including billing and member management
EditorCreate/edit/delete experiments, parameters, definitions
ViewerRead-only
Roles are managed at the org level. Project-level scoping (so a team can only edit one specific project) is on the near roadmap.

​
Audit trail

Every change in the dashboard is captured in the decision log — policy state transitions, allocation overrides, rollout actions, manual completions, optimization milestones. Use it to answer “who turned this on / who paused it / who promoted that variant”.

​
Next steps

Your first experiment

The end-to-end flow from traffical init to reading results.

Parameters

Walkthrough of the parameters page.

Layers & policies

Where experiments live.

Settings → Warehouse

Connect Postgres, BigQuery, Snowflake, Databricks, or ClickHouse.