Discussions
What are some common methods or design patterns for sending events to Sprig?
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.
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.
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.
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.
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.
How does Sprig work with Segment?
Sprig has a bi-directional integration with Segment so data can be sent to and received from Sprig.