Open dashboard
Sign in, create a site, and copy your ingest key.
Documentation
Create a site in the dashboard, embed the SDK and recorder, connect MCP for agent instrumentation, and activate events in Event Studio.
Browser SDK — events, consent, and data-insight-id helpers. Production ingest defaults to api.ftanalytics.app.
CLI that writes MCP config and catalog-first policy for Cursor, VS Code, Claude Code, or Devin.
Load the standalone recorder early, before React hydration, for session replay.
Apply airport booking funnel templates from the dashboard for checkout flows.
Connect Cursor, VS Code, Claude Code, or any MCP client for LESP authoring and session analysis.
lesp_get_glossary → lesp_propose_event → lesp_create_event → lesp_validate_event.
Generate data-insight-id tags and track() calls from Event Studio.
Load the recorder early, then initialize the SDK with your site ingest key. Semantic events must be registered in Event Studio before track() calls in strict mode.
<!-- Early replay capture (before React) -->
<script src="https://api.ftanalytics.app/v1/static/recorder/loader.v1.js" async></script>
<!-- SDK (after consent gate) -->
<script type="module">
import { init, syncConsent } from "@ft-analytics/analytics-sdk";
init({
ingestKey: "YOUR_INGEST_KEY",
strictEventCatalog: true,
});
syncConsent();
</script>MCP endpoint (Cursor, VS Code, Claude Code, or any MCP client): https://mcp.ftanalytics.app