Link and QR activity becomes more useful when it reaches the reporting surface your team already operates. Nimriz now sends mapped events to Google Sheets, Amazon S3, and BigQuery. The three connectors share privacy-aware event mapping and delivery health, but each serves a different operating model.
Use Google Sheets for operator reporting
Google Sheets is the fastest path when campaign operators need a familiar table rather than a warehouse. You configure the table fields shown and connect Google. When Select spreadsheet appears, choose one editable Sheet through Google Picker.
Nimriz initializes the first-row header only when the tab is empty. After that, the header must match exactly. If someone deletes the sheet, renames the tab, or changes the columns, delivery stops safely instead of silently recreating or mutating customer-owned structure.
Google Sheets export is available on Professional and Enterprise plans.
Use Amazon S3 for durable event objects
Amazon S3 fits teams that want customer-owned files for downstream processing. Nimriz writes one newline-terminated NDJSON event per deterministic object key, organized by date, hour, and delivery ID. The customer supplies a bucket, region, access key, secret, and optional prefix.
The recommended IAM policy grants only s3:PutObject for the configured prefix. This keeps the connector focused on append-style delivery without broad bucket administration. S3 is available on Enterprise.
Use BigQuery for warehouse queries
BigQuery fits teams that already maintain a customer-owned table and want events available for SQL, BI, or transformation jobs. Nimriz sends batched insertAll requests with the delivery ID as the stable insertId, handles indexed partial errors, and respects the configured project, dataset, and table.
The customer creates the table and supplies a service-account JSON credential with the required insert permission. Nimriz does not create or mutate the warehouse schema. BigQuery is available on Enterprise.
Map once and verify a real artifact
Each destination supports deterministic field mapping and a real provider test. The test creates an actual row, object, or warehouse record, so the customer can confirm schema and access before live delivery starts. Batch destinations preserve per-item results even when several events share a provider request.
Outbound payloads omit raw IP addresses and complete User-Agent strings. Customer external IDs used for CRM delivery are not added to spreadsheet or warehouse events.
Pick the smallest reporting surface that works
Choose Google Sheets when people need to inspect and share the table directly. Choose S3 when files are the durable handoff. Choose BigQuery when SQL and downstream models are already part of the workflow.
Review the Google Sheets guide, Amazon S3 guide, or BigQuery guide to configure the destination and verify its first artifact.