# Traffical ## Docs - [GET /v1/config/:projectId](https://docs.traffical.io/api/get-config.md): Fetch the pre-built config bundle for a project. Supports ETag caching for efficient polling. - [API overview](https://docs.traffical.io/api/overview.md): Authentication, base URL, and the endpoints SDKs use to fetch config and send events. - [POST /v1/decide/:policyId](https://docs.traffical.io/api/post-decide.md): Server-side per-entity decision endpoint for adaptive policies with Thompson Sampling. - [POST /v1/events](https://docs.traffical.io/api/post-events.md): Send exposure, decision, and track events to the Traffical edge for analytics and optimization. - [POST /v1/resolve](https://docs.traffical.io/api/post-resolve.md): Server-side parameter resolution for SDKs in `evaluationMode: "server"`. - [Decisions & attribution](https://docs.traffical.io/concepts/assignments.md): How a parameter resolution becomes a decision, how decision IDs flow through your application, and how track events get attributed to experiments. - [Events](https://docs.traffical.io/concepts/events-and-metrics.md): Exposure, decision, and track events — what gets captured and how it powers experiments and optimization. - [Layers](https://docs.traffical.io/concepts/layers.md): Layers partition the parameter space for mutual exclusivity and enable safe concurrent experimentation. - [Parameters](https://docs.traffical.io/concepts/parameters.md): Parameters are typed configuration values with defaults — the building block of everything in Traffical. - [Policies](https://docs.traffical.io/concepts/policies.md): Policies control how parameter values are assigned to users within a layer — from static A/B tests to adaptive optimization. - [Projects & environments](https://docs.traffical.io/concepts/projects-and-environments.md): The hierarchy your SDK keys point at: organizations, projects, environments, and unit keys. - [Warehouse-native](https://docs.traffical.io/concepts/warehouse-native.md): Compute experiment metrics directly from your own data warehouse. Define assignments and facts as SQL — Traffical aggregates and runs significance tests. - [BigQuery](https://docs.traffical.io/connectors/bigquery.md): Connect Traffical to Google BigQuery for warehouse-native metrics. - [ClickHouse](https://docs.traffical.io/connectors/clickhouse.md): Connect Traffical to ClickHouse (self-hosted, ClickHouse Cloud, Altinity) for warehouse-native metrics. - [Databricks](https://docs.traffical.io/connectors/databricks.md): Connect Traffical to Databricks SQL warehouses (Unity Catalog) for warehouse-native metrics. - [Warehouse connectors](https://docs.traffical.io/connectors/overview.md): Connect Traffical to your data warehouse for warehouse-native metrics. Postgres, BigQuery, Snowflake, Databricks, and ClickHouse are supported. - [Postgres](https://docs.traffical.io/connectors/postgres.md): Connect Traffical to a Postgres database for warehouse-native metrics. - [Snowflake](https://docs.traffical.io/connectors/snowflake.md): Connect Traffical to Snowflake using key-pair authentication for warehouse-native metrics. - [Decision log](https://docs.traffical.io/dashboard/decisions.md): An audit trail of every policy lifecycle change — who did what, when, and why. - [Definitions in the dashboard](https://docs.traffical.io/dashboard/definitions.md): Entities, assignments, and facts — the building blocks of warehouse-native metrics. - [Events in the dashboard](https://docs.traffical.io/dashboard/events.md): Event definitions, property schemas, property groups, the event explorer, and schema violation diagnostics. - [Layers & policies in the dashboard](https://docs.traffical.io/dashboard/layers-and-policies.md): Creating layers, configuring policies, managing allocations, conditions, and rollouts. - [Metrics in the dashboard](https://docs.traffical.io/dashboard/metrics.md): Defining metrics, reading per-policy results, configuring goal metrics for adaptive policies and rollout health gates. - [Dashboard tour](https://docs.traffical.io/dashboard/overview.md): A guided walkthrough of the Traffical dashboard — where to find what, and what each section is for. - [Parameters in the dashboard](https://docs.traffical.io/dashboard/parameters.md): The parameters list, parameter detail page, layer assignment, sync status, and dashboard-only vs synced parameters. - [Pipeline in the dashboard](https://docs.traffical.io/dashboard/pipeline.md): Watch warehouse-native pipeline runs, inspect freshness, debug failures. - [Policy health](https://docs.traffical.io/dashboard/policy-health.md): Diagnostics for running policies: exposures flowing, sample ratio, per-allocation floors, freshness, guardrails, and optimizer eligibility. - [Settings](https://docs.traffical.io/dashboard/settings.md): Project settings — warehouse connection, SDK sync, hashing, API keys, maintenance. - [A/B testing](https://docs.traffical.io/experimentation/ab-testing.md): Run a static experiment end-to-end — define parameters, create a policy, implement in code, measure results. - [Feature flags](https://docs.traffical.io/experimentation/feature-flags.md): A feature flag is a boolean parameter under a policy. Same primitives, with optional safety from rollouts and targeting. - [Optimization](https://docs.traffical.io/experimentation/optimization.md): Adaptive policies that learn from rewards: Thompson Sampling, UCB1, Epsilon-Greedy, per-entity bandits, and contextual bandits. - [Rollouts](https://docs.traffical.io/experimentation/rollouts.md): Progressive delivery with automated ramp, health checks, and rollback strategies. - [Canonical experiments](https://docs.traffical.io/guides/canonical-experiments.md): Patterns by surface and shape — backend, web, mobile, SSR, cross-surface, per-entity, batch, rollout, contextual, warehouse-native, multi-tenant. - [Experiment design](https://docs.traffical.io/guides/experiment-design.md): A practical checklist for PMs, marketers, and engineers running their first few experiments — hypotheses, metrics, guardrails, sample size. - [Your first experiment, end-to-end](https://docs.traffical.io/guides/first-experiment.md): From an empty repo to a running A/B test in twenty minutes — CLI init, parameter definition, dashboard policy, SDK code, reading results. - [Type-safe events end-to-end](https://docs.traffical.io/guides/type-safe-events.md): Property schemas, property groups, generated TypeScript types, dev-mode warnings, and reject-on-violation enforcement. - [How it works](https://docs.traffical.io/how-it-works.md): Local resolution from a config bundle, evaluation modes, and how SDKs talk to Traffical. - [Introduction](https://docs.traffical.io/introduction.md): Traffical is parameter-first experimentation, feature flags, and adaptive optimization in one system. - [Quickstart](https://docs.traffical.io/quickstart.md): Install the Node.js SDK, resolve your first parameter, and track an event in under five minutes. - [Glossary](https://docs.traffical.io/reference/glossary.md): Definitions of the terms used throughout the Traffical docs. - [JavaScript SDK](https://docs.traffical.io/sdks/javascript.md): Browser client SDK for framework-free apps and as the foundation for the React and Svelte SDKs. - [Node.js SDK](https://docs.traffical.io/sdks/node.md): Server-side SDK for Node.js and Bun — install, initialize, resolve parameters, track events. - [SDK overview](https://docs.traffical.io/sdks/overview.md): How Traffical SDKs work, what's available, and how to pick one. - [PHP SDK](https://docs.traffical.io/sdks/php.md): Server-side SDK for PHP 8.1+ — install, initialize, resolve parameters, track events, and flush PHP-FPM-aware. - [React SDK](https://docs.traffical.io/sdks/react.md): React provider and useTraffical hook for parameter resolution, event tracking, and SSR hydration. - [React Native SDK](https://docs.traffical.io/sdks/react-native.md): iOS and Android via React Native — cold-start strategy, AsyncStorage caching, device-info enrichment. - [SSR patterns](https://docs.traffical.io/sdks/ssr.md): Server-side rendering with SvelteKit, Next.js, and Remix — no flash of original content, no double-fetch on hydration. - [Svelte SDK](https://docs.traffical.io/sdks/svelte.md): Svelte 5 runes and SvelteKit integration for parameter resolution, event tracking, and SSR hydration. - [Agent Skill](https://docs.traffical.io/tools/agent-skill.md): Install the Traffical Agent Skill so your AI coding agent sets up Traffical, parametrizes your code, wires the SDK, and places events correctly — across Claude Code, Cursor, and 40+ other agents. - [CLI](https://docs.traffical.io/tools/cli.md): Log in, link a project, and sync parameters, events, and metrics between your repo and Traffical — config-as-code from the command line. - [Configuration file](https://docs.traffical.io/tools/config-file.md): The .traffical/ directory and the config.yaml, project.yaml, and metrics.yaml file formats — every field and option. - [DevTools](https://docs.traffical.io/tools/devtools.md): Inspect SDK state, current assignments, and exposure events live in your browser. - [MCP server](https://docs.traffical.io/tools/mcp-server.md): Connect AI agents to Traffical's read-only MCP server — check change status, read evidence and decision logs, preview transitions, and draft recommendations for humans to act on. - [Visual editor](https://docs.traffical.io/tools/visual-editor.md): Create A/B tests on live pages without writing code, using a browser bookmarklet. - [Why Traffical](https://docs.traffical.io/why-traffical.md): The parameter-first philosophy, the velocity-confidence gap, and how Traffical differs from feature flag tools. ## Optional - [Blog](https://traffical.io/vision) - [GitHub](https://github.com/traffical)