Connect: Get Fullstory in Your Tech Stack

Who can use this feature?
- Available with all plans.
- Requires an Admin role.

Fullstory is most powerful when it's connected to the rest of your tech stack. Integrations let you bring context from your other tools into Fullstory—and push Fullstory insights out to the tools your team already lives in.

This article walks you through three foundational setup tasks that unlock Fullstory's integration capabilities and improve your Integration & API health score.

Task 1: Enable data layer capture

Your site's data layer is a structured JavaScript object (typically window.dataLayer) that your team uses to pass information between your site and tools like Google Tag Manager, analytics platforms, and ad tech. When Fullstory has access to it, you get richer context in your session data—without any additional instrumentation.

Why it matters: Data layer capture lets Fullstory surface the business context behind a session—things like cart values, plan tiers, or experiment variants—alongside what the user actually did. It's a low-effort way to dramatically increase the depth of your session data.

Steps

  1. Confirm with your engineering team that your site has an active data layer (e.g., window.dataLayer).
  2. In Fullstory, go to Settings > Anywhere > Data Layer.
  3. Toggle Enable Data Layer Capture to On.
  4. Optionally configure which specific data layer variables to capture.
  5. Click Save.
  6. Verify in a session replay that the data layer variables appear in the event timeline.

Further reading: Data Layer Capture

Task 2: Deploy one integration

Fullstory integrates directly with the tools your team already uses—including Segment, Amplitude, Mixpanel, Heap, Salesforce, Zendesk, Jira, Slack, and more. Integrations create a bridge: you can enrich session data with context from your CRM, or send Fullstory signals directly into your support tickets and product analytics.

Why it matters: Integrations multiply the value of Fullstory by connecting behavioral data to every other decision your team makes. A support ticket with a Fullstory session link is worth 10x a ticket without one.

Steps

  1. In Fullstory, go to Settings > Integrations > Manage.
  2. Browse the integration catalog and identify the tools your team currently uses.
  3. Click an integration to open its setup guide.
  4. Follow the integration-specific steps (most require an API key or OAuth connection).
  5. Test the integration to confirm data is flowing correctly.
  6. Repeat for each tool you want to connect.
Where to start: The most common first integrations are Segment (for event enrichment), Slack (for session sharing), and your CRM (Salesforce or HubSpot). Connect whichever ones your team will actually use.

Further reading: Supported integrations

Task 3: Set up user identification (FS.identify)

By default, Fullstory tracks anonymous sessions. When you implement FS.identify, you associate each session with a known user—linking sessions to a specific customer, their account, and any user properties your system tracks (plan tier, role, signup date, etc.).

Why it matters: User identification is what transforms Fullstory from a session recording tool into a customer insight platform. With it, you can look up a specific customer's sessions, segment by user attributes, and build cohorts based on who users are—not just what they clicked.

Steps

  1. Work with your engineering team to add the FS.identify call to your application code.
  2. The call should fire after a user logs in and include:
    • A unique user ID (e.g., your internal user ID or email).
    • Optional: custom user properties like displayName, email, planTier.
  3. Example implementation:

    FS.identify('user_12345', {
      displayName: 'Jane Smith',
      email: 'jane@example.com',
      planTier: 'pro'
    });
  4. Verify by checking a session in Fullstory and confirming the user's name and ID appear in the session details.

Further reading: Identifying users

What's next

If you haven't already, head to our Data Capture and Data Management articles to lay the foundations of your Fullstory data. If you've completed the tasks in all three articles, your team can now use reliable Fullstory session data anywhere—in support tickets, analytics tools, product planning, and more.

For a deeper dive into Fullstory's API capabilities, see the Fullstory Developer Guide.

Questions? Reach out to your Fullstory team or join us at Office Hours.


Was this article helpful?

Got Questions?

Get in touch with a Fullstory rep, ask the community or check out our developer documentation.