Discussions

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. Sprig’s no code events system can be used to target visitors viewing different pages based on URLs, clicking on elements with specified text, or different HTML elements (e.g. buttons, widgets) through CSS. Teams can use the Sprig API to send asynchronous or server-side tracked events. Similar to the SDK, these events can be sent to us as they occur, or part of a batched job that sends events for each of your users on a recurring cadence.

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 supports two kinds of no code events which you can create and manage from your dashboard: Page URL, and Interactive. Page URL events are triggered when a visitor loads a matching URL. Sprig supports different comparators so you can match any pattern of URLs from your application. Interactive events are triggered when a visitor clicks a specific CSS element, or any element containing some matching text. Interactive events also use the same logic as Page URL events, so you can target specific pages.