Replay Creation

Record clips based on user attributes or event triggering to see how specific users experience your product.

Create a Replay

Create a standalone Replay

  1. Click + New Study and at top of page, click New Replay
  2. Name your Replay and add it to a specific study folder if desired.
  3. Select a Delivery Platform. You can trigger Replays on your Website or Web App, with Mobile delivery available soon.
  4. Click into Targeting module and set the desired clip timing to X seconds before or after your trigger. Also set your event trigger and any additional filters to ensure you are capturing clips from the right users at the right time in their product experience.
  5. Update Clip Settings to configure how many recordings you wish to capture.
  6. Update Recontact Options to set user-level clip limits and override any global recontact settings.
  7. Click Launch Replay!

Add a Replay to an In-product Survey

  1. Click + New Study, and select a survey template that matches your goal. You can also click New Survey at top of page to start from scratch.
  2. Customize your survey in the Questions tab to ensure you're getting the right feedback from respondents.
  3. Go to the Audience tab and select Website or Web App as your Delivery Platform (mobile is coming soon). You’ll see an Add Replay module pop up below.
  4. Set Targeting module to determine which triggers and filters you'd like to use to reach the right audience for your Survey/Replay.
  5. Click the toggle button on right side of the Add Replay module and customize the clip timing to X seconds before or after your trigger.
  6. Update the Recontact and Response Options to capture the desired number of responses/clips.
  7. Click Launch Survey!

Clip Playback

Sprig Replays playback modal works similarly to other familiar video playback products with some key features identified below:

Sprig Replays Playback Modal

Sprig Replays Playback Modal

  1. Emails in Sidebar: Emails are swapped in for Sprig User IDs when sent to Sprig
  2. Avatars and Checks in Sidebar: Avatars will be swapped for checkbox when a clip is viewed - only for the Sprig user playing the clip (other users will have clips marked as 'unwatched' until they view the clip)
  3. Total Number of User Sessions: "Session" is defined as any activity within a 12 hr period where a user had information sent to Sprig
  4. Clip Metadata:
    1. Number of clicks: Number of mouse clicks taken by a user during the session, useful for gauging relative activity of a user
    2. Pages visited: Number of distinct URLs visited within the duration of the replay clip
    3. Platform: mobile web or desktop
  5. Share Clip: Copy clip URL for entire clip or at particular timestamp
  6. Survey Results Tab: Visible when an In-product Survey w/ Replay
  7. Interactions Tab: Display of all clicks a user takes in a session, events that are sent to Sprig, and survey interactions
  8. Skip Inactivity Toggle: When ON, clip will auto-fast forward through periods of clip inactivity (no mouse movement or event triggering) greater than 10s


Sprig's Approach to Privacy

Sprig's entire application was built with Privacy as a top priority - including Replays.

While a replay clip may look and feel like a screen recording, Sprig's Session Replay clips are not actual “screen” recordings. Instead they are recordings of changes in the web browser's Document Object Model (DOM), which is the data representation of the page. That record of changes is then constructed into a video that represents a users interactions with a particular page. This approach allows us to selectively capture data, such as user interactions and form contents, while redacting other data, such as images and password fields.

By default, all form contents (including password fields) are not recorded or stored. Additionally, users are able to hide specific CSS selectors as they wish. Configure privacy settings at Settings > Replays > User privacy. Additionally, an Admin can turn off replays for the whole workspace, or by Product at Settings > Replay > Configure.


In addition to HTML content, Sprig Replays also record user interactions, such as mouse movements, clicks, screen touches, and keyboard input. Mouse movement captures are approximated during clip playback, limited to an inferred path between start and target destinations.


In adherence to guidelines set by the California Consumer Privacy Act (CCPA), Replays does not capture nor require capturing permissions from end-users. The CCPA mandates that businesses must disclose their practices related to both the collection and sale of consumers' personal information in their privacy policies. While businesses are required to give consumers the option to opt-out of having their personal information sold to third parties, the law does not oblige them to provide a similar opt-out for just the collection of personal information.

View more information on Sprig's Privacy Policy: here

We welcome feedback on our privacy practices. Please contact us at [email protected] if you have any questions or concerns.


Session Replay has been designed to use as little resources as possible. We break down performance into 4 categories: CPU, Memory, Disk and Network


We utilize the MutationObserver API to keep track of DOM changes. MutationObserver batches node changes and dispatches a joint notification which minimizes compute. These events should have very little impact on Javascript’s single-threaded performance.


Session Replay data has near zero impact on memory usage for modern web applications. Sprig immediately moves any data to IndexedDB to keep memory usage low and to persist replay across page loads.


As mentioned in the section above, Sprig uses IndexedDB to store and retrieve Session Replay data. Sprig throttles its use of IndexedDB to not exceed 2 writes per second. Sprig regularly deletes old replay data to minimize disk usage and preserve privacy.


Sprig uploads Session Replay data in one request as opposed to other solutions that upload small pieces frequently. This approach improves compression efficiency, reduces network overhead and reduces energy consumption for mobile devices.


How do I upgrade my Sprig SDK to the latest version?

If you installed with HTML, Google Tag Manager or Segment, your SDK will be automatically upgraded.

For npm and Yarn install methods, reach out to your development team to upgrade the SDK to the latest version. Please note that if you wish to use Replays in additional Products and Environments you will need to update the in each place that the SDK is installed.

Visit our Diagnostics page to learn more.

Why does the number of Replay clips not match the number of Survey responses?

There may be a variety of reasons why your In Product Survey with Replay might not have clips for each response:

  • Sprig will only save clips that are longer than 3 seconds. That means that a user may have quickly answered a survey question and then exited out of the survey before clip length exceeded 3 seconds.
  • Clip upload may have been disrupted by something on the end user's side:
    • Browser tab was closed before a clip was uploaded
    • Internet signal was disrupted before a clip was uploaded
  • Replay parameters were not met (e.g. user session is shorter than specified clip length)

Why are clip lengths different from what I configured?

There may be a variety of reasons why clip lengths are different from what was configured:

  • It took a user less time than the specified "Record for" length to trigger an event
  • If configured to record before and after a survey, some users may take a survey quicker than others which would result in a longer overall clip length

How do I avoid recording certain interactions with pieces of my webpage?

Visit Settings > Replays > Configure to adjust privacy settings including hiding all images or specific CSS elements from clip recordings.

Why are images not showing up in my Replay clips?

The privacy setting Hide all images_under Settings > Replays > User privacy may be ON. Not the case? Please submit feedback here or reach out to your customer support team.

Why are there no interactions listed in the playback side panel?

Interactions will only be recorded if they were sent to Sprig and your SDK was version v2.24.2 or newer at the time of the clip recording.

What happens if a visitor closes a tab or otherwise ends a session in the middle of a recording?

The next time a visitor visits your website, the upload will initiate and a partial clip will be sent to the Sprig dashboard.