Connect FullStory¶

Connect FullStory to verify access to your segments and prepare session-based device, traffic-source and optional conversion data for Squoosh.

What the connection does¶

FullStory's Server API supplies raw event exports rather than aggregate traffic reports. The adapter can request a Segment Export, wait for completion, download it and reduce the rows to distinct sessions using both user and session IDs. Only aggregate counts and distributions are retained in a Squoosh snapshot.

A few sessions do not become a trusted audience distribution. Squoosh applies its shared minimum-sample checks before using any dimension for calibration.

Connect FullStory¶

You'll need an Admin or Architect API key and access to Segment Export. FullStory documents Segment Export as an Enterprise or Advanced plan add-on. A valid key alone does not prove that your plan can export.

1. In FullStory, open Settings → Integrations → API Keys → Create key.
2. Select the Admin or Architect permission level. A Standard key cannot run Segment Export. Use a durable admin account: keys stop working if their creating user is removed.
3. Copy the key when it is shown. FullStory shows the token only once. Keep any data-center prefix intact.
4. Prepare a traffic segment whose only event criterion is a page visit. Copy its ID from the segment URL, …/segments/<id>/…. Leaving the field blank uses the built-in everyone segment, which may create much larger exports.
5. Optionally prepare a conversion segment whose event criterion is your purchase or conversion event. It should describe the same traffic population. A segment based only on user properties does not establish that a conversion event occurred.
6. In Squoosh, open Integrations, choose FullStory, enter the API key and optional segment IDs, then click Connect.

Squoosh checks your key's permission level and segment access. Verification does not create an export or download visitor rows. It cannot verify the Segment Export add-on without requesting an export.

What Squoosh reads and never reads¶

• Verification reads the key's role and segment metadata. FullStory's identity response may also contain the account email; the adapter discards it.
• A traffic export requests UserId, SessionId, EventStart, PageDevice, PageRefererUrl and PageUrl. URLs can contain query parameters; they are processed in memory for channel grouping and are not stored in the snapshot.
• An optional conversion export requests only UserId, SessionId and EventStart. The segment name labels the conversion event.
• The adapter does not request recordings, replay content, user names, user emails, IP addresses, coordinates, page text or custom user variables in exports.
• The API key goes only to FullStory. Signed export files are fetched without the FullStory Authorization header. Neither the key nor signed download URLs are stored in snapshots.
• The connection does not send events, edit segments, delete data or change your FullStory settings. Export requests create temporary export jobs.

Limits and caveats¶

• No conversion segment means no conversion count or rate. A configured event segment with zero matching sessions produces a real zero. Sessions outside the selected traffic cohort are excluded and flagged.
• No automatic snapshot at this beta stage. The current connect route skips initial backfill for auth-stage connectors. A status check verifies access; it does not promise to finish an export from an earlier attempt.
• Exports can take minutes. Each snapshot attempt has one 45-second budget, including downloads. Pending operations are checked at least five seconds apart, at most eight times per export. Job IDs are not persisted across attempts, so retrying creates a new export.
• Quota discipline. FullStory documents two Segment Export requests per minute and a burst limit of 50. The connector declares a six-hour minimum refresh interval and stops immediately on rate limiting, reporting the supplied retry delay.
• Large exports fail visibly. The default local limits per export are 32 MiB for both downloaded and decompressed bytes, 250,000 rows and 100,000 distinct sessions. Squoosh rejects overflow rather than presenting a clipped distribution. Operators can configure these with FULLSTORY_MAX_BYTES, FULLSTORY_MAX_ROWS and FULLSTORY_MAX_SESSIONS.
• Individual HTTP requests time out after 10 seconds within the shared 45-second export budget.
• Wire behavior still needs live confirmation. NDJSON field casing, numeric identifier encoding, the navigation-event filter and the everyone segment's event scope remain unverified. Channel inference can also be weaker for single-page applications and scrubbed referrers.
• Warehouse alternative. Customers using FullStory Anywhere can expose a SQUOOSH_CALIBRATION view through an appropriate warehouse connector. FullStory's ready-to-analyze warehouse views include country information that Segment Export does not provide. Declare a consistent window and session population in that view.

Troubleshooting¶

Related¶

• FullStory API keys and authentication
• Managing API keys
• Segment Export API
• HTTP API: Using Segment Export
• Export fields
• Anywhere ready-to-analyze views
• Connect a CSV / Excel import