Documentation

​
​

Development

User Acquisition

Monetization

Industry

Analytics

Unity SDK

Client API

Analytics

LiveOps
​
​
Analytics
  • Overview
  • Get started
  • Pricing
  • Concepts
  • Tutorials
    • Create a custom event
    • Record an event
    • Record events with a custom user ID
    • Record transaction events
    • Record ad impression events
    • Copy custom events to another environment
    • Create a custom dashboard
    • Edit a custom dashboard
    • Create a funnel
    • Track user acquisition
    • Create a custom audience
    • Run a query with SQL Data Explorer
    • Query parameter values with SQL Data Explorer
    • Optimize SQL Data Explorer queries
    • Set up Data Access
    • Record an event with the REST API
    • Generate a unique user ID with the REST API
    • Request data deletion with the REST API
    • Debug event reporting
    • SDK 5.0.0 migration
    • Migrate to Unity 6.2 with Analytics SDK 6.1.0
    • Request game data deletion
  • Reference
  • Privacy and consent
  • FAQ
  1. Unity Analytics

Run a query with SQL Data Explorer

Create and execute SQL queries on your Analytics data using SQL Data Explorer.
Read time 2 minutes
Last updated 7 months ago

SQL is a programming language used to communicate with databases. A basic understanding of writing SQL queries is required to use SQL Data Explorer. See our collection of "recipes" in the SQL cookbook Data Explorer Queries. Queries are run against Snowflake, so use the Snowflake SQL dialect. Note that non-
SELECT
statements and
$SYSTEM
commands are limited in functionality.
When you first open SQL Data Explorer, a query that counts the number of distinct users who have played your game in the last seven days is shown. You can try this query out or delete it and build your own.
The Glossary panel provides a list of parameters you can use in your query. Use the copy button to copy parameters to the clipboard. The glossary terms are pulled from two sources: the database column names (such as
EVENT_DATE
) and custom parameters parsed from the event json (see Snowflake documentation on how to query JSON data). You can define custom parameters depending on the events you send. Some parameters are fields specific to Snowflake, which can change the syntax in the SQL. A list of available tables and their columns can also be found on the SQL Data Explorer queryable tables page.
Database column names are more performant for querying than the parameters parsed from JSON and should be preferred when possible.
If a parameter is represented by a column (such as
USER_COUNTRY
), the query uses it as:
USER_COUNTRY
If a parameter comes from the event itself, named
missionName
in this example, it's accessed via:
EVENT_JSON:missionName::STRING
For more information about building custom events, see the create a custom event tutorial.
After running a query, you need to set up the chart. You can toggle between a bar chart, line graph, area graph, pie chart, and stacked bar chart. Currently, two Y axes and one X axis are supported.
Tip
To rename an axis label, use the
as
expression in your SQL query.
If you run a query without any data ordering, it's possible that your charts won't be an accurate representation of your data as it's not sorted. A warning will be displayed in this instance and it's recommended to order your query through the use of an
order by
keyword.
Under your chart is a table of results, showing the columns and result of your query.
Use reports to save your queries. The Reports selector provides a list of all saved queries so you can reload and use them later.
Use the Environments selector to switch between Unity Environments.
For information on all the tables and columns available, see the SQL Data Explorer queryable tables page.

Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.


    Report a problem with this page