Transaction inbound (BigQuery)

Transaction inbound is the BigQuery
approach for teams that don’t already produce Twelfth’s webapp_* serving
contract. Instead of pointing Twelfth at finished serving tables, you land raw
transaction and customer data in a BigQuery dataset and Twelfth reads it in,
builds the model, and keeps it in sync on a schedule.

It is inbound and read-only — data flows into Twelfth, and Twelfth never
writes back to your warehouse. Reach it from Settings → Integrations → Google
BigQuery; it’s set up with Twelfth rather than fully self-serve.

When to use this

Use transaction inbound when:

• You have transaction, order, and customer data in BigQuery, but not the
  finished webapp_* serving tables that
  Customer-managed BigQuery expects.
• You’d rather hand Twelfth raw tables and let it derive SKUs, outlets,
  suppliers, and performance itself.

If you already publish the webapp_* contract, use
Customer-managed BigQuery instead — it
is fully self-serve.

How it works

1. Land the data. Keep your transaction and customer tables in a BigQuery
   dataset in your own GCP project.
2. Grant read-only access. As with the customer-managed model, you grant a
   dedicated Twelfth service account read-only IAM on the dataset and project —
   there is no secret to upload, and you can revoke the grant at any time.
3. Map the data. Twelfth works with you to map your raw tables to the model
   it needs, then reads them on a schedule.

The same guarantees apply as every BigQuery read: single-statement SELECT
only, a cost gate, a row cap, and queries that run on your project’s billing.

Security and guarantees

• Read-only inbound. Twelfth reads the tables you nominate and never writes
  to your warehouse.
• No secret stored. Access is an IAM grant in your project, governed and
  revocable by you.
• Scoped to what you land. Twelfth reads only the dataset and tables you point
  it at.

Related

• BigQuery overview — the two models and three approaches
• Customer-managed BigQuery — self-serve read-only serving contract
• Custom integrations — the same inbound idea outside BigQuery (S3, GCS, SFTP, API)
• Request an integration — ask Twelfth to set this up