Event Catalog & Tracking Plan
Auto-discovered events, inferred property types, top values for pickers, and a tracking plan you can enforce in CI.
CollectExplore Event catalog
Collect
Instrument once. Every surface lands in one event store.
SDKs for web, iOS, Android, React Native, Flutter and server, with offline queues, consent gating and automatic lifecycle events.
accepted 12,480deduped 31quarantined 4last hour
Overview
Time to first event is the most winnable number in this category. Edverix ships typed SDKs for every client surface and a server-side API, all writing to one schema. Events queue on the device, deliver when the network returns, and deduplicate on the way in, so a retry never double-counts a purchase.
Only on Edverix
- Live integration debuggerOnly on Edverix
Watch raw payloads and validation results arrive while you are still wiring the SDK.
- Ingestion error streamOnly on Edverix
Rejected payloads by count, type, source and time, so a broken release surfaces in hours, not at quarter close.
Capabilities
Everything in Data collection
21 capabilities in 5 groups, organised the way the product is.
Client SDKs
One event model across every platform you ship on.
Web JavaScript
Lightweight browser SDK with first-party storage, page and session tracking, and a transport that batches and retries.
React and Next.js
Provider and hooks that follow route changes and expose identify, track and consent as typed calls.
iOS and Android
Native SDKs for push tokens, in-app rendering, notification channels and privacy manifests.
React Native and Flutter
Cross-platform SDKs that report the real platform (ios or android) and keep the framework in device metadata.
Cordova, Ionic, Capacitor and Unity
Wrappers for hybrid and game engines so no surface is left untracked.
Connected TV
Android TV, Fire TV, Apple TV, Tizen and webOS targets for media and OTT teams.
Server and batch ingestion
Server-side ingest API
Purchases, refunds, subscription changes and fulfilment events land where they actually happen: on your backend.
Bulk import and CSV upload
Backfill history and correct records without engineering time; every upload is validated against the schema.
Scheduled S3, SFTP and warehouse import
Pull users and events from Snowflake, BigQuery, Databricks or Redshift on a schedule.
CDP and tag-manager connectors
Add Edverix as a destination in Segment, RudderStack or mParticle, or instrument through a tag manager container.
Reliability and privacy
Offline queue with retry and dedupe
Events persist on the device and deliver in order; each carries an id so at-least-once delivery is safe.
Consent gating
Tracking is gated on consent state inside the SDK, so the privacy review is not a retrofit.
PII redaction at the door
Anything resembling a password, card number or token is replaced before it is stored.
First-party tracking domain
Serve the SDK and collect from your own domain so ad blockers do not silently erase your data.
Automatic events
Lifecycle without code
Install, update, launch, session start and end, and crash arrive automatically on mobile.
Uninstall tracking
A scheduled silent push probe detects removed apps and records an uninstall event per device.
Notification lifecycle
Sent, delivered, opened, dismissed and clicked are events like any other, joinable to everything else.
E-commerce spec on day one
Typed helpers from product viewed to refund created, so revenue reports populate before anyone designs a taxonomy.
Integration experience
Live integration debuggerOnly on Edverix
Watch raw payloads and validation results arrive while you are still wiring the SDK.
Ingestion error streamOnly on Edverix
Rejected payloads by count, type, source and time, so a broken release surfaces in hours, not at quarter close.
Multi-project keys
Projects under one organization, each with its own keys, catalog and data, so staging never pollutes production.
FAQ
Questions about Data collection
How long does a first integration take?
A web or React app sends its first event in under an hour. Mobile apps that need push add a native SDK and a Firebase or APNs credential. The live debugger shows every payload as it arrives so you never wait for a report to know it worked.
Do we have to design an event taxonomy first?
No. The catalog discovers events and infers property types as they arrive. Teams that want a contract can add a tracking plan later and enforce it in CI.
What happens to events sent while a phone is offline?
They are queued on the device, delivered in order when the network returns, and deduplicated on ingestion using the event id the SDK assigned.
Get started
See Data collection 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