Avo
  • About
  • Plans
  • Docs
  • Blog
  • Jobs
  • Login
  • Get started
  • About
  • Plans
  • Docs
  • Blog
  • Jobs
  • Login
  • Get started

Issues

The Inspector monitors the health of your current tracking, catching common issues such as missing events or properties, casing inconsistencies, property type mismatches, significant difference in volumes between platforms and many more. The Inspector gives you insights into the health trends of your tracking and email alerts on any regressions. Enabling you to start improving your tracking in a data-driven way.

Here are the issue types that the Inspector can detect. You can enable any subset of them in your project.

Issue Types

Event missing on some platforms

Detects events sent by one platform, but not sent by another. Can be a sign of missing tracking calls.

Example: iOS sends App Opened event, but Android does not.

Property missing on some platforms

Detects properties sent by one platform, but not sent by another.

Example: iOS sends user id with the App Opened event, but Android does not.

Property sometimes missing

Detects absence of event properties across tracking calls.

Example: Property onboarding status is not sent with 30% of the App Opened event.

Property type mismatch

Detects type changes of event properties across tracking calls.

Example: Inconsistent type of property onboarding status on event App Opened: int (84%), string (16%).

Event volume change significant between versions

Detects significant changes in event volume between app versions.

Example: Volume of event App Opened drop by 25% between versions v1.3.2 and v1.3.3 on iOS

Event volume significantly different between platforms

Detects events sent way more frequently by one platform versus another adjusted for sessions number. Can be a sign of duplicated or missing tracking calls.

Example: iOS is sending 10x more volume per session than Android of the App Opened event.

Event name casing (coming soon)

Detects event names spelled in undesirable casing.

Example: Event open_app is snake case, expected title case (Open App).

Property name casing (coming soon)

Detects property names spelled in undesirable casing.

Example: The property onboarding_status on event App Opened is snake_case, expected camel case (onboardingStatus).

Global property type mismatch (coming soon)

Detects properties with identical names and different types across all registered event schemas.

Example: Inconsistent type of property revenue on events Purchase Completed: int and Checkout Completed: string.

Smart Issues (coming soon)

Similar event names

Detects similar event names, that can point to duplicate tracking.

Example: Potentially multiple events describing the same user action: App Opened, App Open, open_app + 2 more events.

Similar property names within event

Detects similar property names in a single event.

Example: Potentially multiple versions of the same property: onboarding_status, onboardingStatus, and Onboarding State.

Unexpected type based on property name

Detects when a property name that is often associated with a specific type has some other type.

Example: Revenue property is string type (expected to be a number).

Global similar property names (low)

Detects similar property names across all registered event schemas.

Example: Potentially multiple versions of the same property: onboarding_status, onboardingStatus, and Onboarding State.

Missing property based on property group pattern

Detects missing property in a group of similarly looking properties.

Example: Property onboarding_status is sent with 4 out of 5 events of the Onboarding events group.