> ## Documentation Index
> Fetch the complete documentation index at: https://docs.innkeepr.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Google BigQuery

> [card] Connection Info
>
> The Google BigQuery Connection is an **Events**, **Profiles**, and **Attribution** connection.
>
> * **Events:** Sends events, such as page views or orders, to Innkeepr.
> * **Profiles:** Adds traits, such as email addresses or phone numbers, to Profiles.
> * **Attribution:** Sends conversions with the campaigns they are attributed to.

[Google BigQuery](https://cloud.google.com/bigquery) is Google Cloud's data warehouse. Add BigQuery as a Connection to Innkeepr to use data that already lives in your warehouse, without additional tracking on your website.

## Getting Started

1. From your workspace's **Connections** page, click **Add connection**.
2. Choose **Google BigQuery**.
3. Enter your **Google Cloud project ID**.
4. Innkeepr creates a service account for your workspace and shows its email address. It looks like this: `ws-<workspace-id>@innkeepr-bigquery.iam.gserviceaccount.com`
5. Give this service account the roles listed under [Permissions](#permissions) in your project.
6. Innkeepr checks that the service account can list your datasets and run queries.
7. Map the columns of each table Innkeepr should read (see below).
8. Click **Save**.

## Map tables to events

Innkeepr reads only the tables you map. For each table, you define which column holds what:

| Field | Required | Description |
| :- | :- | :- |
| `id` | Yes | Unique ID of the row. Innkeepr uses it as the event ID. |
| `created` | Yes | Timestamp of the event |
| `name` | No | Name of the event, for example `checkout_completed` |
| `properties` | No | Properties of the event, for example `revenue` or `order_id`. Nested columns are supported. |

**Example**

This row in your table:

```json theme={null}
{
  "id": "a1b2c3",
  "created_timestamp": "2026-11-18T14:32:00Z",
  "event_name": "checkout_completed",
  "attributes": {
    "revenue": 200,
    "order_id": "abcdef"
  }
}
```

with this mapping:

```json theme={null}
{
  "id": "id",
  "created": "created_timestamp",
  "mappings": [
    { "source": ["event_name"], "target": ["name"] },
    { "source": ["attributes"], "target": ["properties"] }
  ]
}
```

becomes this event in Innkeepr:

```json theme={null}
{
  "type": "track",
  "name": "checkout_completed",
  "properties": {
    "revenue": 200,
    "order_id": "abcdef"
  }
}
```

Use the event names and properties from the [Innkeepr Spec](https://docs.innkeepr.ai/connections/spec-overview.md), so Innkeepr can use the events for Objectives and Signals.

## Sync

Innkeepr reads your mapped tables once a night, one day at a time, with standard SQL queries. Columns that are not in the mapping are ignored.

The queries run as jobs in your Google Cloud project, so BigQuery bills them to your project.

## Permissions

Grant the Innkeepr service account these roles in your project, in **Google Cloud Console** > **IAM & Admin** > **IAM**:

| Role | Why |
| :- | :- |
| **BigQuery Data Viewer** | List datasets and read the mapped tables |
| **BigQuery Job User** | Run the queries that read the tables |

Innkeepr only reads. It does not create, change, or delete tables.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.