Discussions

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. Whenever an attribute is set, that value will override any previous existing value. Please see this article for more information on sending sensitive data or server attributes 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.

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’s Web SDK tracks the following attributes for performance, and to help segment your visitors: - Web browser and version - Device - Session count - Page URL - Screen size - Browser language - Operating System and Version