> 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/feature-experimentation-and-rollout/feature-experimentations-integrations/fullstory-feature-experimentation-integration/import-fullstory-audience-to-feature-experimentation.md).

# Import FullStory Audience to Feature Experimentation

The **FullStory integration** allows you to import your FullStory segments in Feature Experimentation (FE\&R) so you can target them with FE\&R campaigns.

{% hint style="warning" %}
**User ID requirement**

To make this user-matching flow work, you need to pass the same user ID to both FullStory and\
AB Tasty FE\&R.

What you must do

• Make sure FullStory receives a user ID\
• Use that same value as the AB TASTY FE\&R User ID\
• If the values don’t match, AB TASTY FE\&R won’t be able to target your FullStory segment

More info on the FE\&R User ID [here](https://docs.abtasty.com/server-side/concepts/universal-collect-1)\
More info on the FullStory User ID [here](https://help.fullstory.com/hc/en-us/articles/360020828113-Identifying-users)
{% endhint %}

This article will walk you through the different steps to setup the integration on FullStory side and to export your segments.

## Get a FullStory API Key <a href="#h_01habys64f1yg3z4rn01ybxptc" id="h_01habys64f1yg3z4rn01ybxptc"></a>

To enable the integration on Fulltory, follow the steps below:

### ![Screenshot\_2023-01-13\_at\_12.12.57\_\_1\_.png](/files/gnL52GA8C0nl1YF5G1us) <a href="#h_01fybjx66z0eg4nvdz4saqh74c" id="h_01fybjx66z0eg4nvdz4saqh74c"></a>

1. Access **Settings > Integrations > API Keys**
2. Click **“Create key”**
3. In the drawer that appeared, give a name to the API key you will create and give it the “Architect” permissions.
4. Click **“Save API Key”.**
5. Upon successful creation of a key, a modal will appear with the new key’s value. You must copy the value from this modal at this time. You will not be able to see the key value again. Copy the value, and save it in your preferred API key or password manager. This API key value will be used to activate the integration in FE\&R.

For further information on FullStory API keys, please refer to the [FullStory documentation](https://help.fullstory.com/hc/en-us/articles/360052021773-Managing-API-Keys).

<figure><img src="/files/xiSkNPDkC5qlxMAJ4cla" alt=""><figcaption></figcaption></figure>

To enable the integration on FE\&R, follow the steps below:

1. Access [**Settings > Integrations > Feature Experimentation Tab > Pull**](https://app2.abtasty.com/settings/integration/integration-hub?page=feature-experimentation)
2. Select **FullStory > Create**
3. Copy and paste the FullStory API key.
4. Click **“Create”** to finalize the integration.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentations-integrations/fullstory-feature-experimentation-integration/import-fullstory-audience-to-feature-experimentation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
