Integrations

FullStory

Connect FullStory to find users and sessions, summarize what people did, run metrics and funnels, send events, and export segments.

You paste one value into PopMCP: a FullStory API key, made under Settings, then Integrations, then API Keys. PopMCP reads your organization and the key's level from it. A key belongs to one organization, and FullStory shows it only once.

Setup time
1 min
Auth
API credentials
API base URL
https://api.fullstory.com
Rate limits
FullStory limits requests per second with short bursts, and answers 429 with Retry-After. It does not publish the numbers for its Server API. Its AI tools allow 3 requests per second per organization per endpoint, with bursts up to 20.

Before you begin

  • A FullStory account
  • An Admin role to make an Admin key, or an Architect role to make an Architect key. A Standard role can make a Standard key
  • For metrics, funnels and session review: StoryAI turned on by an Admin

Get your credentials

Open the API Keys page

Sign in to FullStory. If you normally sign in at app.eu1.fullstory.com, use that address. Open Settings, then Integrations, then API Keys.

Open this screen →

Create a key

Click Create key and enter a name such as PopMCP. Choose a Permission level. Admin lets every tool work. Architect reads user details, session events and exports, and needs an Enterprise plan. Standard sends data and lists sessions. You can only choose your own level or lower. Save the key.

Open this screen →

app.fullstory.com/ui/acme/settings/apikeys
Acme Inc
Settings / Integrations / API Keys

API Keys

Create key
Name
PopMCP
Permission level
Admin
Save

This view is a simplified sketch: the labels on your page may differ slightly.

Copy the key

FullStory shows the key only once, so copy it now. It starts with your data center, like na1. or eu1..

Open this screen →

app.fullstory.com/ui/acme/settings/apikeys
Acme Inc
Settings / Integrations / API Keys

API Keys

PopMCP
Key
na1.a1b2****e5f6
Copy
You will not be able to see this key again.

Connect in PopMCP

Paste the key into PopMCP's FullStory form and click Connect. That is all PopMCP needs: it finds your organization and data center from the key.

Open this screen →

Turn on metrics and funnels (optional)

Metrics, funnels, journeys and session review come from FullStory's own AI tools. If PopMCP says they are off, an Admin opens Settings, then Account Management, then StoryAI Features, and turns on StoryAI and the Model Context Protocol switch. Everything else works without this.

Open this screen →

app.fullstory.com/ui/acme/settings/storyai
Acme Inc
Settings / Account Management / StoryAI Features

StoryAI Features

StoryAI
On
Model Context Protocol
On

This view is a simplified sketch: the labels on your page may differ slightly.

Connect in PopMCP

Open your workspace, choose FullStory in the marketplace, and fill in the connect dialog:

FieldWhat to enter
API keysecretIn FullStory open Settings, then Integrations, then API Keys, and click Create key. FullStory shows the key once. Stored encrypted and used only on our servers.Encrypted with AES-256-GCM on save and never shown again.

PopMCP verifies the credential against FullStory immediately. On success the connection flips to Verified and its MCP tools are provisioned.

Verify it worked

PopMCP shows the FullStory connector as Connected, named after your organization. It reads your organization and the key's level from FullStory, then checks whether FullStory's AI tools answer. A note says when the key's level or StoryAI will limit what your AI can do, and the connection stays.

Troubleshooting

FullStory did not accept this API key

Why: The key was cut short or copied with something extra, or it has been deleted.

Fix: FullStory shows a key only once, so make a new one under Settings, then Integrations, then API Keys, and paste it.

A tool says it usually needs an Architect or Admin key

Why: The key's level is too low for that tool.

Fix: Make a key with a higher level and connect again. Only an Admin can make an Admin key, and Architect keys need an Enterprise plan.

Metrics are off, or no analytics tools are offered

Why: StoryAI or its Model Context Protocol switch is off for your account.

Fix: Ask an Admin to turn both on at Settings, then Account Management, then StoryAI Features.

An export is refused

Why: Segment Export is an add-on on Enterprise and Advanced plans, and it needs an Architect or Admin key.

Fix: Ask FullStory about the add-on, and check the key's level.

Session events or summaries are refused

Why: The Sessions API is part of Anywhere: Activation and is counted against an Activation quota.

Fix: Check your FullStory plan and quota. Finding a person and listing their sessions still works.

FullStory answers 429

Why: Too many requests at once, or this period's server event quota is used up.

Fix: Wait and try again. Ask your AI to check the FullStory quotas to see which it is.

Reference

On this page