For the complete documentation index, see llms.txt. This page is also available as Markdown.

19. Integrations

FullSession connects to a handful of third-party tools so your session data shows up where your team already works — in support conversations, your CRM, your experimentation tool, and automation platforms. Integrations are managed under Settings → Integrations.

Integrations are a Growth+ feature governed by the integrations:view, integrations:create, and integrations:delete permissions ([Chapter 16 — Team & Account Management]).

FullSession Integrations panel showing Intercom, HubSpot, Optimizely, Shopify, and Zapier connections configured per site.

19.1 Integrations Overview

FullSession offers a focused set of integrations. Here's the lay of the land before the per-tool details:

Integration
What it does
How it connects

Intercom

Surfaces session recordings in your support tooling

OAuth

HubSpot

Puts recordings in the HubSpot contact timeline; powers lists/automations

OAuth

Optimizely

Turns A/B experiment data into session attributes you can filter and segment by

One-click (no login)

Shopify

Connects your store via credentials

Store credentials

Zapier

Links FullSession to thousands of apps via prebuilt Zaps

Opens Zapier

Connecting is per-site

Integrations are connected per site. If you track several sites, you connect (or disconnect) each one independently — the panel has a site selector, and each site shows its own status.

Connect / disconnect mechanics

  • OAuth integrations (Intercom, HubSpot): click Connect, authorize FullSession in the provider's window, and you're returned with the integration active.

  • Optimizely: a single Connect click — no login required.

  • Disconnect: click Disconnect and confirm; the connection (and its stored credentials) is removed.

To update credentials, reconnect. There's no "edit credentials" screen — if a connection needs refreshing, disconnect and connect again, which runs a fresh authorization.

Status

Each integration shows whether it's connected for a site. A Connected badge appears when at least one of your sites has it enabled. For your security, the access tokens behind a connection are never shown back in the app.


19.2 Intercom

The Intercom integration links your support conversations to FullSession recordings, so your team can watch what a customer actually did.

FullSession Intercom integration setup showing authorization to connect Intercom and display session recordings alongside conversations.

What it does

  • "Access session recordings directly from your Intercom conversations."

  • Enriches support interactions with FullSession behavior data.

Where it surfaces — the player

Once Intercom is connected, the session player's visitor info panel shows a View in Intercom link for any identified visitor with an email ([Chapter 6, section 6.6]). One click opens that person's Intercom profile, connecting the replay you're watching to your support history with them.

Setup

Click Connect on the Intercom card, authorize FullSession in Intercom, and the link appears in the player for matching visitors.


19.3 HubSpot

The HubSpot integration brings FullSession recordings and properties into your CRM.

FullSession HubSpot integration card showing connection setup, session recordings in contact timelines, and list creation from FullSession properties.

What it does

  • "View session recordings directly in your HubSpot contact timeline."

  • "Utilize FullSession session properties to create lists and activate automations."

This lets your sales and success teams see a contact's recorded behavior right where they manage the relationship, and use FullSession signals to drive HubSpot lists and workflows.

Setup

Click Connect on the HubSpot card and authorize FullSession in HubSpot. The connection is per site (connect each site you want represented in HubSpot).


19.4 Optimizely

The Optimizely integration makes your A/B testing data available throughout FullSession, so you can analyze sessions by experiment.

FullSession Optimizely integration card showing one-click connection and experiment or variation data mapped into session attributes.

What it does

  • "Use Optimizely experiments as attributes to segment users."

  • Translates experiment variations into session attributes, so you can compare how variants behave and how they affect conversion.

Where it surfaces — filters & segments

Once connected, four Optimizely fields become available in the Sessions and Segment filters (Chapters 5 & 11):

Filter

Opt. Experiment ID

The experiment identifier

Opt. Experiment Name

The experiment name

Opt. Variation ID

The variation identifier

Opt. Variation Name

The variation name

This lets you build a segment like "users in the checkout-redesign experiment, variation B" and analyze their sessions, heatmaps, and funnels.

Setup

Optimizely requires no login — click Connect and it's enabled. Experiment data then flows into the filters above.

FullSession segment builder showing Optimizely variation data used to compare behavior across different experiment test arms.

19.5 Zapier

The Zapier integration connects FullSession to thousands of apps through prebuilt automations — "Automate workflows by connecting FullSession with thousands of apps."

FullSession Zapier integration page showing prebuilt Zaps triggered when a new recording is created.

How it works

The Integrations panel's Zapier section is a discovery page: it lists ready-made Zaps and links you out to Zapier to set them up. The featured workflows all trigger when a new recording is created, and include:

Zap
Does

Google Sheets

Add a row when a new recording is created

Microsoft Excel

Add a row when a new recording is created

Intercom (via Zapier)

Create an Intercom conversation

Trello

Create a Trello card

Gmail

Send an email

Jira

Create a Jira issue

Clicking a card opens the corresponding Zap on Zapier.com, where you complete the connection.

Zapier shows up in two places. Here, as prebuilt recording-triggered Zaps; and in Alerts ([Chapter 15, section 15.4]), where an alert can send to a Zapier hook. They're separate uses of Zapier.


19.6 What Integrations Don't Include

To set expectations clearly, the following don't exist as native integrations:

  • No standalone Slack integration. Slack is available only via Alerts — paste a Slack webhook URL when creating an alert ([Chapter 15, section 15.4]). There's no Slack card in the Integrations panel.

  • No generic/custom webhook integration. Outbound webhooks exist only through Zapier and the Slack alert hook — there's no "add your own webhook URL" integration.

  • No native Jira, Google Analytics, Segment, or Salesforce integrations. (Jira is reachable through the Zapier Zap above.)

  • No integration marketplace beyond the Zapier discovery list, and no "coming soon" catalog.

Integrations vs. the API

Integrations connect FullSession to specific third-party tools. For programmatic access to your FullSession data, use API tokens instead — a separate feature under Settings → API Tokens, covered in [Chapter 20 — API & Developer Tools].

The big picture — FullSession integrates natively with Intercom (recordings in support) and HubSpot (recordings in the CRM timeline) via OAuth, Optimizely (experiment data as filterable session attributes) with one click, and Shopify via store credentials — all per site. Zapier links FullSession to many more apps through prebuilt, recording-triggered Zaps. There's no standalone Slack integration (it lives in Alerts), no custom-webhook builder, and no native Jira/GA/Segment/Salesforce — and programmatic access is handled by API tokens, not integrations.


Next up: [Chapter 20 — API & Developer Tools] covers API tokens and programmatic access to your FullSession data — the developer counterpart to the integrations in this chapter.

Last updated

Was this helpful?