Validation

Introduction

Event validation is crucial to ensure that LionAnalytics events are implemented correctly. Failure to validate can result in releases with incorrect instrumentation, making it impossible to extract insights and causing Looker dashboards to malfunction. To prevent such issues, it is essential to validate events during development, before submission to internal QA, and finally, provide a detailed validation document to our QA team with instructions and logic.

Methods of Validation

Choose either option (whichever one is easier for you):

  1. LionPortal LionAnalytics QA Tool: Use the LionPortal QA tool to view the event stream from a registered device in near-real-time. This tool provides multiple search and filter options, export, and sharing capabilities. Each submission creates a unique URL that can be shared across platforms like Slack, Asana, or Salesforce.
    • How to Access: Navigate to LionPortal → Support → Lion Analytics QA to display recent events fired from your device.
    • Features: View the event stream in near-real-time (less than 1 minute delay), search and filter options, export and sharing capabilities.
  1. Looker Events QA Explore: This Looker Explore shows an aggregate view of the entire user base for the events and parameters fired. Note that this data is not real-time and there is a delay between when events are fired and when they appear on the dashboard. Use the provided links to view both the list of events and the parameters for selected events.
    • How to Access: Use the provided Looker Events QA links to validate your events and parameters.
    • Features: Aggregate view of events and parameters, delayed data updates, access to a list of events and their parameters.

Requirements of Validation

Regardless of the tool you choose, ensure the following for each implemented event:

  • The event name appears on the tool.
  • The required parameters of the events are present.

Validation Workflow

  1. During Development: Validate events using the LionPortal QA tool or Looker Explore in Unity.
  2. Before Submission: Validate events through internal QA, ensuring all events and parameters are correctly implemented.
  3. Submission to QA: Provide a detailed validation document to our QA team, including instructions and the logic behind the events.