Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.

FullStory

This documentation for the FullStory integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate FullStory, visit our connection instructions.

Version

This integration utilizes the FullStory API v1 and v2.

Base URL

The base URL used for all FullStory API endpoints:
https://api.fullstory.com/v2

Authentication & Authorization

The DataGrail FullStory integration connects using API key authentication which requires an API key.

Sensitive Credentials
Publicly exposing your API credentials can allow unauthorized access to FullStory API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Limits

Limits in FullStory are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

  • DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
  • DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

Capabilities

Access

DataGrail's FullStory integration provides Synchronous Access capabilities for the following supported identifier categories: Email and User ID.

Data Interactions

For Access requests, DataGrail will take the following actions:

  1. Get data about the user by application-specific ID using API version v1.
  2. Get users by application-specific ID or email using API version v2.
  3. Export the user's recorded events by the application-specific ID.
  4. Export a series of all pages that the user has visited, including the raw event data recorded on each page.
  5. Get a list of the user’s sessions using the application-specific ID or Data Subject email.

Endpoints Utilized

MethodEndpointPurposeDocs
GET/usersGet Users
GEThttps://api.fullstory.com/sessions/v2List Sessions
GEThttps://api.fullstory.com/users/v1/individual/USER_IDGet User
GEThttps://export.fullstory.com/api/v1/export/userEventsGet User Events
GEThttps://export.fullstory.com/api/v1/export/userPagesGet User Pages

Deletion

DataGrail's FullStory integration provides Asynchronous (Whole Record) Deletion capabilities for the following supported identifier categories: Email and User ID.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

  1. Get a user by the application-specific ID or Data Subject email using API version v2 to verify that the user is still found.
  2. Delete all user data related to a user identified by the FullStory user ID.
  3. Check the status of the deletion using the FullStory user ID to verify and confirm deletion.

Endpoints Utilized


 

Need help?
If you have any questions, please reach out to your dedicated Account Manager or contact us at support@datagrail.io.

Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.