snake_case everywhere
All event names and property keys use snake_case. No camelCase, no PascalCase, no kebab-case.
Event Catalog — Domain Event Dictionary
Purpose
Section titled “Purpose”This catalog provides ready-to-use event definitions for the most common business verticals. Each domain page includes event names, properties, lifecycle stage mapping, and volume classification.
Use this as your primary reference when instrumenting your product with GrowthOS. Instead of inventing event names from scratch, find your domain below, copy the schemas that apply, and customize the properties to match your data model.
How to Use This Catalog
Section titled “How to Use This Catalog”-
Find your domain (or the closest match) in the directory below.
-
Start with Cross-Domain Universal events — these are required for every GrowthOS installation regardless of vertical.
-
Add domain-specific events from your vertical’s page. Each page organizes events by growth loop stage (Acquire, Activate, Engage, Monetise, Advocate).
-
Customize properties — the schemas here are a starting template. Add properties that matter to your business and remove ones that do not apply.
-
Follow naming conventions from the Event Schema page to keep your taxonomy clean and automations reliable.
Naming Conventions
Section titled “Naming Conventions”A quick recap of the rules that apply to every event in this catalog.
object.action pattern
Domain events follow object.action naming — e.g., order.completed, subscription.upgraded, feature.activated.
$ prefix = system only
Events starting with $ (e.g., $page_view, $session_start) are auto-tracked by the SDK. Never use the $ prefix for custom events.
Custom events = no prefix
Developer-defined events are free-form within the naming rules. No $ prefix, no reserved words.
Volume Classification
Section titled “Volume Classification”Each event in the catalog is tagged with a volume badge indicating expected frequency and recommended processing strategy.
| Badge | Meaning | Processing Guidance |
|---|---|---|
| High | Auto-tracked or very frequent user actions | Use batching and sampling; avoid storing raw payloads long-term |
| Medium | Regular user actions | Standard processing pipeline; index key properties |
| Low | Rare events (conversions, lifecycle changes) | Fully processed; store complete payloads; trigger automations |
| Low (admin) | Operational and internal events | Admin dashboards only; not exposed to end-user analytics |
Domain Directory
Section titled “Domain Directory” Cross-Domain Universal Required for all domains — authentication, billing, support, notifications, consent, and lifecycle signals. Start here.
SaaS / B2B Software Trials, onboarding, feature adoption, team collaboration, API usage, and subscription management.
E-Commerce / D2C Product discovery, cart management, checkout, order lifecycle, returns, reviews, and loyalty programs.
Fintech / Banking Account management, transactions, lending, card operations, and compliance events.
Insurance / InsurTech Quote generation, policy lifecycle, claims, renewals, and underwriting events.
EdTech / Online Learning Course enrollment, lesson progress, assessments, certificates, and instructor events.
Healthcare / HealthTech Appointments, consultations, prescriptions, health records, and telehealth events.
Marketplace / Platform Listings, bookings, transactions, ratings, disputes, and seller/buyer lifecycle events.
Media / Streaming Content playback, subscriptions, playlists, recommendations, and ad engagement events.
Real Estate / PropTech Listings, property views, tours, applications, leases, and maintenance events.
HR Tech / Recruitment Job postings, applications, interviews, hiring, onboarding, and employee engagement events.
Logistics / Supply Chain Shipments, warehouse operations, fleet tracking, delivery, and inventory events.
Gaming Player progression, in-app purchases, matchmaking, achievements, and social events.
Event Count Summary
Section titled “Event Count Summary”A quick overview of events per domain and the recommended starting set.
| Domain | Total Events | Recommended Starting Events |
|---|---|---|
| Cross-Domain Universal | 44 | All 44 (required baseline) |
| SaaS / B2B Software | 47 | onboarding.completed, feature.activated, subscription.created, invite.sent |
| E-Commerce / D2C | 46 | product.viewed, product.added_to_cart, checkout.started, order.completed |
| Fintech / Banking | ~40 | account.created, transaction.completed, kyc.completed, loan.applied |
| Insurance / InsurTech | ~35 | quote.generated, policy.purchased, claim.submitted, renewal.completed |
| EdTech / Online Learning | ~38 | course.enrolled, lesson.completed, assessment.submitted, certificate.earned |
| Healthcare / HealthTech | ~36 | appointment.booked, consultation.completed, prescription.created, record.accessed |
| Marketplace / Platform | ~42 | listing.created, booking.completed, transaction.completed, review.submitted |
| Media / Streaming | ~38 | content.played, subscription.created, playlist.created, ad.clicked |
| Real Estate / PropTech | ~34 | listing.viewed, tour.scheduled, application.submitted, lease.signed |
| HR Tech / Recruitment | ~36 | job.posted, application.submitted, interview.scheduled, offer.accepted |
| Logistics / Supply Chain | ~35 | shipment.created, delivery.completed, inventory.updated, route.optimized |
| Gaming | ~40 | level.completed, purchase.completed, match.started, achievement.unlocked |
Next Steps
Section titled “Next Steps” Event Schema & Taxonomy The canonical event envelope structure, naming rules, reserved system events, and best practices.
Ingest API Reference Send events via the track, identify, and page endpoints.
SDKs & Components Client and server SDKs that auto-track system events and simplify custom event tracking.