Snowflake Reader Account Overview

In this article

Coveo uses the Snowflake Database to store all UA data. Snowflake is powered by a data platform provided as SaaS and runs on cloud infrastructure. It enables clients to explore and export their data as well as create customized exports and materialized views.

In the Coveo Administration Console, the Snowflake reader account enables you to do the same with your Coveo organization data. A reader account grants you direct access to your organization’s data. This feature is unique to every organization and can be accessed by multiple users. Members of the Administrators built-in groups can add users and IP addresses to the reader account.

What’s a Reader Account?

In order to fully take advantage of the reader account, it’s essential to first understand the Snowflake environment. It’s comprised of databases and virtual warehouses. The database is a physical storage space in which the data is secured. The warehouse is the data processing unit that represents the computing power to query the data.

Snowflake and Coveo

This diagram illustrates the architecture that encompasses the Snowflake reader account:

  1. Coveo has one main Snowflake account with its own warehouse.

  2. The main account receives events collected from Coveo-powered search hubs.

  3. The reader account is linked to a single organization and provides a view of the organization data stored in the main account.

  4. BI or ETL tools are integration solutions that facilitate data analysis and let us understand where the queries sent to the database are originating from.

  5. The reader account is linked in the Raw Data (platform-eu | platform-au) page of the Coveo Administration Console.

  6. The Coveo Administration Console reads the data from the database and generates UA reports.

The separate warehouse structure allows for optimal performance and also lets us understand where the queries sent to the database are originating from. Coveo has one main Snowflake account with its own warehouse and generally one reader account linked to each organization. Each reader account has one warehouse that lets users perform their queries as well as connect different tools to their reader account.

The reader account is essentially a microcosm of the main account, since it provides a direct view of live data. The key difference is that a single reader account exclusively provides access to data for a specific organization. When you connect to the reader account, it gives you access to the live data from your organization.

Notes
  • In most cases, there’s no need to export data to a CSV file as you would with UA data exports. With the reader account, you can query all data tables, including those for:

    • Server-side events

    • Incoherent events

    • Page views

    • Search impressions

  • The date and time for every event in the Snowflake database are in GMT.

Furthermore, you can configure one of several integration solutions to better access your data, such as Tableau™, Power BI™, or Informatica™.

Note
  • We recommend using a BI or an ETL tool to facilitate your data retrieval. Alternatively, you can use a native Snowflake connector, such as the Snowflake Python™ connector, though this is recommended for developers. For more information, see Snowflake’s documentation on data integration solutions and connectors.

  • Although the Snowflake Partner Connect feature is available to clients with their own Snowflake account using the ACCOUNTADMIN role , it isn’t available to those using the reader account since the ACCOUNTADMIN role can’t be granted to reader account users.