Measurement Types
When you set a dev item to “VEKTIS measures it for me”, you pick a Value Type. It tells VEKTIS what kind of number to produce from the activity your product sends, and it decides what else you need to fill in — some types need one action name, some need two, and two need nothing at all.
You pick it once, when you configure tracking. Everything after that happens on its own.
The five types
Section titled “The five types”| Value Type | What it measures | What you configure |
|---|---|---|
| Count occurrences | How many times the action happens per period | Action name |
| Conversion rate | The share of customers who complete one action after starting another | Numerator action and Denominator action |
| Time to complete | The average time between two paired actions | Start action and End action |
| Overall activity | How many customers use the feature and how deeply they use it | Nothing |
| Revenue (manual) | Revenue, cost, or spend — entered by hand | Nothing |
Choosing the right one
Section titled “Choosing the right one”| If you want to know… | Pick |
|---|---|
| Is anyone using this? How often? | Count occurrences |
| Do people who start this actually finish it? | Conversion rate |
| Did this get faster? | Time to complete |
| Is this feature pulling its weight overall? | Overall activity |
| What is this worth in money? | Revenue (manual) |
If you’re not sure, Count occurrences is the safe first choice. It answers the most common question and needs the least setup.
What you configure
Section titled “What you configure”An action name is the label your product attaches when a customer does something — exported, checkout-completed, invite-sent. You type it into the dev item, your product sends the same string, and VEKTIS matches them up.
The match is exact. Capital letters, dashes and underscores all count, and a name typed one way here and sent another way from your product will never produce a number. Keep names to 200 characters or fewer.
Count occurrences
Section titled “Count occurrences”One field: Action name. VEKTIS counts how many times that action arrives.
It counts occurrences, not customers — ten from one customer count as ten.
Conversion rate
Section titled “Conversion rate”Two fields, and they need to be two different action names:
- Denominator action — the one your product sends when someone starts.
- Numerator action — the one it sends when they succeed.
VEKTIS divides the customers who succeeded by the customers who started. It counts each customer once on each side, so someone who retries five times doesn’t skew the rate.
If both fields carry the same name, the rate sits at 100% and never moves.
Time to complete
Section titled “Time to complete”Two fields, again two different names:
- Start action — sent when the work begins.
- End action — sent when it finishes.
VEKTIS measures the gap between them for each customer and averages the results. Nobody has to time anything or send a duration — the two markers are enough.
Attempts that start in one week and finish in the next are left out of the average, so this type fits work that completes in minutes or hours rather than days.
Overall activity
Section titled “Overall activity”Nothing to configure — no action names to keep in sync, no fields to fill in. VEKTIS combines how many of your customers reached the feature with how much they did once they got there.
Pick it when a feature doesn’t have one obvious action worth counting, or when you want a single number for “is this feature earning its place.”
The trade-off for that simplicity: Overall activity is measured across your customer base as a whole, so it has no Customer Breakdown. If you need to see which customers a release moved, pick Count occurrences or Time to complete instead.
Revenue (manual)
Section titled “Revenue (manual)”Currency metrics require manual data entry. You add each measurement yourself, the same way you would for a dev item set to “I’ll enter results myself.”
Automated revenue tracking arrives with CRM integration.
Common questions
Section titled “Common questions”Can I change the Value Type later? Yes. Open the dev item, change it under “How should VEKTIS measure this?”, and fill in whatever action names the new type needs. Measurements already recorded stay where they are.
I picked a type and nothing is showing up. Open the dev item. If the action name you typed doesn’t match what your product is sending, VEKTIS says so and lists the names actually arriving, so you can see the two side by side. Fix whichever one is wrong.
Which type gives the most reliable score? The one that matches what you’re actually trying to prove. A Count occurrences metric on a well-chosen action beats a Conversion rate built from two actions nobody is sending.
Do I need to tell my engineers which type I picked? Yes — the action names have to match on both sides. Send them the dev item, or point them at the server-side ingest guide, which covers what to send for each type.
Related
Section titled “Related”- Choosing how VEKTIS measures it — where you pick the measurement type
- Feature IDs — the tag that connects your product’s activity to the dev item
- Metric Value Types — how a metric’s number is displayed once VEKTIS has it
- Server-side event ingest — the engineer-facing guide to sending the activity