Integration guide
Google BigQuery
Start with a governed retail data extract.
Use this page to plan Google BigQuery with NOGL. Confirm source coverage, customer authorisation and the delivery method before relying on a connection.
Start with a retail decision
Choose the review
Bring an agreed product or performance dataset into the pilot without opening the whole warehouse.
Make the evidence comparable
Validate row counts, nulls, key uniqueness, freshness and ownership of each metric.
Data scope to agree
These are planning fields, not a guarantee that every field is exposed or connected. Begin with the smallest useful sample.
| Proposed fields | Operation | Access boundary |
|---|---|---|
| Agreed table or view · stable keys · date grain · market · metric definitions | Read an agreed sample | Confirm permissions and field availability before setup |
Before you begin
- Name the business owner and the person who can approve source access.
- Choose one market, a small sample and a concrete review question.
- Agree record IDs, date range, currency, privacy boundaries and retention.
From scope to a reviewed connection
01
Plan
Agree the fields, direction, delivery method and success criteria.
02
Authorise
Confirm the owner and permissions through the agreed secure setup process.
03
Validate
Compare a small sample with the source; check missing rows, duplicates and timestamps.
04
Review health
Agree a freshness threshold, failure contact and how to pause or revoke access.
Limits & support
A named warehouse in the directory does not establish a deployed ingestion job or write permission.
Do not send passwords, API keys or customer records through the contact form.