Skip to main content

Data export

The Data export module lets you download the platform's raw records for your own analyses — spreadsheets, BI, data warehouses. Exports are prepared in the background, and the finished file stays available for download for 7 days.

What it's for​

  • File export — raw records in CSV, JSONL or XLSX; exporting several datasets at once produces a ZIP archive.
  • Datasets grouped like the modules: brand visibility (checks, cited sources), products, attribution/orders, infrastructure (bots, AI traffic, crawl).
  • BigQuery Sync (Enterprise) — daily incremental synchronization of your data into your own Google BigQuery project.

Export is available in every package, but each dataset is gated by package — e.g. the Brand package sees visibility and infrastructure datasets, while order datasets require a package with attribution.

How to start​

Exports are run by the account administrator (client_admin role). Think about what you need: for a quick spreadsheet analysis, an XLSX with a date range is enough; to feed your own database — JSONL without a range (all records up to the limit).

Step by step​

  1. Open Data export.
  2. Select the datasets (at least one) and pick a format.
  3. (Optional) set a date range — without one we export all records up to the limit.
  4. Click "Create export". The job is queued; you can track progress in the "Your exports" table.
  5. When the file is ready you'll get an e-mail — download it from the table within 7 days, after which it's automatically deleted.
BigQuery Sync (Enterprise)

In the BigQuery Sync tab you connect your own GCP project (service account + dataset). Once configured, data syncs incrementally every day; you can also trigger a sync manually. A step-by-step guide is available in the configuration panel.

FAQ​

Does the export contain AI cost data? No — exports contain substantive data (checks, citations, orders, bot traffic). Cost summaries live in the Cost Center, which has its own CSV export.

Why can't I see a certain dataset? The dataset belongs to a module outside your package (e.g. orders without the attribution module) — or your role lacks export permissions.

How large can an export be? Each dataset has a per-job record limit. For bigger needs, narrow the date range and split the export into batches — or (Enterprise) use BigQuery Sync, which doesn't have this constraint.

What happens to the file after 7 days? It's permanently deleted from the server. You can re-create the export at any time.