# Your events, delivered to your own bucket

Bucket export supports gzip JSON Lines or Parquet with quarter-hour delivery once your S3 destination is configured and enabled. Add the bucket policy shown in **Settings > Exports** and test the connection. Only the studio owner can add, change, pause or disable an export. Google Cloud Storage is not currently available.

## Future Google Cloud Storage setup

This provider cannot currently be enabled. When available, grant the studio-specific service account shown in the dialog a custom bucket role with `storage.objects.create` and `storage.objects.delete`, restricted to your export prefix. Replacement permission is needed for delivery retries and hourly manifest updates. No read or list permission is required. The service account must first be provisioned by the platform operator; no customer credential file is uploaded.

## What it costs

Configuration, connection tests and delivery require a positive prepaid balance. Your included event allowance still applies. Each exported event counts as five events on your shared event meter, so 100,000 exported events are 500,000 events, $0.25 once the included allowance is spent. Nothing is charged for an hour with no events, a refused write is refunded, and a retry is never charged twice. Each export has a monthly cap of 20,000,000 exported events by default (set it to 0 for no cap); an export writes up to it and then pauses until the first of next month or until you raise it. If your balance cannot cover the next file, the export pauses with the reason shown, we email the owner once, and it picks up exactly where it stopped once funded. Late-arriving events are picked up by the regular quarter-hour delivery using the time Ravensight received them. No debt is carried.

## Granting S3 access

Ravensight writes as one role and never holds a key of yours. Add this statement to your bucket policy, with the role ARN and studio id the export dialog shows you. The condition pins the role's session name, which ends in your studio's id, so only Ravensight writing on behalf of your studio can use it. It allows writing new objects under your prefix and nothing else: Ravensight never lists, reads or deletes anything in your bucket. Creating the export makes one test write, `/_ravensight_test/.json`, and reports access denied or a missing bucket by name. Connection tests are limited to once per minute for each destination.

```
{
  "Version": "2012-10-17",
  "Statement": [{
    "Sid": "RavensightExport",
    "Effect": "Allow",
    "Principal": { "AWS": "<role ARN from the dialog>" },
    "Action": "s3:PutObject",
    "Resource": "arn:aws:s3:::<your-bucket>/<prefix>/*",
    "Condition": { "StringLike": { "aws:userid": "*:ravensight-export-<studio id>" } }
  }]
}
```

If the bucket encrypts with your own KMS key, name the key in the dialog and allow the same role `kms:GenerateDataKey` on it; otherwise objects are written with S3-managed encryption. We recommend the bucket's Object Ownership setting "Bucket owner enforced" (the default for new buckets), so every exported file is owned by you with no access control lists to manage.

## Layout

One file per page of up to 10,000 events, never crossing a UTC ingestion hour, plus a manifest per hour listing its files and row counts:

```
<prefix>/game_id=<gameId>/dt=2026-10-15/hour=09/1760518800000-1760522400000.jsonl.gz
<prefix>/game_id=<gameId>/dt=2026-10-15/hour=09/_ravensight_manifest.json

{ "schema": 1, "gameId": "<gameId>",
  "files": [ { "file": "1760518800000-1760522400000.jsonl.gz", "rows": 8421, "bytes": 702113 } ] }
```

The folders are named key=value partitions, so a query engine reading the bucket sees `game_id`, `dt` and `hour` as columns. The two numbers in a file name are the page's start and end in epoch milliseconds.

Parquet files use the same partition layout with `.parquet` instead of `.jsonl.gz`, the same manifest and the same price. Their fixed schema has scalar columns, `ts` as TIMESTAMP_MILLIS, nullable typed `rs_*` columns, and `props`, `data` and `rs` as JSON text. Unknown properties and experiment tags remain in the raw JSON rather than adding columns. Invalid typed values remain in raw JSON and do not populate trusted typed columns.

## Row schema

Each JSON line is one event in the same shape as the [raw event export](https://ravensight.io/docs/limits/): `schema` (currently 1), `gameId`, `deviceId`, `sessionId`, `event`, `ts` (epoch milliseconds), `tsIso`, `level`, `platform`, `gameVersion`, `country`, `deviceModel`, `osVersion`, `gpu`, `synthetic`, `props`, `data` (the stored payload text), `rs` (the typed event contract), and `campaign`, `adset` and `creative` (where the device was acquired, null when it was not attributed). Keys are only ever added, so read the ones you know and ignore the rest. Playtest sessions are left out unless you include them.

## Backfill and timing

Choose "include the last 90 days" when you add an export to start from the oldest events Ravensight still keeps; the dialog estimates what that costs first. After that, each quarter hour writes what arrived up to a minute ago.

## Duplicates

A write that succeeded but reported a failure is retried to the same file name, and in rare cases a row can appear in two files. Dedupe on `sessionId`, `ts`, `event` and `data`. Disabling an export keeps every file it wrote.

Owners can also read delivery history through the `list_export_deliveries` MCP tool. It uses the same game and owner permissions as the dashboard, returns up to 50 deliveries per page, and accepts `before` from the returned `nextCursor`. It cannot create, change or start an export. Standard MCP usage charges apply.

Source: https://ravensight.io/docs/bucket-export/
Last updated: 2026-11-15
