Discussions

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.

Sprig offers a package through NPM or Yarn, which allows engineers to bundle and host a copy of the Sprig Web SDK as part of your web application. This allows your engineering team to use a static version of Sprig, and receive new updates and features as needed.

Sprig offers customers the ability to choose how often individual users can receive Sprig studies. This is done by adjusting the Recontact Waiting Period on the Settings page. The Recontact Waiting Period is the minimum number of days Sprig waits after a user receives a study before sending them another study.

Once an engineering team has set up Sprig on their application, to track events and attributes, there is no additional work needed to create or launch surveys. Surveys can be launched and maintained solely from within your Sprig dashboard. Sprig often releases new features and new survey question types. Engineering teams can update the Sprig SDK version used in their applications to take advantage of those upgrades. As teams find expanded or new use cases for collecting feedback, engineering teams may be needed to track new visitor events and attributes to qualify visitors into those surveys.

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.

As part of tracking events through Sprig’s Web SDK, your team can define a callback passed to the `showSurveyCallback` parameter, which will be used whenever a visitor is eligible for a survey. Your function needs to return a boolean, when true, will then allow the Sprig Web SDK to display the survey to your visitor.

On desktop web applications Sprig supports positioning surveys in all four corners of the browser window, plus centered modal. Positioning can be changed from your dashboard, through the [Look & Feel](https://app.sprig.com/settings/look-and-feel) section under Settings. On mobile applications, the study will always be presented at the bottom of the device window.