Claim and evidence
Define which events and properties you track, how they are named and how they fit together before instrumenting.
No dated example yet. Treat this tactic as a hypothesis.
Vendor claim
A tool vendor reports numbers about its own customers or product. Useful, but not independent.
Working · 2026-11 Amplitude docs updated 2026-09-09; the same principle appears in other analytics tools but those pages were not fetched.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
Consistent names prevent duplicate and unusable events when several teams send data. Starting from business goals keeps the plan lean.
How to run it
- Define business objectives
- Break key metrics into events
- Set one naming convention with consistent casing
- Define properties consistently across events
- Review and version the plan with developers
Ways to run it
Design options to test, not promised results.
- Option AObject-action names
Name every event as an object plus a past-tense action with one fixed casing.
- Option BShared property dictionary
Define each property once and reuse the same name and type across all events.
- Option CVersioned tracking plan
Keep the plan in a reviewed, versioned document that developers sign off before instrumenting.
Dated examples
No dated example yet. Treat this tactic as a hypothesis.
Does it still work?
Amplitude docs updated 2026-09-09; the same principle appears in other analytics tools but those pages were not fetched. source
Risks
- Inconsistent casing creates separate events
- Over-tracking creates clutter
Sources
- amplitude.com
“A taxonomy defines which events and properties you track, what you name them, and how they fit together.”
✓ quote checked word-for-word on the page - amplitude.com
“Amplitude captures `Song Played` and `song played` as two separate events.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (ops-ai)