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 allows you to unlock the full potential of Sprig. With Trigger Events, User Filters and advanced settings, you can easily send your Survey or Feedback, or capture Replays and Heatmaps, of the right users, at the right time.
Study Triggers
Study triggers are Events or URLs to trigger Replays, Heatmaps, Survey or Feedback. Study triggers are required for all In-product studies.
Steps to Add a Study Trigger:
-
Configure your Survey (for Surveys & Feedback)
-
Select a Platform
-
Select Trigger Type:
- Click Add event or URL
- Heatmaps and Feedback are restricted to inline URL events only
- (optional) Add additional triggers - Sprig supports up to 10 triggers per in-product study.
- Click Add event or URL
-
Configure Trigger: Event Properties (optional)
- Event properties allow you to more specifically target users - limited to Code events
- 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.
Advanced Session Filters
- Session History - # of visits before triggering
- Measured as 12-hour windows in which a visitor has one or more events tracked
- 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 three kinds of user filters:
- Attributes: Enables filtering by properties of your users (e.g.
Plan = Enterprise
) - Groups: Enables filtering by groups of users
- Event History: Enables filtering by previous interactions (e.g.
Dashboard - Sign Up Complete Last Occurred > 60 Days Ago
)
Steps to Add a User Filter:
-
Add a New Filter:
- Click Add attribute, group or event
-
Adding Filters
- Select an attribute
- Define the criteria for the selected attribute
- Included Attribute Conditions:
is equal to
is not equal to
is set
is greater than
is greater than or equal to
is less than
is less than or equal to
- Included Attribute Conditions:
-
Adding Groups:
- Select a Group
- Define the criteria for the selected group
- Included Group Conditions:
users in group
users not in group
- Included Group Conditions:
-
Adding Event History:
- Select an Event
- Define the criteria for the selected groups
Filter | Value | Use |
---|---|---|
Is Set | Yes or No | The Is Set operator checks whether or not there is a value stored for the intended event |
Occurrences | Is greater than , Is less than , is greater than or equal to , is less than or equal to , is equal to | The Occurrences 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 Occurred | Is greater than , Is less than , is greater than or equal to , is less than or equal to , is equal to | The First Occurred operator compares the first recorded event trigger and compares to the value specified by the user |
Last Occurred | Is greater than , Is less than , is greater than or equal to , is less than or equal to , is equal to | The Last Occurred operator compares the last recorded event trigger and compares to the value specified by the user |
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:
- Manually - With the users you have already tracked in Sprig
- via CSV Upload - With additional attributes about users
- 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.
- Go to Users > All Users.
Add to New Group
- Select users by checking the boxes.
- Click Add to Manual Group.
- Click Create Manual Group.
- Name and describe the group.
- Click Create Manual Group.
- Close the window.
- Check your new group under the Groups tab.
Add to Existing Group
- Select users by checking the boxes.
- Click Add to Manual Group.
- Choose the group(s) to add users to.
- Click Add to Group.
- Check your updated group under the Groups tab.
Add from CSV
- Click Upload CSV.
- Select and upload your file.
- Map the column to User ID.
- Check Add users to Group after uploading.
- Click Continue.
- Choose to add users to an existing group or create a new group.
- Click Add to Group.
- Refresh to check if validation is complete.
- Close the window.
Creating a Dynamic Group
Dynamic groups change based on filters.
- Go to Users.
- Click Filter Users.
- Add filter conditions (e.g.,
Language = French
). - Apply the filter to see results.
- Click Create Dynamic Group if satisfied with the results.
- Name and describe the group.
- Click Create Manual Group.
- Check your new group under the Groups tab.
Updated 6 months ago