Metrickle

Where your data is stored, and getting it out

Last updated

Metrickle keeps two kinds of data in different places: the analytics data your apps send, and the account details that run your workspace. This page explains where each one lives, how EU data location works, and how to get your raw events out into your own warehouse or scripts.

What is stored where

DataWhere it’s stored
Events, including survey answersYour workspace’s data location
Session replay recordings and the index that lists themYour workspace’s data location
Feedback screenshotsYour workspace’s data location
Heatmap page snapshotsYour workspace’s data location
Hosted warehouse export filesYour workspace’s data location
Account details: sign-in, workspaces, members and billingOne global account database
App and survey settingsOne global account database
Feedback message textOne global account database, for now
Study participants' contact detailsOne global account database, for now
The evidence in casesOne global account database, for now
Accessibility scan results, from CI or visitors' browsersOne global account database, for now
Protected task verdicts and what each gap costs (totals and rates, nothing about any one person)One global account database

Analytics data is stored in Cloudflare D1 and R2 storage. A workspace’s analytics data is all kept in one location.

Standard data location

By default, a workspace’s data location is Standard (no jurisdiction). The storage has no jurisdiction restriction, so Cloudflare decides where it sits.

To see your workspace’s data location, open Team & workspace and look at the plan summary. It shows Data location with the current setting.

EU data location

EU data location keeps your workspace’s analytics data in the European Union, in storage created with Cloudflare’s EU jurisdiction. It comes with the Pro, Agency and Enterprise plans.

To use it, email chris@metrickle.com before you install Metrickle.

How it works:

  • Ask before you install. The data location has to be set before your workspace’s first data arrives. Metrickle sets it for you; there’s no switch in the dashboard.
  • Stored data isn’t moved automatically. Once a workspace has any events, replays, screenshots or snapshots, its data location can’t simply be changed.
  • Account details stay global. Sign-in, members, billing, and app and survey settings stay in the global account database, wherever your analytics data is. So do protected task verdicts: totals and rates such as what a gap costs, never anything about one person. For now so do feedback message text, study participants' contact details and the evidence in cases. Only the analytics data in the table above is kept in the EU.

Export your raw events

The Data export page sends your workspace’s raw events to your own warehouse every day, or lets your scripts read them with the query API. It’s on the Pro, Agency and Enterprise plans.

To see the page, your role needs Export raw events, with user ids and properties. Owners, admins and members have it; viewers don’t. Only owners and admins can change where data is exported.

Daily warehouse export

Every day after 04:00 UTC, yesterday’s events, and any that arrived late, are written as gzipped JSON lines, one folder per app and day.

To set it up:

  1. Open the workspace menu at the top of the sidebar and choose Data export.
  2. Under Daily warehouse export, select Export every day.
  3. Set Start from to the first day to export. The first run fills in every day since then, a week at a time.
  4. Under Where the files go, choose Metrickle-hosted files, or Your own bucket to also copy them to an S3-compatible bucket you own, such as Amazon S3, Cloudflare R2 or Google Cloud Storage.
  5. For your own bucket, fill in the Endpoint URL, Bucket, Region, Access key ID and Secret access key, then choose Test connection.
  6. Choose Save export settings.

To pause the export, clear Export every day and choose Save export settings. Pausing keeps the settings and picks up where it left off.

Recent runs lists each export. Hosted files are kept for a limited time, shown on the page, and every download is recorded in the audit log. The page also has loading recipes for BigQuery and Snowflake, filled in with your bucket and folder.

When you erase a person’s data in Metrickle, their events are deleted at once. Files already exported can’t be changed, so the next run writes an erasures file, and the recipes show how to apply it.

For file formats and loading steps, see warehouse export.

Query API

The query API reads raw events and aggregates from scripts, notebooks and BI tools, a page at a time. It uses an API token. See query API and API tokens.