- TELEMETRY
- ANALYSIS
- AUDIT
- HUMAN
Short answer
How can I send backend events using my AI?
Your AI uses the FullStory MCP to call the create_event tool whenever a specific backend condition is met. This sends telemetry directly to your FullStory dashboard to enrich user sessions with server-side data. You'll see the breakdown of how this works below.
The results.
Where your data lands.
The AI handles the event creation so your telemetry stays accurate.
TELEMETRY
Enriched user sessions
The AI sends the event via create_event. Your FullStory dashboard now includes backend data alongside browser interactions.
ANALYSIS
Complete user journeys
Because the AI triggers these events, you can map server-side logic to specific user sessions without manual code changes.
AUDIT
Verified event logs
Every event triggered by your agent is logged in FullStory. You can verify exactly when the AI decided to fire a specific event.
HUMAN
Manual review needed
The AI won't change your existing FullStory configuration. You still need to check your dashboard to confirm the data looks right.
The workflow
What your AI does when an event is triggered.
The AI acts as the bridge between your logic and your telemetry provider.
Identify the trigger
Your agent recognizes a specific state or user action that requires a backend event.
create_eventFormat the payload
The AI structures the event properties and user identifiers to match your FullStory schema.
create_eventExecute the event
The AI calls the specific tool to push the data to your FullStory account.
create_eventConfirm delivery
The AI verifies the tool execution was successful before moving to the next task.
create_event
Try it
Copy these to start.
Use these prompts to begin sending data to FullStory.
Starting points
These are basic ways to start. Swap out the specific event names or user IDs for your actual data.
FullStory Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_JUUCyNnUSrqZlTvYnLFVd8WQHuMjFZOwjQQP8NY8/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — FullStory capabilities are ready to use.
{
"mcpServers": {
"fullstory-mcp": {
"url": "https://edge.vinkius.com/vk_preview_JUUCyNnUSrqZlTvYnLFVd8WQHuMjFZOwjQQP8NY8/mcp"
}
}
}Send a FullStory event named 'order_processed' for user ID 12345.
Trigger a custom event in FullStory when the subscription status changes to 'active'.
Create a FullStory event for the 'checkout_complete' action with a total_price property.
Log a backend event to FullStory whenever a user hits the payment gateway.
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect FullStory once, then ask.
Just link your account once. Your credentials stay encrypted, and you can start triggering events immediately through your AI client.
Connect FullStory to your AIFAQ
How this task behaves.
- 01
Can the AI delete existing FullStory events?
No. The AI only has the ability to create new events.
- 02
Will the AI change my FullStory dashboard settings?
No. The AI can only send data to the dashboard, not modify your account configuration or settings.
- 03
Does the AI need my FullStory password?
No. You connect via the Vinkius platform, which keeps your login credentials encrypted and secure.
- 04
Can I send multiple properties with one event?
Yes. You can instruct the AI to include various properties in the event payload.
- 05
Can the AI capture mouse movements?
No. This MCP is for backend telemetry. Mouse movements and browser-side interactions are captured by the standard FullStory browser script.
More questions about FullStory? The Connector page answers them. See everything the FullStory Connector can do
Connect FullStory to Claude, Cursor, ChatGPT & more
