> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/integrations/push-integrations/fullstory.md).
# FullStory
FullStory is a digital experience analytics platform that tracks how visitors interact with your website or app in order to optimize the customer experience.
The Fullstory push integration allows you to send the AB Tasty campaign data to Fullstory.
## Fullstory & AB Tasty
AB Tasty campaign data are sent as a custom event with event properties:
* Event name is “**abtasty**”
* Event parameter **abtasty\_campaign** contains the **Campaign ID** and **Campaign Name** formatted as **\[campaign\_id] campaign\_name**
* Event parameter **abtasty\_variation** contains the **Variation ID** and **Variation Name** formatted as **\[variation\_id] variation\_name**
The event is sent using the FS.event() method.
## Integration
1. Access **Integrations > Integration Hub**.
2. Search for and select **Fullstory**.
3. Click **Setup connector.**
4. Give a name to your connector so you can easily retrieve it.
5. \[Optional] Check the box to automatically add the connector to your future campaigns.
6. Click **Save and create connector.**
If you have checked the box, the connector will be automatically added to the Advanced step of your future campaigns. However, it is not applied retroactively to previously created campaigns.
If you left the box unchecked (default behavior), your connector won't be added automatically. You can still decide to send campaign data to your connector by selecting it from the *Advanced options* step of your campaign. More information on how to link a campaign is can be found in the [Advanced Options Step ](/web-experimentation-and-personalization/campaign-flow-advanced-options.md)article.
You can also modify this behavior from the Integration hub, by editing your connector configuration (check or uncheck box).
{% hint style="warning" %}
You must update the AB Tasty tag to make your changes live.
{% endhint %}
## Integration check
Once you have set up the integration and activated it in an AB Tasty campaign, you may want to verify that data is sent correctly to Fullstory.\
\
On the FullStory interface:
1. Access **Settings > Data Management > Events**
2. In the list of events you should see the event **“abtasty”,** click on it.
3. Under the property name, you should see “abtasty\_variation” and “abtasty\_variation”
More information on data management in the FullStory interface [here](https://help.fullstory.com/hc/en-us/articles/7331245227287-Data-Management-in-FullStory).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.abtasty.com/integrations/push-integrations/fullstory.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
1. Access **Integrations > Integration Hub**.
2. Search for and select **Fullstory**.
3. Click **Setup connector.**
4. Give a name to your connector so you can easily retrieve it.
5. \[Optional] Check the box to automatically add the connector to your future campaigns.
6. Click **Save and create connector.**
If you have checked the box, the connector will be automatically added to the Advanced step of your future campaigns. However, it is not applied retroactively to previously created campaigns.
If you left the box unchecked (default behavior), your connector won't be added automatically. You can still decide to send campaign data to your connector by selecting it from the *Advanced options* step of your campaign. More information on how to link a campaign is can be found in the [Advanced Options Step ](/web-experimentation-and-personalization/campaign-flow-advanced-options.md)article.
You can also modify this behavior from the Integration hub, by editing your connector configuration (check or uncheck box).
{% hint style="warning" %}
You must update the AB Tasty tag to make your changes live.
{% endhint %}
## Integration check
Once you have set up the integration and activated it in an AB Tasty campaign, you may want to verify that data is sent correctly to Fullstory.\
\
On the FullStory interface: