This article describes how to set up the FullStory tag in your Tag Management account.
Tag tips
- In the Advanced Settings, set the Bundle Flag to Yes and the Wait Flag to No to make FullStory start recording as soon as possible.
- Use mapping to:
- Send the User ID for identified users (
FS.identify). - Send additional user parameters (
FS.identifyandFS.setUserVars). - Send an event with parameters (
FS.event). - Override the Event Source (default is
tealium). - Enable FullStory debugging.
- Stop adding the FullStory Session ID to the data layer.
- Stop sending the Tealium Session ID to the
FS.identifyandFS.setUserVarsmethods. - Stop sending the Tealium Visitor ID to the
FS.identifyandFS.setUserVarsmethods.
- Send the User ID for identified users (
- Events send when a value is present in the Event Name variable.
- If a Full Event Object is present, none of the Individual Custom Event parameters are sent.
Tag configuration
Go to the tag marketplace to add a new tag. For more information, see About tags.
When adding the tag, configure the following settings:
- Org ID
- Your FullStory Org ID
- Namespace
- Your FullStory JavaScript namespace
Data mappings
Data mappings send values from data layer variables to the corresponding variables in the vendor tag. For more information, see About data mappings.
The available categories are:
Standard
| Variable | Description |
|---|---|
fs_debug |
|
get_fs_session_id |
|
get_tealium_session_id |
|
get_tealium_visitor_id |
|
fs_consent |
|
fs_script |
|
User Parameters
| Variable | Description |
|---|---|
uid |
|
uservars.displayName |
|
uservars.email |
|
uservars.custom |
|
Events
| Variable | Description |
|---|---|
fs_event_name |
|
fs_event_source |
|
s_event.custom |
|
fs_event_object |
|
Page Events
| Variable | Description |
|---|---|
fs_page.pageName |
|
fs_page.category |
|
fs_page.title |
|
fs_page.url |
|
fs_page.image_url |
|
fs_page.custom |
|
fs_page_object |
|
This page was last updated: November 10, 2026