Data Collection & SDKs
SDKs for web, iOS, Android, React Native, Flutter and server, with offline queues, consent gating and automatic lifecycle events.
CollectExplore Data collection
Collect
Your event schema builds itself, then enforces itself.
Auto-discovered events, inferred property types, top values for pickers, and a tracking plan you can enforce in CI.
EventStatus7d volumeProperties · inferred type
- product_viewedactivesku: stringprice: numbercategory: stringtop categoryfootwear · 41%bags · 23%watches · 12%
- order_completedactiveorder_id: stringrevenue: numberitems: number
- checkout_startedactivecart_total: numberstep: string
- cart_abandoned_v1deprecatedcart_id: string
- debug_pingblockeddropped at the door
tracking-plan.yaml · pull request #212checking…
@@ events/coupon_applied @@+ coupon_applied.coupon_code: string (required)
Overview
Instrumentation rots everywhere because nothing enforces it. Edverix discovers every event and property as it arrives, records the most common values so filters offer a picker instead of a guessing game, and lets you turn that catalog into a contract: violations are quarantined, types are generated, and schema changes show up as a diff in a pull request.
Only on Edverix
- Top values for pickersOnly on Edverix
The most frequent value of every property, ordered by frequency, so segment and funnel filters suggest real values.
- Contract enforced in CIOnly on Edverix
Define the plan once; pull requests that change instrumentation show the schema diff and fail on violations.
- Typed code generationOnly on Edverix
TypeScript, Swift and Kotlin types generated from the plan, so a misspelled property is a compile error.
Capabilities
Everything in Event catalog
11 capabilities in 3 groups, organised the way the product is.
Discovery
Auto-discovered catalog
Every event name, property and inferred type, maintained during ingestion without a separate scan.
Top values for pickersOnly on Edverix
The most frequent value of every property, ordered by frequency, so segment and funnel filters suggest real values.
Per-event volume and last seen
See which events are firing, how often, and when each was last received.
Descriptions and ownership
Document what an event means and who owns it, with AI-drafted descriptions you can accept or edit.
Governance
Active, deprecated, blocked
Retire an event without deleting history, or block one so mistaken sends are dropped at the door.
Mandatory property validation
Reject or quarantine events missing required fields rather than silently accepting them.
Per-event retention
Different lifetimes per event type, the lever that makes long lookback affordable.
Schema export with references
Every event and property, and which segments, journeys and reports reference it.
Tracking plan as code
Contract enforced in CIOnly on Edverix
Define the plan once; pull requests that change instrumentation show the schema diff and fail on violations.
Typed code generationOnly on Edverix
TypeScript, Swift and Kotlin types generated from the plan, so a misspelled property is a compile error.
Drift alerts
A rename that would kill a funnel is caught the day it ships, not at quarter close.
FAQ
Questions about Event catalog
Do we need a tracking plan to get started?
No. Discovery works from the first event. The plan is optional and can be adopted incrementally, one event at a time.
What happens to an event that violates the plan?
You choose per event: accept and flag, quarantine for review, or reject. Quarantined events are replayable once the schema is fixed.
Get started
See Event catalog on your own data.
Send your first event in an hour, simulate your first journey against real history, and keep every byte of it in a database you can query.
- No credit card for the Developer plan
- Bring your own providers
- Export everything, any time