Skip to main content

FullStory Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a FullStory location.
fullstory_api.png

FullStory

  1. Click the + icon on the Nexset that will be sent to the FullStory destination, and select the Send to Destination option from the menu.

  2. 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.

  3. In Nexla, FullStory destinations can be created using pre-built endpoint templates, which expedite destination setup for common FullStory endpoints. Each template is designed specifically for the corresponding FullStory endpoint, making destination setup easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    FullStory destinations can also be configured manually, allowing you to send data to FullStory endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common FullStory endpoints. Each template is designed specifically for the corresponding FullStory endpoint, making destination setup easy and efficient.

Endpoint Settings​

  • Select the endpoint to which this destination will send data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your destination for this endpoint.

    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.

    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.

    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.

    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.

    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.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can send a test payload to verify the destination is configured correctly.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. A test payload will be sent and the result will be displayed in the Endpoint Test Result panel on the right.

  • If the test result is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again to verify the updated configuration.

Configure Manually​

FullStory destinations can also be manually configured to send data to any valid FullStory Server API endpoint. Using the FullStory destination, you can send user records, custom events, or batch data into FullStory 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.

First, select the API method that will be used for calls to the FullStory API from the Method pulldown menu. Common methods for sending data to FullStory include:

  • POST: For creating new users, sending custom events, or initiating batch imports
  • PUT: For updating existing user records or overwriting user properties
  • PATCH: For partially updating user properties without replacing the full record
  • DELETE: For removing user data (requires Architect-level API key)

Data Format​

  1. Select the format in which the Nexset data will be sent to the FullStory API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call.

    The FullStory Server API accepts data in JSON format. Select JSON from the Content Format menu to ensure that data is correctly formatted for FullStory API endpoints.

API Endpoint URL​

  1. Enter the URL of the FullStory API endpoint to which you want to send the Nexset data in the URL field. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

    Common FullStory Server API destination endpoints include:

    • Create/update users: https://api.fullstory.com/v2/users (POST/PUT)
    • Batch create users: https://api.fullstory.com/v2/users/batch (POST) — for importing large numbers of user records efficiently
    • Create custom events: https://api.fullstory.com/v2/events (POST)
    • Batch create events: https://api.fullstory.com/v2/events/batch (POST) — for sending multiple events in a single API call

    When sending data to FullStory's user endpoints, each record in your Nexset should contain at minimum a uid field (FullStory's user identifier) and a properties object containing any custom user attributes. Refer to the FullStory Users API documentation for the full schema.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    For FullStory API calls, you may need to include:

    • Content-Type:application/json — required for POST and PUT requests that send JSON data

    You do not need to include the Authorization header here — it is automatically handled by Nexla using the API key configured in your FullStory credential.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this FullStory destination, select the attributes from the Exclude Attributes pulldown menu. This is useful when your Nexset contains internal tracking fields, intermediate processing columns, or other attributes that should not be sent to FullStory.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

    FullStory's batch import endpoints (/v2/users/batch and /v2/events/batch) are specifically designed to accept multiple records in a single request, making record batching an efficient approach for sending large volumes of user or event data.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings — click on an algorithm listed below to view instructions for configuring these settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the FullStory API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call, such as FullStory job IDs for async batch operations.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the FullStory API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing​

After all endpoint settings have been configured, Nexla can send a test payload to the FullStory API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the FullStory API using the current settings.

Save & Activate the Destination​

  • 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.