# FullStory Destination

## Destination Info

* Accepts [Identify](/docs/segment/connections/spec/identify) calls.
* Refer to it as **FullStory** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)

### Components

* [Browser](https://github.com/segment-integrations/analytics.js-integration-fullstory)

## Connection Modes

[Learn more about connection modes.](/docs/segment/connections/destinations/#connection-modes)

### Device-Mode

* web: yes
* mobile: no
* server: no

### Cloud-Mode

* web: no
* mobile: no
* server: no

> \[!NOTE]
>
> This page is about the FullStory Destination. See below for information about other versions of the FullStory destination:
>
> * [FullStory Device Mode (Actions)](/docs/segment/connections/destinations/catalog/actions-fullstory)
> * [FullStory Cloud Mode (Actions)](/docs/segment/connections/destinations/catalog/actions-fullstory-cloud)

> \[!WARNING]
>
> This destination is currently under maintenance. Please check back later or contact support.

[FullStory](https://www.fullstory.com/) lets product and support teams easily understand everything about the customer experience. The Segment integration for FullStory helps accurately identify your customers within the FullStory dashboard.

## Getting Started

1. From the Segment web app, click **Catalog**.
2. Search for "FullStory" in the Catalog, select it, and choose which of your sources to connect the destination to. Note the source must be sending events using our JavaScript library Analytics.js.
3. Add your `FS Org` in the destination settings. You can find this in FullStory by navigating to `Settings` > `General` > and copying the value found on the line `window['_fs_org'] = 'fullstory_org_here';`

Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading FullStory's recording snippet on your page and sending data.

## Identify

If you're not familiar with the Segment Specs, take a look to understand what the [identify method](/docs/segment/connections/spec/identify/) does. Identify calls sent to Segment will be transformed and sent to [FullStory's](https://help.fullstory.com/hc/en-us/articles/360020828113) `FS.identify` method.

An example call which does not include a `userId` will send FullStory the value of the `anonymousId` and would look like:

```javascript
analytics.identify();
```

If an `identify` call does contain a `userId`, that will be the ID sent along to FullStory.

```javascript
analytics.identify("userId");
```

In addition, Segment will send over along any traits included in the `identify` call. The example call below would send over both `plan` and `logins`.

```js
analytics.identify("userId123", {
  plan: "premium",
  logins: 5
});
```

### Specifying display name and email

Both `email` and `displayName` are special traits that will be passed to FullStory to be used in their interface as explained in [FullStory's docs](https://help.fullstory.com/hc/en-us/articles/360020828113). These traits are optional.

```js
analytics.identify("userId123", {
  email: "john.doe@example.com",
  displayName: "John Doe"
});
```

## Track

If you're not familiar with the Segment Specs, take a look to understand what the [track method](/docs/segment/connections/spec/track/) does. Track calls sent to Segment will be automatically passed directly to FullStory using [FullStory's](https://help.fullstory.com/hc/en-us/articles/360020623274) `FS.event` method, including all the properties passed in the event.

An example call would look like:

```js
analytics.track('Product Purchased', {
    order_ID: '2969302398',
    category: 'boots',
    product_name: 'yellow_cowboy_boots',
    price: 99.95,
    currency: 'EUR'
});
```

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field                    | Description                                                                                                                                                                                           | Required | Type    |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- |
| Enter FS debug mode      | This will enable FullStory's debug mode                                                                                                                                                               | No       | boolean |
| Capture only this iFrame | This will enable FullStory within an iframe.                                                                                                                                                          | No       | boolean |
| FS Org                   | You can find your \_fs\_org on the FullStory settings page by logging into your account, clicking the settings icon on the bottom left, and looking in the recording snippet for window\['\_fs\_org'] | Yes      | string  |
| Track All Pages          | Sends all page calls as tracking events to FullStory.                                                                                                                                                 | No       | boolean |
| Track Categorized Pages  | Sends pages that specify a category to Fullstory as tracking events.                                                                                                                                  | No       | boolean |
| Track Named Pages        | Sends pages with names to FullStory as tracking events.                                                                                                                                               | No       | boolean |