Data tracked by Objectiv adheres to an open, standardized taxonomy. This means it's well-structured & self-descriptive, and can be validated at the first step of the pipeline. Objectiv provides several tools to catch errors before data starts flowing in, outlined below.
During instrumentation, you'll get inline documentation for every function, and linting for any validation issues: unknown tagging/tracking calls, missing properties, or wrongly typed properties.
Example inline error in IDE:
When you run your application, any validation errors are caught by the Objectiv debugger, and displayed in the browser console:
- Errors: Warnings are thrown for unknown tagging/tracking calls, missing properties, or wrongly typed properties.
- Uniqueness: If an Event
idand its Location Stack are not unique, an Error is thrown. In the browser console, the error can be hovered/clicked to identify the existing and colliding Elements. See Locations - Solving Collisions for an example.
For more background, see the Collector docs.
Check out this how-to guide on how to configure logging.