Stream Nimriz events into BigQuery

Send mapped link, QR, card, and conversion rows to a customer-owned table with stable insert IDs and independent row results.

Read setup docs All integrations

Link clicks
QR scans
Card events
Conversions

Event flow

Async delivery

Nimriz eventsMapped batchBigQuery table

Nimrizredact · filter · map

BigQuery

Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.

Why BigQuery with Nimriz

Stream event rows into the warehouse your analysts already use. Nimriz keeps batches off the redirect path, preserves row-level outcomes, and provides a documented default schema you can adapt to mapping changes.

Row-level delivery truth

Indexed BigQuery errors map back to individual Nimriz deliveries, so valid rows do not repeat with rejected siblings.

Stable insert identity

Each row uses its delivery ID as insertId for best-effort provider deduplication.

Scoped service account

Use a key limited to the intended dataset and verify it with a real streaming row before enabling.

Under the hood

What Nimriz sends, and how.

Use a scoped service account to stream mapped batches through BigQuery tabledata.insertAll.

Plan note

BigQuery streaming export is available on Enterprise plans.

Delivery: Batched tabledata.insertAll requests
Batch bound: Up to 100 rows or the shared 4 MiB payload ceiling
Schema: Customer-created table matching the mapped payload
Errors: Independent indexed row results, including HTTP 200 responses with insertErrors

Guided setup

Connected in four reviewed steps.

01
Create the table
Use the documented schema or one matching your custom mapping.
02
Add a scoped key
Paste a service-account JSON key and target identifiers.
03
Insert a test row
Confirm a real sample row reaches the selected table.
04
Enable delivery
Nimriz enables delivery after the saved key, table, and mapping pass the real test.

Use cases

Warehouse reporting
Attribution analysis
Customer-owned transformations

Privacy notes

Privacy-aware rows omit customer external IDs used for CRM delivery, raw IP, and complete User-Agent strings.

Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.

Analytics privacy docs

Pair BigQuery with the rest of the catalog.

Live

Google Sheets

Keep an operator-friendly event table in a spreadsheet your team owns, with deterministic columns, managed Google authorization, and safe header checks.