Goals
Understanding how and when to use goal-based triggers
Overview
Goals triggers cause a rule to be evaluated only once that goal’s own evaluation criteria has been satisfied. This means they introduce the concept of logic into a trigger, and allow you to set specified thresholds or conditions that you want a trigger to pass before a rule is evaluated.
When you set up Goal triggers, you can choose whether you want to consider activities, awards or segments, as part of that evaluation:
Activity-based goals: can be as simple as the number of actions meeting some specified threshold, or more nuanced, like multiple separate actions meeting specified thresholds as defined by the logic implemented when creating the goal.
Example: a goal could specify that a user must fulfill ten deliveries within a given time period for the goal evaluation criteria to be passed.
Award & segment-based goals: these function similarly to activity-based goals except they require a user to be in a segment, or have some defined number of awards. These types of goals can be set to run off scheduled evaluation frequencies to ascertain whether a meets the qualification criteria.
Example: a user must have over 10,000 points to pass the goal evaluation.
Goal Types
Cumulative Activity Goals
Activity goal triggers are evaluated based on the total number of activities that have occurred ever, or in a defined period, by a given user. They use basic logic operators like =, >, <, >=, <=. For instance, a goal could be successfully evaluated when a user completes more than 50 deliveries in a 7-day period.
Note: When a Cumulative Activity Goal is created, a user's Activities only begin begin counting toward that Goal from the moment it is created. For example, if you already completed 100 Activities, and you set the Cumulative Activity goal 50, the Goal will only trigger after the user completes another 50 Activities after the Goal is created.
Action Goal vs Action Trigger: Let's say I want to award $5 every time a user completes a trip. I would use a simple Action trigger "Trip Complete" to award $5 every-time a trip completes.
Now let's say I only want to award a user the first time they complete a trip. I need logic to evaluate this. I'd use a Goal trigger, with logic "Trip Complete" = 1. Similarly I could award $5 only when the user completes 5 trips, where "Trip Complete" = $5.
Cumulative Award Goals
Award goal triggers are evaluated based on whether a user has a certain number of awards. Again, they use basic logic operators like =, >, <, >=, <=. For example, a goal could be reached when a courier has over 5,000 loyalty points or when a contractor has a 'gold-star' badge.
Segment Goals
Segment goal triggers evaluate based on whether a user is in a segment or not. This can be either TRUE or FALSE. For example, a segment-based goal could be used to personalize a user's experience based on that segment, or otherwise evaluate a rule based on whether a user is in or out of one or more segments during a scheduled evaluation.
Percentile Goals
Percentile action goals: Percentile action goal triggers evaluate whether a user falls within a defined percentile of all users who have done a defined action in a given time period. For example, trigger a rule to distribute an award if the user is in the top 5% of customers based on total purchases made last week.
Percentile award goals: Percentile award goal triggers evaluate whether a user falls within a certain percentile of all users who hold a defined award (such as points or medallions). For example, a goal could be satisfied when a user is in the top 10% of all users based on total points held by those users.
Creating Goal Triggers
You can create a new goal trigger by navigating to the Goal tab of the Triggers section. Here's an overview of the inputs required:
| Input | Description |
|---|---|
Goal Name | Enter a name for the goal. This may be user-facing, so choose a name that is identifiable for both external and internal users. |
Goal Type | Choose from the following options. These are explained above.
|
Short ID | This is the ID used in the Village database to identify a particular trigger. The short ID is auto-populated based on your Goal Name, but you also edit it if needed. |
Description | This is an internal-only description of what this goal does. We suggest you are as specific as possible for other admin users to understand the goal logic. |
Associated Users | Note that you do not set associated users for a goal, but be aware that the goal inherits the associated users from its underlying action triggers, or based on the awards or segments that you specify in the goal's logic. Only these users will appear as available Recipients in any Rule that uses this goal. |
Goal Requirements | This is where you set the logical conditions that need to be satisfied:
You can add multiple goal requirements as needed. Be aware that these are AND conditions, meaning all need to be satisfied for the goal to be satisfied overall. To create OR conditions, please create a separate goal. |
Qualification Times | Action-based Goals (both Cumulative and Percentile) have Qualification Times. These let you specify a time period in which the goal requirements must be achieved. For example, a user must complete 10 transactions this month. If not qualification time is specified, the goal will evaluate all actions, irrespective of time period. You can specify both date and time restrictions, or create recurring qualification periods. For more complicated qualification times, such as 6-9pm Thursdays and Fridays, use the 'Custom' time picker.
|
Goal Evaluation Rules | All goals require you to specify when the goal will be evaluated. As a reminder, this can occur in two ways: when an activity occurs (either on your platform, or as the result of another rule distributing an award or segment), and/or on a predefined schedule. For non-percentile goals:
For percentile goals:
|
Ongoing Qualification | If you select "Require Ongoing Qualification," it means that whatever award or segment was issued to a user as a result of initially qualifying for a goal will be revoked if they no longer meet the qualification requirements. As an example, if a rule with a goal-based trigger awards a status badge to the top 10% of shoppers by purchases, selecting ‘Require Ongoing Qualification’ means this status badge will be revoked if the user falls out of the top 10% of shoppers. |
As a reminder, once you have created your goal trigger, you then need to create a rule that uses this trigger for any output operation to occur when the goal is satisfied.
Editing Goals
To edit a Goal, go to Triggers section, click on the Goals tab, and then click the "Edit" button. From there, you can update any of the fields set when creating the Goal.
Duplicating Goals
To duplicate a Goal, click the purple duplicate button on the right side of a Goal.
Deleting Goals
To delete a Goal, click the "Delete" button. Please note that deleting a Goal is permanent and cannot be undone. You will not be able to delete a Goal when it is being used as part of an active rule. To do so first deactivate the rule, before deleting the Goal.
Last updated