Point-based markers are designed for the moments when you want a clear, consistent answer to one question about your accounts. How far along is this account in activation? How deeply has it adopted the product? How healthy is it overall? You pick the factors that matter, decide how many points each one is worth, and set up Marker Values that fit your use case, like Not Started, Ramping, and Fully Activated. Odie evaluates every account the same way, so when an account lands somewhere, you can see exactly why. And before you save, you can preview how it all plays out on your real accounts.
How we Evaluate Point-based Markers
- Each criterion gives the account points, based on the first condition it matches.
- Each group combines its criteria into one group total.
- Odie weights the group totals and adds them up into the account's total points.
- The total lands in a Marker Value, unless an override places the account directly.
Start a point-based marker
- Go to AI Toolkit > Markers and click New.
- On the Basics step, name the marker and choose Point-based.
- Click Next to open Rules & Scope.
The builder opens as a full page with three steps: Basics, Rules & Scope, and Preview. Click Back at any time to return to the previous step.
Screenshot needed: Basics step with the Point-based option selected.
Add criteria and conditions
A criterion is one thing you want to evaluate, such as Weekly Active Users. Each criterion has numbered conditions, and each condition is worth a number of points.
- In a group, click Add Criterion.
- Click the criterion name to rename it.
- Add conditions and enter the points each one gives.
- Enter the points for Everything Else. This is always the last step and covers accounts that match none of the conditions above it.
Odie checks conditions from top to bottom, and the account gets the points of the first condition it matches. Use the up and down arrows to reorder them.
Conditions such as Is Null and Is Not Null don't need a value. Criteria are collapsible cards, so you can close the ones you're done with.
Screenshot needed: Criterion card with numbered conditions and the Everything Else step.
Group criteria and set weights
Groups let you evaluate related criteria together, such as everything about product usage.
- Click Add Group and enter a Group Name.
- Choose an Aggregation to combine the group's criteria:
- Average: the average of the criteria points.
- Highest: the most points any criterion in the group earned.
- Lowest: the fewest points any criterion in the group earned.
- Enter a Weight (%) for each group. Weights must add up to 100.
The account's total points are each group total multiplied by its weight, added together. If an account has no data for a group, Odie leaves that group out and scales up the other weights to fill the gap.
Define Marker Values
Marker Values are the labels accounts receive, based on their total points.
- Open Marker Values and click Add Marker Value.
- Enter a Value Name, choose a Priority, and set From Points and To Points.
- Choose the marker's Icon. A preview shows how each value's chip will look on an account.
An account's total lands in the value whose range contains it. Ranges can't overlap.
The Score Range shows the lowest and highest total an account can actually get with your current criteria. Odie warns you when:
- Some accounts could land below your lowest value or above your highest value, so they would get no marker.
- A Marker Value can't be reached by any account.
Each warning names the criteria that cause it. Hover over the link to see them, then click one to jump straight to it.
Screenshot needed: Marker Values pane with Score Range, a coverage warning, and the Icon picker.
Add overrides
An override puts matching accounts straight into a chosen Marker Value, no matter how many points they earn. For example, any account whose onboarding is paused can always show Not Started.
- Open Overrides and click Add Override.
- Enter an Override Name and choose the Marker Value to apply.
- Add the condition that accounts must match.
If an account matches more than one override, the first one in the list wins. Use the up and down arrows to set the order. Odie still adds up the account's points and shows them in the preview.
Limit the marker to segments
By default, the marker evaluates every account. To evaluate only some accounts, open Segments and choose one or more Segments.
Preview results
The Preview step shows how your rules evaluate real accounts. Nothing runs on its own.
- Click Generate Preview. The first time, you'll see an empty state with this button.
- Review the results:
- Accounts Evaluated: how many accounts were evaluated.
- A bar chart of how many accounts land in each Marker Value.
- A searchable table with each account's Account, Score, Marker Value, and the Override that applied, if any.
- After you change any rules, click Generate Preview again to see fresh results.
If Odie can't check a condition, for example because its data source isn't connected, a yellow warning names that condition and explains that it was treated as not matching. The rest of the preview still runs.
Screenshot needed: Preview step with Accounts Evaluated, the distribution chart, and the results table.
Example: Activation Progress
This marker places accounts in Not Started, Ramping, or Fully Activated.
Product Usage group (Weight 60%, Average)
| Criterion | Condition 1 | Condition 2 | Everything Else |
|---|---|---|---|
| Weekly Active Users | 50 or more: 100 points | 10 or more: 50 points | 0 points |
| Features Adopted | 5 or more: 100 points | None | 20 points |
Support group (Weight 40%, Average)
| Criterion | Condition 1 | Condition 2 | Everything Else |
|---|---|---|---|
| Open Support Tickets | 0: 100 points | 2 or fewer: 60 points | 10 points |
Marker Values
| Value Name | From Points | To Points |
|---|---|---|
| Not Started | 0 | 39 |
| Ramping | 40 | 69 |
| Fully Activated | 70 | 100 |
Override: Onboarding Paused. Accounts whose onboarding status is Paused go straight to Not Started.
How Northwind gets its value
Northwind has 30 weekly active users, 6 adopted features, and 1 open support ticket.
- Weekly Active Users: 30 doesn't match Condition 1, but it matches Condition 2, so Northwind gets 50 points.
- Features Adopted: 6 matches Condition 1, so Northwind gets 100 points.
- Product Usage averages its criteria: (50 + 100) / 2 = 75.
- Open Support Tickets: 1 doesn't match Condition 1, but it matches Condition 2, so Northwind gets 60 points. Support totals 60.
- Total points: (75 × 60%) + (60 × 40%) = 45 + 24 = 69.
- 69 falls between 40 and 69, so Northwind is Ramping.
If Northwind's onboarding were paused, the override would make it Not Started instead. The preview would still show its 69 points, with Onboarding Paused in the Override column.
FAQs
What happens if an account's total falls between two Marker Values?
It counts toward the lower value. Only accounts whose total falls below your lowest value or above your highest value get no marker. The Score Range warning tells you when this can happen.
What if an account has no value for a criterion?
By default, it gets the Everything Else points. Turn on Exclude null values from calculation on a criterion to skip that criterion for accounts with no value instead. If an account has no data for any criterion in a group, Odie leaves the group out and scales up the other group weights.
Why is an account in a different Marker Value than its total points suggest?
An override applied. Check the Override column in the preview to see which one.
Why didn't my preview update after I changed a rule?
The preview only runs when you click Generate Preview. Click it again to see results for your latest rules.
A preview warning says a condition was treated as not matching. What should I do?
Odie couldn't check that condition, often because its data source isn't connected. Connect the source and generate the preview again, or change the condition.
How is a point-based marker different from Odie's renewal prediction?
Odie's renewal prediction learns from your history which signals matter, and it updates on its own. A point-based marker uses the points and weights you set, for a signal you want to track your own way. Use both: the prediction tells you the likely outcome, and your markers tell you which signals you want to act on.