What does Sprig collect?

Sprig delivers contextual micro-surveys triggered by user behavior and collects ratings and text responses. When session replay is active, it records mouse movements, clicks, and page state using DOM snapshots. A persistent sprig_user_id cookie or localStorage token identifies returning users.

How does ConsentStack manage Sprig?

ConsentStack gates Sprig on analytics consent when session replay is enabled. For survey-only deployments, it can be configured as functional. This lets ConsentStack enforce the right consent level based on which Sprig features are active on your site.

What tracker domains does Sprig use?

ConsentStack has catalogued tracker domains for Sprig including cdn.sprig.com and api.sprig.com. These are the network destinations Sprig's scripts contact, which a consent platform blocks until a visitor agrees.

Sprig (cdn.sprig.com) - In-Product Research & Consent Profile

Q: Does Sprig require consent?

It depends on your configuration. Sprig used for surveys only can be treated as functional. When session replay is enabled, Sprig captures behavioral data equivalent to a full recording tool and requires analytics consent before initialization under GDPR.

Back to Vendor Library

Overview

Sprig (formerly UserLeap) is an in-product research and user feedback platform that enables product teams to deliver micro-surveys, collect qualitative feedback, and capture session replays without leaving the application context. It is used to gather user sentiment at specific moments in the product journey — onboarding completion, feature adoption, churn signals — enabling teams to combine quantitative product analytics with qualitative user insights.

What This Script Does

The Sprig JavaScript SDK loads from cdn.sprig.com and operates within the host application to deliver surveys and capture sessions:

Survey delivery and response collection

Displays contextual micro-survey prompts (single-question NPS surveys, multi-step feedback forms, emoji ratings) triggered by user behavior, page events, or manual API calls
Survey display rules are configured in the Sprig dashboard: trigger on specific page URLs, after X visits, after a feature is used, or on a specific user attribute condition
Captures survey responses (ratings, text inputs, selections) and transmits them to Sprig's servers (api.sprig.com)
Suppresses survey re-display for users who have already responded, using cookies or localStorage to track response state

Session replay capture

Records user sessions including mouse movements, clicks, scrolls, and navigation events
Session replays are linked to survey respondents to give product teams visual context for qualitative feedback
DOM snapshot capture and incremental mutation recording (similar to FullStory architecture) powers the replay feature
Data is streamed to Sprig's servers and associated with the user's Sprig session ID

User identification and frequency control

Sets a sprig_user_id cookie or localStorage token (1st party, persistent) to identify returning users
Controls survey display frequency: prevents showing the same user multiple surveys within a configurable cool-down period
When Sprig.setUserId() is called, anonymous device IDs are linked to known application user IDs, enabling lookup of sessions and responses by user in the Sprig dashboard
Collects device and browser metadata automatically: OS, browser, screen size, and session timing

Consent & Compliance

Category: Analytics / Functional
GDPR: Sprig spans analytics and functional categories. Survey delivery for product feedback can be argued as functional (directly serving the user's relationship with the product), but the session replay component and persistent user tracking constitute behavioral analytics that require consent. Many GDPR-compliant deployments gate Sprig initialization on analytics consent. The session replay feature in particular captures detailed user behavior and should be treated with the same care as FullStory or Hotjar.
Data transfers: Sprig is a US company. Data is processed in the US. EU-US Data Privacy Framework applies for EU personal data transfers.
Cookies/storage: sprig_user_id (1st party, persistent, duration varies), session state tokens in localStorage
DPA: Sprig provides a Data Processing Agreement for GDPR compliance.

Should You Block This Without Consent?

Conditional. For survey-only deployments without session replay, Sprig can be treated as functional if surveys are delivered in direct response to user actions. However, when session replay is enabled, Sprig captures behavioral data equivalent to a session recording tool and requires analytics consent. Gate Sprig initialization on analytics consent in GDPR-regulated deployments, and disable or exclude session replay if you wish to categorize Sprig as functional-only.

Is Sprig GDPR compliant?

Sprig typically loads analytics and functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Sprig can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Sprig, not on Sprig itself.

Visit website