Skip to content

Commit 1f22b8e

Browse files
author
Miguel Campos
authored
Add updates to FullStory cloud mode destination docs (#3917)
* add updates to fullstory cloud mode destination docs (#2) * apply suggested code fix
1 parent be7ff6c commit 1f22b8e

File tree

1 file changed

+9
-6
lines changed
  • src/connections/destinations/catalog/actions-fullstory-cloud

1 file changed

+9
-6
lines changed

src/connections/destinations/catalog/actions-fullstory-cloud/index.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ versions:
1313

1414
[FullStory](https://www.fullstory.com/){:target="_blank"} lets product and support teams easily understand everything about the customer experience. The Segment integration for FullStory helps accurately identify your customers within FullStory.
1515

16-
FullStory’s cloud mode Segment integration allows you send user and event data to FullStory from your servers and Cloud Apps so that you apply it to your analysis throughout FullStory. For example, you could build a funnel to analyze drop-off of users who engaged with a certain marketing campaign.
16+
FullStory’s cloud mode Segment integration allows you to enrich FullStory data by sending user properties and events from your servers and Cloud Apps so that you apply it to your analysis throughout FullStory. For example, you could build a funnel to analyze drop-off of users who engaged with a certain marketing campaign.
1717

18-
If you want to use FullStory’s tagless autocapture, use the [FullStory Device Mode (Actions) web destination](/docs/connections/destinations/catalog/actions-fullstory/). However, if you want to capture custom user properties and events from other [server-side sources](/docs/connections/sources/#server) or [cloud apps](/docs/connections/sources/#cloud-apps), such as recurring subscription purchases, use this cloud mode destination.
18+
FullStory’s cloud mode destination requires that you also use FullStory’s tagless autocapture, available through the [FullStory Device Mode (Actions) web destination](/docs/connections/destinations/catalog/actions-fullstory/). However, if you want to enrich the autocapture data with custom user properties and events from other [server-side sources](/docs/connections/sources/#server) or [cloud apps](/docs/connections/sources/#cloud-apps), such as recurring subscription purchases, use this cloud mode destination.
1919

2020
### Overview
2121

@@ -26,19 +26,22 @@ The FullStory cloud mode destination sends information about your users and rela
2626

2727
### Benefits of FullStory Cloud Mode (Actions)
2828

29-
- Works with FullStory’s latest data capture APIs
29+
- Enrich autocapture data with FullStory’s latest data capture APIs
3030
- Ability to send custom events from new sources
3131
- Use [Destination Filters](/docs/connections/destinations/destination-filters/) to selectively send certain events or user properties to FullStory
3232

3333
### Getting Started
3434

3535
1. You need a FullStory API Key to use the FullStory cloud mode destination. Refer to [this article](https://help.fullstory.com/hc/en-us/articles/360052021773-Managing-API-Keys){:target="_blank"} to learn how to generate a new API Key within FullStory.
36-
2. From the Segment web app, click **Catalog**, then click **Destinations**.
36+
2. From the Segment web app, click **Catalog**, then click **Destinations**.
3737
3. Find “FullStory Cloud Mode (Actions)” in the Destinations list and click it.
38-
4. Click **Configure FullStory Cloud Mode (Actions)**.
38+
4. Click **Configure FullStory Cloud Mode (Actions)**.
3939
5. Select an existing Source to connect to FullStory Cloud Mode (Actions).
4040
6. Provide a Destination Name and select **Fill in settings manually.** Ensure the “Actions” destinations framework is selected and click **Save.**
4141
7. On the **Basic Settings** page, enter your FullStory API Key from step 1 and click **Save Changes**.
42-
8. On the **Mappings** tab, you can view default mappings as well as add, modify, or disable mappings.
42+
8. On the **Mappings** tab, you can view default mappings as well as add, modify, or disable mappings. Confirm that the "User ID" FullStory property is mapped to the ID previously used to identify the user. For more information, please refer to the [API documentation](https://developer.fullstory.com/server-events){:target="_blank"}.
43+
44+
> info ""
45+
> Events that you send through to FullStory through a Cloud-mode connection count towards your FullStory server event quota. To see your company’s current quota allotment, view the Subscription information on the Account Settings page in FullStory.
4346
4447
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)