Defining Action Filters
Action Filters are used to define the action customers can perform which you would like to study.
They are used in many Woopra features, such as:
- Funnel Reports – Action Filters allow you to define the goals of your funnel. For example, “signed up”, “opened Customer.io Email invite”, “downloaded mobile app”, then “made purchase from mobile app” can all be defined by individual Action Filters.
- Retention Reports – Action Filters allow you to define the retention milestones for your reports. For example, you can answer the question “Of my customers who used Feature X, how many continue to return and use Feature Y?”
- Triggers – Action Filters allow you to define the condition which fires a Trigger event. For example, managers may want to receive a notification each time a high profile customer submits a support ticket.
|Action||The “Action” drop-down menu lists all of the actions you may select from. This list includes events Woopra tracks by default, such as pageviews, AppConnect Actions, and custom events which you have added such as “payment”, “sign up”, “play video”, etc.|
|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 sent with the given 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, IP address, etc.
For example, I may want to create a filter for “customers who opened an Email sent through customer.io from a mobile device”, where “device type is mobile” would be the visit constraint.
Example: How To Create a Action Filter
If we have installed the customer.io AppConnect App, we might add a step to a Funnel report for people who have opened a promotional email:
- Add a goal to the Funnel to open the Action Filter editor, and select the action “Email Opened” from the dropdown list. Since the customer.io App has already defined the action “Update Status” in our Schema, it will be pre-populated in our actions drop-down menu.
- Select ‘Save Goal’ to save your changes and create a new column in the Funnel.