Skip to content

Commit 6ad528b

Browse files
estgcmarkzegarelli
andauthored
Adding 404 error info (#4125)
* Adding 404 error info Information taken from FullStory docs: https://help.fullstory.com/hc/en-us/articles/5079576446871-Server-Side-User-Properties#faqs * Update src/connections/destinations/catalog/actions-fullstory-cloud/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/destinations/catalog/actions-fullstory-cloud/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: markzegarelli <[email protected]>
1 parent c56a296 commit 6ad528b

File tree

1 file changed

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

1 file changed

+9
-1
lines changed

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

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,4 +44,12 @@ The FullStory cloud mode destination sends information about your users and rela
4444
> info ""
4545
> 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.
4646
47-
{% include components/actions-fields.html %}
47+
## Troubleshooting
48+
49+
### Why am I getting a ‘404 Not Found’ error?
50+
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.
52+
53+
Data sent server-side for users must match an already existing userId that was sent from a client-side connection.
54+
55+
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)