There are two cases of this issue type:
Example: Property onboarding status is not sent with 30% of the App Opened event.
Detects type changes of event properties across tracking calls.
There are two cases of this issue type:
Example: Inconsistent type of property onboarding status on event App Opened: int (84%), string (16%).
Alert when an event that is not defined in the tracking plan is detected by Inspector
Example: Event Signup Completedd not found in Tracking Plan.
Alert when an property that is not defined in the tracking plan is detected by Inspector
Example: Property authenticationMethod not found in Tracking Plan.
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.
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.
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
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.
Detects event names spelled in undesirable casing.
Example: Event open_app is snake case, expected title case (Open App).
Detects property names spelled in undesirable casing.
Example: The property onboarding_status on event App Opened is snake_case, expected camel case (onboardingStatus).
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.
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.
Detects similar property names in a single event.
Example: Potentially multiple versions of the same property: onboarding_status, onboardingStatus, and Onboarding State.
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).
Detects similar property names across all registered event schemas.
Example: Potentially multiple versions of the same property: onboarding_status, onboardingStatus, and Onboarding State.
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.