Start here
Every SDK needs a project config in your repo —projectId, forms, experiments, and keys. Generate it locally with the Embeddables CLI (em login → em init), then import the generated config in your app. Do not assemble that object by hand.
Overview
SDKs are installable toolkits that connect a website or app to the Embeddables platform, each covering a single capability — visitor identity, event tracking, experimentation, form handling. This site covers installation, configuration, and usage for each one.Architecture
Every SDK is built around one shared foundation: Core resolves project and visitor identity once, and every other SDK reads that identity instead of resolving it independently. SDKs don’t depend on each other. If two capabilities need to work together — for example, an experiment assignment showing up as an analytics event — that connection is made explicitly in application code, not implicitly by the SDKs themselves. See each SDK’s own page for its specific integration points.Available tools
Core
Foundation — project and visitor identity
Analytics
Growth & Testing — event tracking
Experiments
Growth & Testing — A/B test assignment
Forms
Data Collection — form state, validation, and persistence
Key concepts
Project ID
Project ID
The unique identifier for an Embeddables project. Every SDK call is scoped to one project via
this value.
Publishable key
Publishable key
A key in the form
pk_live_... or pk_sandbox_... that authenticates requests from client-side
code. It is safe to expose publicly — it identifies a project, it does not grant elevated
access. Required by SDKs that call the Embeddables API, such as Analytics.em init prints sandbox and live keys for your project. You can also find them in the Embeddables admin under Settings → Portal / SDK — use the sandbox key (pk_sandbox_...) for development and the live key (pk_live_...) for production.Next steps
- Embeddables CLI — generate your project config
- Quickstart — install Core and make your first call