Your website's own business intelligence

Website Intelligence is business intelligence for your website. It joins the behavior data your site collects to the deal data in your CRM, producing one row per person that shows everything they read before they were identified and everything they became after. That single table is what lets you rank pages, channels and campaigns by revenue instead of traffic.

Because Google Analytics 4 stops at the form. GA4 records what an anonymous visitor did and your CRM records what a named customer paid, and no shared key connects them, so neither system can tell you they are the same person. Website Intelligence writes that key at the moment someone submits a form, then joins both sides in BigQuery.

No. It reads whatever first-party visitor ID your site already issues, so it works with GA4 and Google Tag Manager on any platform. Webflow sites get more out of it, because Webflow Analyze exports clicks already named the way you named them in the Designer and records which visitor saw which test variation. Neither is available in GA4 without extensive manual tagging.

Any CRM that can export deals with an email address, including HubSpot, Salesforce and Pipedrive. The join happens on a hashed email rather than a vendor-specific ID, so the CRM is interchangeable. What varies is how your CRM data reaches your warehouse, which is why it's the first thing we ask about.

Weeks rather than months. The tracking bridge is a single tag and a small endpoint, written once and reused across sites, and the join is a handful of scheduled BigQuery queries. What moves the timeline is how your CRM data reaches the warehouse. A CRM that already syncs is the fast case.

No. The output is one flat table with columns named in plain English, readable without SQL. It's also why you can point a language model at it and ask questions directly, and every answer comes back with the query that produced it, so a surprising number can be checked rather than believed.

The data stays in your own BigQuery instance, in the region your policy requires. Emails are stored as a one-way SHA-256 hash and never in the clear, and nothing is captured before your visitor's consent choice is read. The AI layer runs on a read-only account scoped to your dataset, so it can read your data and cannot change it.

A customer data platform connects many systems and asks you to set up the tracking and adopt its schema first. Website Intelligence connects two, your website and your CRM, and the tracking setup is included because the team building it also builds your site. That narrower scope is why it takes weeks rather than a platform rollout.