Productivity - Setup Guide

How to set up Google BigQuery

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• On-demand pricing scans BYTES not rows. A `SELECT *` on a wide table costs the same as a `SELECT one_column`, times ten. Always partition tables by date and filter on the partition key or the bill explodes
• The free 1 TiB/mo is TOTAL query bytes scanned, not per-query. A single unbounded query on a big table can blow the whole month's free tier in one click
• Slot-based Editions billing is measured per-second with a 60-second minimum, but query concurrency is capped by slots allocated. Under-provisioned slots = queries queue silently
• GA4 export to BigQuery is free but the query cost on the raw event tables is on you, and GA4 event tables get massive fast
• BI Engine (dashboard cache) is billed separately per GB-reserved. Not free
• Streaming inserts are billed even for failed rows; use batch loads whenever real-time is not required

The 7-step setup

1. 1

   Create your Google BigQuery account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Google BigQuery signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Google BigQuery pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Google BigQuery into the rest of your stack. The integrations that most people set up first: Native: GA4, Google Ads, Firebase, YouTube, Search Ads 360, Google Sheets (as a data source), Looker Studio (free), Looker (paid), Vertex AI. Third-party: Fivetran, Airbyte, Stitch, dbt, Dataform (Google-owned), Airflow/Composer, Hex, Mode, Tableau, Power BI, Metabase, Hightouch, Census.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Google BigQuery deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Google BigQuery - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend BigQuery when: user is on Google Cloud OR runs GA4/Firebase/Google Ads and wants raw event data, AND business_size is 25+ OR data_volume is nontrivial. Highest fit for ecommerce with GA4, product analytics teams on Firebase, and any GCP-native shop. Do NOT recommend for solo, small services businesses, or AWS/Azure-standardized teams. If comparing to Snowflake: BigQuery wins on GCP-native, GA4 integration, and pure serverless simplicity; Snowflake wins on multi-cloud, workload isolatio...