Triggers and Filters

Triggers

Triggers are required for both Web and Mobile studies. A trigger is an event used to display a study. An event is any action that a user may take in your web or mobile application. The Web or Mobile SDK must be installed on your Web or Mobile applications in order to use in a given study.

Every study contains an Audience tab. The Audience tab in a study is where you associate an Event to act as a Trigger to display the study when the user interacts with your application.

📘Info

For Web and Mobile study to trigger, make sure to have decided how to implement that event prior to defining the Audience portion of your study. For Web you can add Events via No Code or Code. For Mobile use Code events.

Select an Event to Trigger

1. Navigate to a study.
2. Select the Audience tab of the study.
3. Choose either Web or Mobile App as the delivery method.
4. Navigate to the When to Send.
5. Click Select... and scroll or type the event name that is intended to display the study to your customer, then select that event.

Additionally, you can choose if you'd like a few different events to be eligible to trigger the study and in the case of a Web study you can also set time delays that afford a few extra moments from when the user performs the action and when it's actually displayed.

Select Multiple Triggers

Sprig supports up to 5 unique triggers per in-product study. To add additional triggers, click Add Another Event.

Set Time Delayed Triggers

You can set a time delay (web only) before showing the study. This time delay is the number of seconds to wait after the trigger occurs to display a study.

Filter

Filters are useful when you want to segment the audience that should qualify for a study. We’ll sometimes reference these as study filters. A study's filter can be either an event or an attribute. Study Filters are available for Web, Mobile, and Email studies; not Link studies.

Select Filters

1. Navigate to a study.
2. Select the Audience tab of the study.
3. Choose either Web, Mobile App, or Email as the delivery method.
4. Navigate to Who to Send to. Click + Add Filter.
5. Scroll or type the event or attribute name that is intended to display the study to your customer, then select that event or attribute.

Sessions as Filters

1. Select Advanced from the dropdown for filters.
2. Choose the Session check box.
3. Input a number to represent the number of sessions you'd like the study to wait before a given user can experience it.

📘Info

Sessions in Sprig are measured as 12-hour windows in which a visitor has 1+ event tracked in Sprig.

Page Views as Filters

1. Select Advanced from the dropdown for filters.
2. Choose the Page check box.
3. Input a number to represent the number of pages you'd like the study to wait before a given user can experience it.

📘Info

Page views are only applicable to web studies and will not be displayed for email, mobile, link-based studies.

Events as Filters

Events are defined as the actions or behaviors users take on a given page or application. Sprig relies on events to deliver highly customizable studies that are targeted on an event or multiple groups of events. When you select an event as a study filter, you'll be provided with a set of conditions to choose from to include or exclude the values we receive about that event.

Included Event Filters:

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 is triggered 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

Attributes as Filters

Like events, attributes are just another way to enhance your study targeting functionality. While events are triggered behaviors that occur on the client-side, attributes can be thought of as groups or segmentations that are assigned based on that behavior.

Included Attribute Filters:

• is equal to,

• is not equal to ,

• is set ,

📘Info

Sprig does not support DATE or DECIMAL as attribute data types. All non-supported data types are converted to strings. The only logical operators available for Strings are equal, not equal and is set.

• is greater than ,

• is greater than or equal to ,

• is less than ,

• is less than or equal to

📘Info

Attribute values are set on the client-side, for more information on setting attributes please read through SDKs. When adding attributes to use as filters, we limit the total number of distinct key-value pairs to be <= to 100. So for example, if you are trying to send an attribute that aims to compare orderCartValue it is best to convert and send as quantifiable buckets or ranges rather than an incremental array of values that will render more than 100.

AND/ORs

AND/ORs allow for increased functionality when targeting user cohorts, conditions with AND must satisfy all criteria, whereas conditions with OR only need to satisfy one.

Logic Groups

Logic groups allow you to create more complex groupings of ANDs/ORs. For a study to be delivered it must pass at least one of the logic groups. To add a logic group, click ... and select Add Logic Group. Then select the Event or Attribute you wish to add to the Logic Group.

The icon denotes where the logic group is defined.

Deleting Logic Groups/Filters

To remove a logic group or a filter, click ... and select Remove.

Insert New Below

Click ... and select Insert New Below to add another study filter below the current filter. If you do so in a logic grouping it will add an additional condition within that same logic group.