Discussions
How do older SDK versions deployed on an application, handle new features as they are released?
As new features such as new question types are rolled out, these changes may require an updated version of the SDK on your application.
Sprig tracks the visitor’s current SDK version, as part of determining whether or not they are eligible to see a survey. Visitors on an older version of the SDK will be unable to receive or respond to any surveys requiring a newer version, but are still eligible to receive any surveys which they meet all criteria for.
The dashboard will warn you of potential SDK compatibilities when creating a survey, and will show you the expected percentage of visitors who can receive a survey based on the questions and features you are using.
Posted by Sprig about 1 year ago
How can we anonymize our user IDs before sending them to Sprig?
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.
Posted by Sprig about 1 year ago
Can we self-host the Sprig SDK on our servers?
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.
Posted by Sprig about 1 year ago
What does Sprig use to ensure that people do not see multiple surveys over a certain period of time?
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.
Posted by Sprig about 1 year ago
Once Sprig is set up, what additional engineering work is needed to maintain the integration in our application?
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.
Posted by Sprig about 1 year ago
Do I need to send Sprig the same user ID that we use for our own services?
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.
Posted by Sprig about 1 year ago
Is it possible to send sensitive data to Sprig, as opposed to exposing it in our application and sending it through the Sprig SDK?
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.
Posted by Sprig about 1 year ago
What data can I export out of Sprig?
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.
Posted by Sprig about 1 year ago
How can I send data into Sprig?
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.
Posted by Sprig about 1 year ago
I have other web integrations which might overlap and conflict with Sprig. Is it possible to tell Sprig not to display a survey under certain contexts or views?
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.
Posted by Sprig about 1 year ago