--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-fullsession#article headline: FullSession (Actions) Destination description: Connect Segment to the FullSession (Actions) Destination to identify customers and capture user behavior analytics in the FullSession dashboard. url: https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-fullsession inLanguage: en dateModified: 2026-06-10T17:19:57.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # FullSession (Actions) Destination > \[!IMPORTANT] > > This feature is in active development and may change before general availability. ## Destination Info * Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **FullSession** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This destination is not compatible with [Destination Insert Functions.](/docs/segment/connections/functions/insert-functions/) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** [FullSession](https://fullsession.io/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) provides user behavior analytics software that helps you visualize all user interactions, analyze trends and patterns with laser precision, and optimize your website for peak performance. The Segment integration for FullSession helps accurately identify your customers and track their behavior within the FullSession dashboard. This destination is maintained by FullSession. For any issues with the destination, [contact the FullSession support team](mailto:support@fullsession.com). ## Getting started To connect the FullSession (Actions) destination: 1. From your workspace's [Destination Catalog](https://app.segment.com/goto-my-workspace/destinations/catalog), search for **"FullSession"**. 2. Select **FullSession**, then click **Add Destination**. 3. Choose an existing **JavaScript Source** to connect with FullSession (Actions). 4. Navigate to the [FullSession Setup](https://app.fullsession.io/settings/setup) page and copy your **Customer ID**, beginning with `cus_`. 5. Paste the **Customer ID** into the **FullSession Destination settings** in Segment. 6. Before enabling the destination, go to the **Mappings** tab and configure the mappings to ensure the correct data is captured. 7. Once your mappings are configured and enabled, go to the **Settings** tab and enable the destination. Segment then automatically loads the **FullSession recording snippet** in the user's browser. ## Destination Settings | Field | Description | Required | Type | | ----------- | ---------------------------------------------------------------------------------------------- | -------- | ------ | | Customer ID | Your FullSession Customer ID. You can find this in your FullSession dashboard under Settings . | Yes | string | ## Available Presets FullSession has the following presets | Preset Name | Trigger | Default Action | | ------------- | ----------------------- | -------------- | | Visit Page | Event type = "page" | Page View | | Record Event | Event type = "track" | Track Event | | Identify User | Event type = "identify" | Identify User | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following FullSession-supported actions: > \[!NOTE] > > Individual destination instances support a maximum of 5 mappings. * [Page View](#page-view) * [Identify User](#identify-user-4) * [Track Event](#track-event-7) ### Page View Track page views and set page-specific attributes in FullSession for navigation analysis. Page View is a **Web** action. The default Trigger is `type = "page"` | Field | Description | Required | Type | | --------------- | ------------------------------------------------------------- | -------- | ------ | | Page Properties | Properties and metadata associated with the page being viewed | No | OBJECT | ### Identify User Identify users and set their properties in FullSession. Identify User is a **Web** action. The default Trigger is `type = "identify"` | Field | Description | Required | Type | | ------------ | ------------------------------------------------------------- | -------- | ------ | | User ID | The user's unique identifier. | No | STRING | | Anonymous ID | The user's anonymous identifier when no user ID is available. | No | STRING | | User Traits | User traits and properties to be sent to FullSession. | No | OBJECT | ### Track Event Track custom events and user interactions in FullSession for behavioral analysis. Track Event is a **Web** action. The default Trigger is `type = "track"` | Field | Description | Required | Type | | ---------------- | ------------------------------------------------------------- | -------- | ------ | | Event Name | The name of the event being tracked. | Yes | STRING | | Event Properties | Additional properties and metadata associated with the event. | No | OBJECT | ## Settings Segment lets you change these destination settings from the Segment app without having to touch any code. | Field | Description | Required | Type | | ----------- | ---------------------------------------------------------------------------------------------- | -------- | ------ | | Customer ID | Your FullSession Customer ID. You can find this in your FullSession dashboard under Settings . | Yes | string |