> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FullStory: Tag Setup, Validation, and FAQs

> Update your Invoca Tag to capture the FullStory Session ID, confirm events reach FullStory, and review the fields Invoca sends.

**Update your Invoca Tag to capture the FullStory Session ID, confirm that events reach FullStory, and review the data Invoca sends, for marketers and analysts who manage Invoca integrations.**

## Overview

FullStory uses the session ID that the Invoca Tag captures to attribute events to specific user sessions. The capture method depends on which FullStory implementation your site uses, v1 or v2. This article is Step 3 of the FullStory integration. Steps 1 and 2 are in the companion article [FullStory: Integration Guide](https://docs.invoca.com/s/article/fullstory-integration-guide.md).

## Before you begin

* You completed Steps 1 and 2 in [FullStory: Integration Guide](https://docs.invoca.com/s/article/fullstory-integration-guide.md): your **FullStory** account is connected in Invoca and you created at least one Action.
* Your Invoca Tag is deployed on your website.
* You know whether your site uses FullStory v1 or v2.

## Step 3: Update your Invoca Tag to capture the FullStory Session ID

Follow the procedure that matches your FullStory implementation.

### FullStory v1 implementations

For [FullStory v1 implementations](https://developer.fullstory.com/browser/v1/get-session-details/):

1. Click the **gear icon**, select **Invoca Tags**, then select your deployed Tag.
2. In the **Revision History** tab, create a **New Draft**.
3. In the **Marketing Data** section, find the **FullStory Session ID** (`fullstory_session_id`) field.
4. Confirm that the field is enabled and set to capture from the **Data Layer** (Data Source Type: **DataLayer**).
5. In the data source name field, enter `window.FS.getCurrentSession()`.
6. Test your Tag changes, then click **Save & Go Live**.
7. If you have multiple Invoca Tags for different websites, repeat these steps for each Tag.

### FullStory v2 implementations

For [FullStory v2 implementations](https://developer.fullstory.com/browser/get-session-details/):

1. Click the **gear icon**, select **Invoca Tags**, then select your deployed Tag.

2. In the **Revision History** tab, create a **New Draft**.

3. Scroll to the custom code block near the bottom of your Tag and paste the following code:

   ```javascript theme={null}
   // Listen for FullStory to start and securely capture the v2 session ID
   try {
     if (typeof window.FS === 'function') {
       window.FS('observe', {
         type: 'start',
         callback: function() {
           try {
             window.invoca_fs_session_id = window.FS('getSession', { format: 'id' });
           } catch (err) {
             console.error('Invoca-FullStory getSession Error:', err);
           }
         }
       });
     }
   } catch (error) {
     console.error('Invoca-FullStory Initialization Error:', error);
   }
   ```

   > **Note:** Check the formatting of your custom code block, especially if you have other JavaScript functions. Paste the code before a `return options;` line, and make sure `return options;` appears only once.

4. In the **Marketing Data** section, find the **FullStory Session ID** (`fullstory_session_id`) field.

5. Confirm that the field is enabled and set to capture from the **Data Layer** (Data Source Type: **DataLayer**).

6. In the data source name field, enter `window.invoca_fs_session_id`.

7. Test your Tag changes, then click **Save & Go Live**.

8. If you have multiple Invoca Tags for different websites, repeat these steps for each Tag.

## Handle script timing with Re-run attribution

If your Invoca Tag runs before the FullStory script loads on the page, the Tag cannot capture the session ID. To prevent this timing issue, edit your Invoca Tag and enable the **Re-run attribution** setting. A 5-second delay is a good starting point because it gives FullStory time to load before the Tag captures the ID.

## Validate that events reach FullStory

1. Go to **Integrations** > **Manage Integrations**.
2. Click the **FullStory** tile, then click the name of your configured Action.
3. Use the **Delivery Details** and **Delivery History** tabs to confirm that server-to-server requests return positive (green) responses.

## Frequently asked questions

### What fields does Invoca send to FullStory by default?

Invoca sends the following data for each event:

* FullStory Session ID, which links the event to the user's web session
* Event Name
* Event Timestamp
* Unique Interaction ID
* Duration in Seconds
* Interaction Type

> **Note:** You can also configure additional parameters to send as event properties when you set up your Action.


## Related topics

- [FullStory: Integration Guide](https://docs.invoca.com/s/article/fullstory-integration-guide.md)
- [ChatGPT Ads: Tag Setup, Validation, and FAQs](https://docs.invoca.com/s/article/chatgpt-ads-tag-setup-validation-faqs.md)
- [ChatGPT Ads: Integration Guide](https://docs.invoca.com/s/article/chatgpt-ads-integration-guide.md)
- [Piwik PRO: Setup & Overview](https://docs.invoca.com/s/article/piwik-setup-overview.md)
- [Segment: Setup & Overview](https://docs.invoca.com/s/article/segment-setup-overview.md)