Skip to content

Commit a63d0a5

Browse files
Merge pull request #5056 from cowpaths/fullstory-v2-docs
Fullstory v2 docs
2 parents e22f7d8 + 797258a commit a63d0a5

File tree

1 file changed

+11
-2
lines changed
  • src/connections/destinations/catalog/actions-fullstory-cloud

1 file changed

+11
-2
lines changed

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

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,10 @@ FullStory’s cloud mode destination requires that you also use FullStory’s ta
2121

2222
The FullStory cloud mode destination sends information about your users and related events to FullStory. It uses [FullStory’s REST APIs](https://developer.fullstory.com){:target="_blank"}.
2323

24-
- **Identify User:** Converts Segment [Identify](/docs/connections/spec/identify/) calls to [FullStory Set User Properties API calls](https://developer.fullstory.com/set-user-properties){:target="_blank"}. Use this to set custom attributes which can be used to search and segment within FullStory.
24+
- **Identify User**: Converts Segment [Identify](/docs/connections/spec/identify/) calls to [FullStory Set User Properties API calls](https://developer.fullstory.com/set-user-properties){:target="_blank"}. Use this to set custom attributes which can be used to search and segment within FullStory.
2525
- **Track Custom Event**: Converts Segment [Track](/docs/connections/spec/track/) calls to [FullStory custom event API calls](https://developer.fullstory.com/server-events){:target="_blank"}. Use this to capture more context about your user’s experience on your site or to capture user’s actions in other applications to build a more complete understanding of your user’s overall experience.
26+
- **Identify User V2**: Converts Segment [Identify](/docs/connections/spec/identify/) calls to [FullStory Create User API calls](https://developer.fullstory.com/server/v2/users/create-user/){:target="_blank"}. Use this to upsert a user and their attributes which can be used to search and segment within FullStory.
27+
- **Track Custom Event V2**: Converts Segment [Track](/docs/connections/spec/track/) calls to [FullStory Create Event API calls](https://developer.fullstory.com/server/v2/events/create-events/){:target="_blank"}. Use this to capture more context about your user’s experience on your site or to capture user’s actions in other applications to build a more complete understanding of your user’s overall experience.
2628

2729
### Benefits of FullStory Cloud Mode (Actions)
2830

@@ -48,8 +50,15 @@ The FullStory cloud mode destination sends information about your users and rela
4850

4951
### Why am I getting a ‘404 Not Found’ error?
5052

51-
The user for which the API request is being made can not be found in the identified set of users within your FullStory organization. If you expect that user to already exist, you can search for that User ID in FullStory to confirm. Also, double check that you are using an API key from the same organization.
53+
If you are using the original 'Identify User' and 'Track Event' actions and encounter a "404 Not Found" error, the user for which the API request is being made can not be found in the identified set of users within your FullStory organization. If you expect that user to already exist, you can search for that User ID in FullStory to confirm. Also, double check that you are using an API key from the same organization.
5254

5355
Data sent server-side for users must match an already existing userId that was sent from a client-side connection.
5456

57+
The new 'Identify User V2' and 'Track Event V2' actions will automatically create users when a user matching the
58+
provided UID is not found.
59+
60+
### Why can't I propagate GDPR deletions?
61+
62+
GDPR deletions require an `Admin` or `API` key to propagate. You may also contact FullStory directly for deletions.
63+
5564
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)