Fine-grained control over
analytics events
Govern, transform, filter, and route logs & analytics events from your apps
to multiple destinations,
without redeployments.
Platform agnostic
Works everywhereCurrently supports JavaScript environments, with more SDKs planned in future
Everything you need
Open Source & vendor agnosticFunctionalities carefully assembled together keeping real world use cases in mind, with a platform and vendor agnostic approach.
- Track once, send anywhere
- Route your tracked events conditionally to multiple different destinations via remote configuration.
- Single source of truth
- Define and manage your events in one place, for consistency and organization-wide awareness.
- Transformations
- Manipulate payloads before transporting them over to your destinations based on remote configuration.
- Effects
- Handle custom side-effects in your application via modules that are triggered by certain events and conditions.
- Multiple environments
- Manage multiple projects in one place, per each environment, for incremental risk free deployments.
- Data enrichment
- Enrich your tracked events with additional data on demand via modular lookups, without needing to change your existing code.
- Sampling
- Sample a certain percentage of your tracked events based on detailed conditions, saving ingestion costs and bandwidth.
- Tagging
- Tag your definitions accordingly so you only load the ones you need and nothing more, to keep your applications free of bloat.
- Vendor agnostic
- Integrate with as many third-party analytics and logging services as you want, without being tied to any specific one.
- Runtime validation
- Let teams know immediately when they are sending data in wrong shapes or about deprecations, before ingesting them anywhere.
- Testing
- Test your definitions before deploying them to gain maximum confidence.
- Universal SDKs
- Use JavaScript SDK in both Node.js and the browser, with more SDKs planned in future.
Manage with Git
Streamlined workflow for teams
Three simple steps to visualize the workflow:
- 1. Send Pull Requests
Your team sends Pull Requests to your Eventvisor project repository updating events, attributes, and/or destination definitions.
- 2. Build and upload to CDN
Upon merging your Pull Request, trigger your CI/CD pipeline to build the datafiles (static JSON files) and upload them to your CDN or custom server.
- 3. Fetch and track with SDKs
Fetch the datafiles from your applications and/or services, and start tracking events using provided Eventvisor SDKs.
Real world scenarios
...
Bring Product, Engineering, Data, and Marketing folks together in one workflow.
Conditionally route your events to multiple different vendors, either first or third-party.
Gradually migrate from one vendor to another with ease.
Apply advanced filtering and sampling to reduce ingestion costs.
Filter your tracked events before processing them further.
Get validation warnings if wrong shapes of data are tracked.
Bring marketing pixels into the same workflow for full visibility and control.
Deprecate events and attributes gracefully, allowing developers to clean things up at their own pace.
Bring order in your microfrontends architecture for overlapping cross-team analytics events.
Control the flow of tracked events from your applications without the need to redeploy them.
Transform and enrich your data with advanced lookups, without needing to change your existing code.
Establish ownership and boundary for your analytics events in a cross-team environment.