FullStory is a digital experience analytics platform that automatically captures every user interaction on your website or application — including clicks, scrolls, page transitions, and custom events — and reconstructs those sessions visually so teams can understand exactly how users experience their products. FullStory combines session replay, behavioral analytics, heatmaps, and funnel analysis into a single platform, enabling product, engineering, marketing, and customer success teams to diagnose UX issues, validate product decisions, and improve digital experiences with precision. Its Server API enables both ingestion of user and event data into FullStory and extraction of behavioral data, sessions, and user information for integration with external systems.
Power end-to-end data operations for your FullStory API with Nexla. Our bi-directional FullStory connector is purpose-built for FullStory, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to FullStory or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your FullStory workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to FullStory, you need a FullStory account with permission to create API keys. FullStory API keys are available to Standard, Architect, and Admin users on all FullStory plans. Architect-level keys — required for reading and exporting user data — are available on Enterprise plans only.
FullStory API keys use three permission levels that form a hierarchy: Standard → Architect → Admin. A key at a higher level can access all endpoints available to lower levels. Choose the permission level appropriate for your Nexla integration:
Standard — Allows sending data into FullStory (events and users), listing sessions, viewing recording settings, and managing async operations. Use this level when Nexla will only write data to FullStory.
Architect — Includes all Standard permissions, plus the ability to view, export, and delete user data, access privacy settings, search exports, and manage raw data exports. Use this level when Nexla will read or export data from FullStory. Available on Enterprise plans only.
Admin — Includes all Architect permissions, plus the ability to create, update, and delete element block rules that control what FullStory captures. Use this level only when required for privacy-critical configuration.
FullStory recommends using a separate API key for each integration or tool, and assigning only the minimum permission level required for the intended use. For details, see Managing API Keys in the FullStory Help Center.
Navigate to Settings (gear icon) in the left navigation.
Under the Integrations section, select API Keys.
Click the Create key button in the upper-right corner of the API Keys list.
Enter a descriptive name for the key in the Key name field — for example, Nexla Integration.
Select the appropriate permission level from the Permission level dropdown (Standard, Architect, or Admin) based on your intended use.
Click Create key to generate the API key.
Important
A modal will appear displaying the new key's value immediately after creation. You must copy the key value at this time — FullStory will not display the key value again after you close the modal. Store the key in a secure password manager or secrets management system.
Copy the API key value and keep it available for the next section.
If you need to revoke or regenerate a key at any time, return to Settings > Integrations > API Keys, locate the key in the list, and select the revoke option. After revoking a key, any integrations using that key will stop working until they are updated with a new key.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter the FullStory API key you generated in the Prerequisites steps above into the API Key field. This key authenticates all requests Nexla makes to the FullStory Server API and should be treated with the same security as a password.
The FullStory API key is sent in the Authorization HTTP header as Basic {YOUR_API_KEY} for every API request. Nexla handles this header formatting automatically — you only need to provide the raw API key value.
Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the FullStory connector tile, then select the credential that will be used to connect to the FullStory instance, and click Next; or, create a new FullStory credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common FullStory endpoints. Each template is designed specifically for the corresponding FullStory endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List Block Rules
Retrieves all recording block rules configured in the FullStory account. Use this endpoint to audit which CSS selectors or page elements are excluded from session capture.
Feature availability depends on your FullStory plan tier. No parameters are required.
List Session Targeting Rules
Retrieves all session targeting rules configured in FullStory, which determine which user sessions are captured based on criteria such as URL patterns or user attributes.
No parameters are required. Each returned rule includes its conditions and capture percentage settings.
List Webhooks
Retrieves all webhook endpoints configured in FullStory for receiving system event notifications, such as session recording or export completion events.
Configure the following parameters: User UID — filter by UID; Email — filter by email address; Limit — maximum number of results to return; Page Token — token for paginating through results.
All parameters are optional. To paginate through large result sets, use the page token returned in the previous response.
Get Segment
Retrieves segment information — including name, creator, and app URL — for a specific FullStory segment by its ID.
Configure the following parameter: User Id — the FullStory user ID for which to retrieve events.
Returns high-level indexed events (page views, clicks, errors) rather than raw interaction data. For complete raw event data, use the segment export workflow.
Get User Pages
Retrieves a user's visited pages including raw event data recorded on each page visit.
Configure the following parameters: Uid — filter sessions by user UID; Email — filter sessions by user email; Limit — maximum number of sessions to return.
At least one of Uid or Email is required. Session replay URLs are direct links to the FullStory session player.
List Segments
Retrieves a paginated list of all segments defined in your FullStory account, including segment names and creator information.
Configure the following parameters: Limit — maximum number of segments to return; Pagination Token — token for paginating through results.
Segment management and export features require an Enterprise plan. Use the returned segment IDs with the Get Segment or Get Export Results endpoints.
List Operations
Retrieves a paginated list of all operations — both ongoing and completed — for the FullStory account, useful for monitoring export or bulk processing jobs.
Configure the following parameters: Limit — maximum number of operations to return; State — filter by operation state (e.g., pending, complete); Type — filter by operation type.
All parameters are optional. Use this endpoint to monitor the status of all long-running jobs in your account.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
FullStory sources can also be manually configured to ingest data from any valid FullStory Server API endpoint not covered by the pre-built templates, including chained API calls or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The FullStory Server API uses https://api.fullstory.com as its base URL for all v2 endpoints. Common base URLs include https://api.fullstory.com/v2/users (users), https://api.fullstory.com/sessions/v2?email={user_email} (sessions for a user), https://api.fullstory.com/v2/sessions/{session_id}/events (session events), and https://api.fullstory.com/segments/v1 (segment exports, Enterprise only). Responses typically wrap records in a named array — for example, the Users API response wraps records in a users array, so specify $.users[*] as the path to data to treat each user record as an individual Nexla record. Additional request headers may be needed for API versioning or content type; the Authorization header is handled automatically based on your credential configuration.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new FullStory data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the FullStory destination, and select the Send to Destination option from the menu. Select the FullStory connector from the list of available destination connectors, then select the credential that will be used to connect to the FullStory organization, and click Next; or, create a new FullStory credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common FullStory endpoints. Select the endpoint to which this destination will send data from the Endpoint pulldown menu. Then, click on a template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create or Update User
Creates a new FullStory user or updates an existing user's profile data and custom properties by matching on the provided UID.
Sends a POST or PUT request to the FullStory Users v2 API with the user record payload.
Each record in the Nexset should include a uid field and a properties object containing custom user attributes.
If a user with the provided UID already exists, their profile will be updated. If no matching user is found, a new user record will be created.
Delete User
Deletes all data related to a FullStory user, including sessions, events, and custom properties, based on their UID.
Sends a DELETE request to the FullStory Users v2 API for the specified user.
Configure the following parameter: User UID — the UID of the user whose data should be permanently deleted.
This operation is irreversible. All session recordings, events, and custom properties for the user will be permanently removed. Requires an Architect-level API key.
Batch Create Users
Batch creates or updates up to 50,000 users in a single asynchronous import job, making it ideal for large-scale user data synchronization.
Enable record batching in the destination settings to send multiple user records per API call.
This endpoint is asynchronous — it returns a job ID that can be used with the Check Batch User Import Job Status source endpoint to monitor progress. Batches of up to 50,000 users are supported.
Create Event
Creates a single custom server-side event associated with a FullStory user or session, enabling server-side behavioral data to be included in session analysis.
Each event record should include a user identifier (uid or session) and event properties.
Server-side events are associated with existing FullStory sessions. Ensure the user or session referenced in the event payload exists in FullStory.
Create Batch Events Import Job
Creates a batch import job for multiple custom server-side events asynchronously, suitable for ingesting large volumes of historical or server-side event data.
Enable record batching to send multiple events per API call.
This endpoint processes events asynchronously. Use the Get Batch Events Imports source endpoint with the returned job ID to verify that events were successfully imported.
Create Webhook Endpoint
Creates a new FullStory webhook endpoint to receive system event notifications, such as export completion or recording events.
Each record should include the destination URL and the list of event types to subscribe to.
Use the List Event Types source endpoint to retrieve the available event types that can be included in a webhook subscription.
Update Webhook Endpoint
Updates an existing FullStory webhook endpoint, allowing you to change the destination URL or event subscriptions.
Sends a PUT or PATCH request to the FullStory webhook endpoint URL with the updated configuration.
Configure the following parameter: Id — the ID of the webhook endpoint to update.
The webhook endpoint ID is returned when the webhook is created and can also be retrieved via the List Webhooks source endpoint.
Delete Webhook Endpoint
Deletes an existing FullStory webhook endpoint, stopping delivery of system event notifications to the configured URL.
Sends a DELETE request to the FullStory webhook endpoint URL for the specified webhook.
Configure the following parameter: Id — the ID of the webhook endpoint to delete.
This action is irreversible. Once deleted, no further event notifications will be sent to the associated URL.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to send a test payload. The result will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the destination is configured correctly before saving.
FullStory destinations can also be manually configured to send data to any valid FullStory Server API endpoint — including user records, custom events, or batch data — to enrich your digital experience analytics with data from external systems. You can also configure Nexla to automatically send the response received from the FullStory API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The FullStory Server API accepts data in JSON format only. Common destination endpoints include https://api.fullstory.com/v2/users (create/update users, POST/PUT), https://api.fullstory.com/v2/users/batch (batch create users, POST, up to 50,000 users per asynchronous job), https://api.fullstory.com/v2/events (create custom events, POST), and https://api.fullstory.com/v2/events/batch (batch create events, POST). For update/upsert operations, include the ID of the object to be updated at the end of the URL. Each user record should include at minimum a uid field and a properties object containing custom attributes — see the FullStory Users API documentation for the full schema. FullStory's batch endpoints are designed to accept multiple records per request, making record batching an efficient way to send large volumes of user or event data. When sending JSON data, include a Content-Type:application/json request header.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to FullStory, open the destination resource menu, and select Activate.
The Nexset data will not be sent to FullStory until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
