Study Triggers, User Filters, and Groups

This document explains how to add Study Triggers, User Filters, and Groups to a study in Sprig

👍

Sprig SDK Installation & Event/Attribute Instrumentation Required for Targeting

In-product Studies like Surveys, Feedback, Replays and Heatmaps require SDK installation and events to be instrumented to properly capture your user's experience. Learn more about Installation, Events and Attributes

Overview

Targeting unlocks the full potential of Sprig by enabling you to reach the right users at the right time across Surveys, Feedback, Replays, and Heatmaps, using study trigger events and/or URLs, user filters, and other advanced filters.

Example Survey Targeting Card

Example in-product Survey targeting card.

Study Triggers

Study triggers consist of events and/or URLs that initiate Surveys, Feedback, Replays, and Heatmaps, and are required for all in-product studies.

Steps to add a Study Trigger:

  1. Configure your Survey (for Surveys & Feedback)

  2. Select a Platform

  3. Select Trigger Type:

    1. Click Add event or URL
      1. Heatmaps and Feedback are restricted to inline URL events only
    2. (optional) Add additional triggers - Sprig supports up to 10 triggers per in-product study.
  4. Configure Trigger: Event Properties (optional)

    1. Event properties allow you to more specifically target users - limited to Code events
    2. Note: You are limited 10 event properties across all triggers in a study. For example, if your study has 2 triggers, you can have 5 event property filters per trigger.

Note: You can use the same event to trigger more than one Study, but if the same study type, your visitors will be evenly sampled to contribute to a study

Wait Time Filter - Surveys Only (Optional)

Wait times allow you to ensure that you are not interrupting key user flows. Adding a wait time will delay the survey from displaying for some number of seconds.

Inline URL Event Triggers

Inline URL Event Triggers work the same under the hood as No Code Events, just with the ability to create a No Code Event directly inline from the Targeting card.

As with all No Code Events, your SDK must be first be installed on the same page that you are targeting with a URL.

Example: Inline URL Event alongside Code Event

Example: Inline URL Event alongside Code Event

Advanced Session Filters

  1. Session History - # of visits before triggering
    1. Measured as 12-hour windows in which a visitor has one or more events tracked
  2. Page View History - # of web pages seen in a single session (Web studies only)

User Filters - Attributes, Group or Event History (Optional)

User filters allow you to target specific user segments based on their attributes or behaviors. This helps in personalizing the study to relevant user groups.

There are several types of filters available:

  1. Attributes: Enables filtering by properties of your users (e.g. Plan = Enterprise)
  2. Groups: Enables filtering by groups of users
  3. Event History: Enables filtering by previous interactions (e.g. Dashboard - Sign Up Complete Last Occurred > 60 Days Ago)
  4. Question Types & Logic Statements( e.g. How would you rate your satisfaction with the following is 4)
  5. No Code Event URLs
  6. [Pages]
  7. [Signals]
  8. [Devices]
  9. [Themes]
  10. Frustration Signals - Public Beta(e.g. Rage Clicks = to 5)

Steps to Add a User Filter:

  1. Click Filter button

  2. Select one of the available categories, depending on Survey Type, categories and options will vary - see options variables below:

Survey Filters

QuestionsOperatorsValue
Questions created in the survey. Use to narrow down questions you want to highlight or dig deeper on.Is, Is not , is submitted , is skippedOptions specific to the question selected
Trigger EventsOperators
Events that have been triggered in a survey. Used to filter specific events that triggered the survey.Triggered study, Did not trigger study
Trigger PageOperatorsValue
Page on which a user was on when the survey was displayed. Use to target specific survey results when a page was viewed.Exactly matches, Contains , Starts with , is skipped, Does not exactly match, Does not contain, Matches regular expression, Matches regular express (case sensitive)Name, path, or a URL of desired page

Replay Filters

PagesOperatorsValue
Page on which a user was on when the survey was recording. Use to target specific replay results when a page was viewed.Exactly matches, Contains , Starts with , is skipped, Does not exactly match, Does not contain, Matches regular expression, Matches regular express (case sensitive)Name, path, or a URL of desired page
EventsOperatorsValue
Replay Events that are contained within the Replay clips of the study. If an event was never triggered and captured in the Replay study, then it should not show on this list.= (equal to), ≠ (not equal to) , < (less than) , ≤ (less than or equal to), > (greater than), â‰Ĩ (greater than or equal to), Not tracked in clipNumerical value
SignalsOperatorsValue
Replay Signals are tracked by interactions and frustrations. Clicks, Rage Cicks, and Dead Clicks are three signals we use in Replays today.= (equal to), ≠ (not equal to) , < (less than) , ≤ (less than or equal to), > (greater than), â‰Ĩ (greater than or equal to), Not tracked in clipNumerical value
DevicesOperators
Filter the recordings by device that was used.is device), is not device

User Filters

AttributesOperatorsProperty
Ideally only showing Attributes of users captured in the study.= (equal to), ≠ (not equal to) , < (less than) , ≤ (less than or equal to), > (greater than), â‰Ĩ (greater than or equal to), Contains, Does not contain, Starts with, Ends with, Is set, Is not setAvailable properties are specific to Attribute selected

Event History

Event History has sub-filters after selecting an Event specific to your use-case. Use these filters to set parameters around a specific event in your survey.

FilterOperatorValueUse
Tracked= (equal to), ≠ (not equal to),\< (less than),≤ (less than or equal to), > (greater than), `â‰Ĩ (greater than or equal to)Numeric valueThe Tracked operator compares the total number of times an event has been triggered by a visitor, since first being tracked, to the specified value provided by the user
First trackedIs greater than, Is less than , is greater than or equal to , is less than or equal to , is equal toThe First tracked operator compares the first recorded event trigger and compares to the value specified by the user
Last trackedIs greater than, Is less than , is greater than or equal to , is less than or equal to , is equal toThe Last tracked operator compares the last recorded event trigger and compares to the value specified by the user
Is SetYesThe Is Set operator checks whether or not there is a value stored for the intended event

Creating & Managing Groups

Groups help you segment visitors for multiple studies. Instead of setting up each study individually, you can create a group filter and use it across studies.

Groups can be created a variety of ways:

  1. Manually - With the users you have already tracked in Sprig
  2. via CSV Upload - With additional attributes about users
  3. via Dynamic Groups - With existing and future users based on Attributes, Event History, or other Groups

Creating a Manual Group

Manual groups are fixed collections of users.

  1. Go to Users > All Users.

Add to New Group

  1. Select users by checking the boxes.
  2. Click Add to Manual Group.
  3. Click Create Manual Group.
  4. Name and describe the group.
  5. Click Create Manual Group.
  6. Close the window.
  7. Check your new group under the Groups tab.

Add to Existing Group

  1. Select users by checking the boxes.
  2. Click Add to Manual Group.
  3. Choose the group(s) to add users to.
  4. Click Add to Group.
  5. Check your updated group under the Groups tab.

Add from CSV

  1. Click Upload CSV.
  2. Select and upload your file.
  3. Map the column to User ID.
  4. Check Add users to Group after uploading.
  5. Click Continue.
  6. Choose to add users to an existing group or create a new group.
  7. Click Add to Group.
  8. Refresh to check if validation is complete.
  9. Close the window.

Creating a Dynamic Group

Dynamic groups change based on filters.

  1. Go to Users.
  2. Click Filter Users.
  3. Add filter conditions (e.g., Language = French).
  4. Apply the filter to see results.
  5. Click Create Dynamic Group if satisfied with the results.
  6. Name and describe the group.
  7. Click Create Manual Group.
  8. Check your new group under the Groups tab.