> For the complete documentation index, see [llms.txt](https://lionstudios.gitbook.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lionstudios.gitbook.io/readme/analytics/validation.md).

# 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):

* [LionPortal LionAnalytics QA Tool](/readme/analytics/validation/lion-analytics-qa-tool.md): 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.

{% hint style="warning" %}
**This method requires LionPortal access. If you currently do not have access, please contact your Lion Studios Product Manager.**
{% endhint %}

* [**Looker Events QA Explore**](/readme/analytics/validation/looker-events-qa.md): 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.

{% hint style="warning" %}
**This method requires Looker access. If you currently do not have access, please contact your Lion Studios Product Manager.**
{% endhint %}

## 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.

***

[Lion Analytics QA Tool](/readme/analytics/validation/lion-analytics-qa-tool.md)

[Looker Events QA](/readme/analytics/validation/looker-events-qa.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://lionstudios.gitbook.io/readme/analytics/validation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.