BigQuery

Your Webflow site captures site data such as form submissions and Webflow CMS content, but stores that data in isolation. You cannot run SQL joins across your Webflow form data and CRM records inside Webflow. Lead scoring and custom attribution models need data moved somewhere built for analytics.

BigQuery closes that gap. Connecting it with Webflow lets you route form submissions and order events into a data warehouse. CMS sync can follow through the Webflow APIs. There, standard SQL handles petabyte-scale queries. You can join Webflow data with CRM and revenue tables to compute segments. Then push results back into your CMS for personalized content.

Data analysts use this connection to build attribution models. Marketing teams track multi-touch conversions across channels. Webflow developers wire up webhook pipelines, and RevOps teams run reverse ETL from BigQuery back into Webflow.

How to integrate BigQuery with Webflow

What is BigQuery? BigQuery is Google Cloud's fully managed, serverless data warehouse and analytics platform. Its architecture splits into a storage layer and a compute layer connected by Google's petabit-scale network. You run standard SQL queries and stream data in real time through the Storage Write API. Machine learning models can also be trained directly in SQL.

Teams pair BigQuery with Webflow when site data needs to live alongside CRM and revenue data for analysis. A marketing team joins Webflow form submissions with Salesforce records to score leads. A publisher routes CMS content performance metrics into BigQuery for custom reporting. The direction of data flow and the amount of code you write depend on which method you choose.

The BigQuery-Webflow integration supports four approaches:

• Looker Studio embeds with Code Embed display BigQuery data on Webflow pages through an iframe.
• Native Data Exports send Analyze and Optimize data to BigQuery nightly on Enterprise plans.
• No-code automation platforms move data between Webflow and BigQuery without code.
• The Webflow Data API and BigQuery APIs give you full control over bidirectional sync, but require server-side development.

Implementations can combine two or more of these methods depending on the complexity of the setup.

Embed Looker Studio dashboards with Code Embed

Looker Studio is the only zero-code way to display BigQuery data on a Webflow page. You connect BigQuery to Looker Studio, build a dashboard in its drag-and-drop editor, then embed the report as an iframe. Write-back flows require automation or API middleware. Marketing teams and analysts use this to publish live metrics on internal or public pages without touching a backend.

To embed a Looker Studio report:

1. Connect BigQuery as a data source in Looker Studio using the BigQuery connector.
2. Build your report, then follow the steps to embed a report and copy the iframe code.
3. In Webflow, drop a Code Embed element onto the page and paste the iframe.

The Code Embed element cannot run server-side languages like PHP or Python, and it caps at 50,000 characters. For dashboards that stay within display-only use, this constraint rarely matters.

You can also bind CMS fields into a Code Embed if you want CMS field parameters in the iframe URL. See Use Collection fields in custom code embeds for how that works inside a Collection List.

Use native Data Exports to BigQuery

A built-in export sends Analyze and Optimize data to BigQuery on specific Enterprise plans. This is a one-way flow for analytics only. CMS content sync requires other methods. Your developers configure the connection, then you plug in the credentials they provide to start sending newly collected site data automatically.

To enable this export, your team follows the setup in the Export Analyze and Optimize data to Google BigQuery guide. Newly collected data exports on a nightly basis every 24 hours. Historic data is not exported, so plan the cutover date around when you want your warehouse record to begin.

This feature sends analytics data on Enterprise plans. Form submissions and CMS items require the API methods described next.

Connect with Zapier, viaSocket, or n8n

No-code automation platforms handle the authentication and error handling that a direct browser connection cannot. These tools store your BigQuery credentials securely on their side, so you never expose service account keys in client-side code. The platforms listed below all confirm direct Webflow ↔ BigQuery connections. This path suits marketing and operations teams who want data moving between the two systems without building middleware.

To set up a Zapier connection:

1. Create a new Zap and choose a Webflow trigger such as Webflow: New Form Submission or Webflow: New Order.
2. Connect your Webflow account and select the site and collection.
3. Add a Google BigQuery action like Google BigQuery: Create Row or Google BigQuery: Run a Query, then map the fields.

Each platform offers a different mix of triggers and actions:

• Zapier has four pre-built Zap templates. Webflow triggers include Webflow: New Form Submission, Webflow: New Order, Webflow: Updated Order, and Webflow: New Comment. Google BigQuery actions cover Google BigQuery: Create Row, Google BigQuery: Create Rows, Google BigQuery: Import Data, Google BigQuery: Update Row(s), Google BigQuery: Delete Rows, Google BigQuery: Run a Query, and Google BigQuery: Find One Row.
• n8n connects the Webflow node: create, update, delete, get items with the Google BigQuery node: Execute Query, Insert.
• viaSocket triggers on Webflow: New Form Submission, Webflow: New Order, Webflow: Updated Order, Webflow: Site Published, and Webflow: Page Created, with Google BigQuery actions for Google BigQuery: Run SQL Query, Google BigQuery: Insert Rows, Google BigQuery: Update Rows, Google BigQuery: Delete Rows, and Google BigQuery: Create Table.

