Web - Introduction

The Sprig SDK allows you to monitor your customer's interactions and generate triggers to launch a Sprig study, asking just the right question at just the right time.

JavaScript or Google Tag Manager

To launch a Sprig study on your Website or Web App, you'll need to either install the Sprig SDK code snippet on each page or deploy it using Google Tag Manager.

Sending Events to Sprig

Sprig uses events in your Web environment to display studies at some point in time. In addition to using these events to trigger a study, they can also be used as a filter to target the study at a subset of the potential audience.

Once you've installed the Sprig SDK, the next step is to configure the tracking of events that you would like to use to trigger a study. There are two methods of tracking events for Web environments:

  • No Code
  • Code

No Code Events

Once the Sprig SDK is installed, No Code events can be added in Sprig as Events. As No Code events rely on the URLs, HTML elements, and CSS page structure, they usually do not require any further coding of that Web page. No Code events can give groups without direct access to the Web code the flexibility to configure and launch new studies without engaging the Web code owners. However, No Code events can only display Web studies.

Code Events

Sometimes No Code events may not provide visibility into a particular event that you would like to track; for example, you may want to study users who, in the previous month, have downgraded their account status from premium to standard. It may be preferable to generate the event directly from the Website or Web App in such cases. Read more on Code Events implemented with:

Sending Attributes to Sprig

Sprig tracks a default set of attributes but also allows you to specify custom client-side attributes and values. These attributes allow you to provide more context about the user to understand their feedback better. You can also use these attributes for targeting, or filtering, which audience you wish to study. Read more on sending Attributes to Sprig using: