Tracking ObservabilityIssue Types

Issue Types in Avo Inspector

Event unexpected by tracking plan

Detects events that are not defined in the tracking plan

Example: Event Signup Completed not found in Tracking Plan.

Event unexpected on source

Detects events that are not expected from a specific source according to the Tracking Plan

Example: Event unexpected on iOS by tracking plan

Property type does not match tracking plan

Detects properties with different types than defined in the tracking plan

Example: Property seen as bool but expected as string.

Property type inconsistent

Detects properties seen with multiple different types

Example: Property types seen: object, string.

Property unexpected on event

Detects properties on events where they are not expected according to the tracking plan

Example: Property unexpected on event by tracking plan

Required property sometimes missing from event

Detects properties that are required in the tracking plan but sometimes missing

Example: Property set as always sent on “App Opened” in tracking plan but missing on event

Upcoming Issue Types in Avo Inspector

Here are some of the issue types we’re planning on adding in the future. Reach out if you’d like to see any of these sooner than others.

Event missing on some sources (coming soon)

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 sources (coming soon)

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.

Event volume change significant between versions (coming soon)

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 sources (coming soon)

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 bundle pattern

Detects missing property in a bundle of similarly looking properties.

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

Issues ViewFind Issues