Discussions
What are some common methods or design patterns for sending visitor attributes to Sprig?
Attributes, including the visitor’s user ID, can be sent whenever a visitor is identified. This can be done on instances such as every time a visitor logs in to their account, or as they meet criteria for new segments based on their interactions within your application.
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.
What attributes does Sprig track by default?
For security and privacy, Sprig does not track any PII by default.