FullStory

Signal sends server-side custom events to FullStory’s Server API v2 (POST /v2/events). Session replay itself is recorded by FullStory’s browser snippet; Signal’s events are attached to the identified user and, when there is one, their session of the last 30 minutes.

FullStory needs a user or a session for every event. Signal sends the user ID as user.uid, which must be the same ID your site passes to FS.identify. Anonymous events are not sent.

Prerequisites

A FullStory API key (Settings > API Keys, Admin or Architect role).

Configuration fields

Field	Required	Description
`api_key`	Yes	Sent as `Authorization: Basic {api_key}` (the key itself, as FullStory documents).
`org_id`	No	Not used by the Server API.
`api_host`	No	Not used: `api.fullstory.com` routes to your account’s data centre (na1 or eu1) automatically.

API endpoint

POST https://api.fullstory.com/v2/events
Authorization: Basic {api_key}
Idempotency-Key: {Signal event ID}

{"name": "purchase", "timestamp": "2026-09-22T10:00:00Z",
 "user": {"uid": "crm-user-7"}, "session": {"use_most_recent": true},
 "context": {"browser": {"url": "https://www.example.com/checkout", "user_agent": "..."}, "location": {"ip_address": "203.0.113.7"}},
 "properties": {"transaction_id": "T-1001", "value": 104.5, "currency": "EUR", "item_ids": ["SKU-1", "SKU-2"], "item_names": ["Trail shoe", "Sock"]}}

FullStory does not accept arrays of objects in custom properties, so items[] becomes item_ids and item_names lists. Source: Create Event (read 2026-09-22).

Presets

Default (core cross-vertical events), Retail, Insurance, B2B / SaaS, Travel and Media & Streaming: each maps the vertical’s event-spec events with their documented properties under the Signal event name, plus page_view. No personal data is sent.

Default consent category: analytics.

Blueprint

Blueprint version 0.4.0 (not yet tested against a live FullStory org).

Firebase Glassbox