Getting Started
Two ways to set up FunnelFizz. Pick whichever fits how you work.
A. Hand it to your agent (~5 min)
If you use Claude Code, Cursor, Windsurf, ChatGPT, or any other agent that supports the Model Context Protocol, your agent can do the entire setup. It calls real tools to register tracking sites, validate Stripe keys, OAuth providers, verify email senders, and wire everything to your funnel.
1. Add the FunnelFizz MCP server to your agent's config. Most agents support a JSON block like this:
{
"mcpServers": {
"funnelfizz": {
"type": "streamable-http",
"url": "https://mcp.funnelfizz.com",
"headers": { "Authorization": "Bearer ff_YOUR_KEY_HERE" }
}
}
}
Get your ff_… key from Settings → Developer. For Claude Desktop / Cursor / Windsurf one-click install URLs and the Claude Code variant, see MCP → Connecting.
2. Paste this prompt into your agent:
Connect to the FunnelFizz MCP server, then read
https://docs.funnelfizz.com/skill.md and follow it.
Stop and ask before anything destructive.
3. Answer the questions it asks (your domain, framework, whether you have Stripe). It writes the tracking snippet into your codebase, walks you through the Stripe key, kicks off provider OAuth, registers your sender domain, and instruments identify + custom events.
→ Full walkthrough: Setup with an agent. Reference: What MCP can do.
B. Do it yourself (~10 min)
The onboarding wizard walks you through these in order:
| # | Step | Time |
|---|---|---|
| 1 | Sign up and name your funnel | 30s |
| 2 | Install tracking | 2m |
| 3 | Connect Stripe | 2m |
| 4 | Connect providers | 2m each |
All four steps are quick, and each one unlocks a different piece of your funnel. Do all four to see the full picture.
What lights up when
Each setup step turns on a different part of your funnel. Here's what moves people from one stage to the next:
| Trigger | Moves them to |
|---|---|
| First impression on a connected social provider (X post, YouTube video, GSC search result) | AWARENESS |
| First pageview on your tracked site | CONSIDERATION (and they get a _fn_vid cookie that follows them across visits) |
Custom event you fire (funnelfizz('event', 'signup')), or a Stripe trial subscription starting | TRIAL |
Stripe subscription flips to active (paid) | CUSTOMER (with retained / upgraded / churned breakdown computed from their subscription state) |
Same userId seen on a second device after you call funnelfizz('identify', …) | Devices merge into one profile, all events roll up together |
Identity stitches automatically. Anonymous visitor cookies get linked to user IDs the moment you call identify, and to Stripe customers the moment they check out. One person, one timeline, end to end.
After launch
You'll land on the funnel canvas. From there: split traffic by UTM/device/country, add extensions to track upsells, wire stage-triggered email and automations, and ask your agent for weekly insights.
Stuck? FAQ or [email protected].