Have a question?

Defining Trigger Filters

Overview

Trigger Filters are used to define the action the customer committed which you would like to study.

Woopra Trigger FilterThey are used in many Woopra features, such as:

  • Funnel Reports – Trigger Filters allow you to define the goals of your funnel. For example, “signed up”, “downloaded mobile app”, then “made purchase from mobile app”.
  • Retention Reports – Trigger Filters allow you to define the retention milestones for your reports. For example, you can answer the question “for how long did customers who used Feature X continue to use Feature Y?”
  • Triggers – Trigger Filters allow you to define the parameters for a Trigger event, such as a notification. For example, managers may want to receive a notification each time a customer makes a purchase over $1,000.

Below is an explanation of the two sections you will need to define when creating a Trigger Filter.

Action The “Action” drop-down menu lists all of the actions you may select from. This list includes both events Woopra tracks by default, such as pageviews, or custom events which you have added such as “payment”, “sign up”, “play video”, etc.

Note that the custom events are pre-populated in the drop-down based on how you have defined them in your Schema.

Action Constraints Once you select an action, a section will appear below the drop-down that reads “+ Add Action Constraints”. By clicking this, you will be able to add constraints to the action in order to further define it.

The options listed in the constraints drop-down are based on the properties you have defined for the given custom event in your Schema. For example, you may have a custom event “payment”, for which you track the properties “amount”, “package type”, and “payment method”. These three properties will be pre-populated in the actions constraints drop-down menu.

Visit Constraints The “Visit Constraints” section allows you to define certain criteria that the visit must match when the filter’s action is committed by the customer. This could be the visit referral source, the browser used during the visit, the customer’s location during the visit, etc.

For example, I may want to create a filter for “customers who made a payment from a mobile device”, where “device type is mobile” would be the visit constraint.

Example: How To Create a Trigger Filter

If we are tracking the custom event “signup” and sending the property “company size” with it as defined in our Schema, we may set up a Trigger Filter for when a customer signs up from a company with over 200 employees using a mobile device and from the United States by following these steps:

  1. Open the Trigger Filter editor by clicking the “Any Action” button next to “When”
  2. In the Action section, select the action “signup” from the drop-down menu. Since we have already defined the custom event “signup” in our Schema, it will be pre-populated in our actions drop-down menu.
  3. Add an action constraint by clicking “+ Add Action Constraint”
  4. Select “company size” from the action constraint drop-down menu. Since we have already defined the property “company size” in the Schema for our custom event “signup”, “company size” is pre-populated in the action constraint drop-down menu for the action “signup”.
  5. After selecting “company size” from the action constraint drop-down, select “greater than” from the next drop-down and type “200” into the next field so that it reads “company size greater than 200”
  6. Add a visit constraint by clicking on “+ Add Visit Constraint”. Select “Device Type” from the first drop-down menu, leave the second drop-down menu as “is”, and select “mobile” from the third drop-down menu so that it reads “device type is mobile”.
  7. Add another visit constraint by clicking on “+ Add Visit Constraint”. Select “Country” from the first drop-down menu, leave the second drop-down menu as “is”, and select “United States” from the third drop-down menu so that it reads “country is United States”.
  8. Click “Apply”

Need any help? Contact support