For high-volume syncs, batch your writes and handle retries.

Build with the Webflow and BigQuery APIs

The API path lets you write to both Webflow and BigQuery and control retry and batching behavior. It requires server-side development because BigQuery authentication uses OAuth 2.0 or service accounts. Those credentials must never appear in browser JavaScript. Use Cloud Functions or Cloud Run for the middleware. A similar backend also works if it can hold credentials and broker requests between the two systems.

API builds use the BigQuery REST API for queries via jobs.query and streaming inserts via tabledata.insertAll. For high-throughput streaming with exactly-once semantics through committed streams, use the Storage Write API. Webflow's Data API v2 with Webflow webhooks handles CMS data and real-time events between systems.

Prefer the Storage Write API over tabledata.insertAll for new work. It delivers higher throughput and offers exactly-once semantics. Each row lands in BigQuery once, even on retries.

Stream form submissions to BigQuery

Route Webflow form submissions into a BigQuery table so you can join them with CRM data and calculate lead scores in SQL. This runs on webhooks, so events arrive as they happen rather than on a schedule.

To implement this:

1. Register a webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks and a body of { "triggerType": "form_submission", "url": "<your_middleware_url>" }.
2. Receive the POST payload in your middleware and parse the form fields from the webhook body.
3. Stream each row into BigQuery using the Storage Write API AppendRows on a default stream (at-least-once) or committed stream (exactly-once).

If you use tabledata.insertAll instead, include a unique insertId per row for best-effort deduplication. Note that tabledata.insertAll has usage constraints that the Storage Write API avoids.

Warehouse e-commerce orders

Capture order and inventory changes from a Webflow e-commerce site in BigQuery for revenue analysis and reconciliation. Order and inventory webhook trigger types cover the events you need.

To set this up:

1. Register the order webhooks first: ecomm_new_order and ecomm_order_changed via POST https://api.webflow.com/v2/sites/{site_id}/webhooks. Add ecomm_inventory_changed for inventory events.
2. Route order events in middleware to tables such as orders and order_updates. Route inventory events to inventory.
3. Stream events using the Storage Write API, then run jobs.insert for nightly batch reconciliation.

Webflow CMS is not designed for sensitive payment data. You must independently scope any payment pipeline for PCI DSS compliance.

Run reverse ETL from BigQuery to Webflow CMS

Push computed segments and metrics from BigQuery back into your Webflow CMS for personalized CMS content. Reverse ETL means querying your warehouse and writing the results back into another system. This flow queries BigQuery, then writes results to CMS items through the Data API.

To implement this:

1. Query BigQuery with jobs.query to retrieve computed data like personalization segments.
2. Map result columns to Webflow CMS field slugs in middleware, then update items with PATCH /v2/collections/{collection_id}/items/{item_id}.
3. Throttle your requests and use exponential backoff for large datasets.

Reference fields need Webflow-generated item IDs, so your middleware must store and pass those IDs rather than arbitrary strings. Event-driven reverse ETL needs an Eventarc or Pub/Sub intermediary in Google Cloud. See the guide on how to trigger Cloud Run actions on BigQuery events.

What can you build with the BigQuery Webflow integration?

Integrating BigQuery with Webflow lets you analyze site data alongside your full data stack without exporting spreadsheets by hand.

• Lead intelligence pipeline: Stream form submissions into BigQuery through a webhook, then join them with CRM records in SQL to calculate lead scores. Sales sees a ranked list of inbound leads scored on behavioral and firmographic signals.
• Multi-touch attribution model: Centralize Webflow behavioral data in BigQuery and build attribution across paid and organic channels. A growth team reports which touchpoints drove pipeline instead of crediting only last click.
• Embedded BI dashboard: Connect BigQuery to Looker Studio, build a live sales dashboard, and embed it on a Webflow page with Code Embed. Stakeholders view current metrics on an internal page without a separate analytics login.
• Personalized CMS content: Run reverse ETL to sync customer segments from BigQuery back into CMS items, then bind those fields in a Collection List. Returning visitors see content matched to their computed segment.

If you need more control over exactly-once streaming or event-driven reverse ETL, the API integration path covers those cases with full flexibility.