Discussions

We suggest sending events to Sprig as they occur. Events should track actions or interactions within your application, such as viewing a certain page, using different modals, or other tracked interactions like scroll depth and exit intent. Sprig’s no code events system can be used to target visitors viewing different pages based on URLs, clicking on elements with specified text, or different HTML elements (e.g. buttons, widgets) through CSS. Teams can use the Sprig API to send asynchronous or server-side tracked events. Similar to the SDK, these events can be sent to us as they occur, or part of a batched job that sends events for each of your users on a recurring cadence.

User IDs can be anonymized via encryption before being passed to Sprig. When data is exported from Sprig those encrypted IDs can then be decrypted off-platform for reference.

Developers will often choose to send a foreign key or reference ID to Sprig, instead of the exact user ID stored in their services. While a foreign key is not a strict requirement, Sprig is fully flexible in meeting companies’ security practices and needs.

For any sensitive data that users do not want exposed or surfaced in their application, Sprig offers a REST API. The `/users/` endpoint allows teams to create, or update, visitor records from your backend. If the `userId` sent to the API does not already exist in the specified environment, a new visitor record will be created. If the `userId` already exists, any new data will be appended to that visitor record.

Sprig allows you to export visitor and response data, either through the API, webhooks, or from the Sprig dashboard. Survey questions, responses, and themes can all be exported either from the Sprig API with the use of your API key, or by downloading the data as a CSV from within your dashboard. Webhooks enable you to have survey responses and survey events automatically sent to an endpoint, as they come in.

Sprig can ingest data from the SDK, CSV upload, or API. The primary method of sending data into Sprig is via the SDK from your application. CSV upload, and the API can be used to send backend data that may not be available in your application that is necessary for survey filtering.

Sprig has a bi-directional integration with Segment so data can be sent to and received from Sprig. The Sprig Actions destination plugin can be used with web and mobile applications to deploy the Sprig SDK, and automatically map Segment's track and identify calls to Sprig's SDK methods. This enables all of the data already tracked with Segment to also be tracked with Sprig. Our Segment Streams integration can be used to automatically send Sprig survey responses back to Segment, so they can be transported to other destinations such as a data warehouse or BI tool.