Connect PostHog with Webflow

PostHog with Webflow

Most startups run one analytics tool on the marketing site and another inside the product, then spend a quarter arguing about which number is right. PostHog can hold both. The work is making the Webflow side send events the product will recognise.

Book a call

Analytics work like this usually takes 2–4 days

What the integration covers

What syncs, and what needs a decision.

Wired up

A small, named event set fired from real interactions rather than autocapture alone
The same distinct id used on the marketing site and in the product, so the funnel joins
Campaign parameters carried from first visit through to signup
Session replay limited to the pages where watching one would teach you something
Consent respected, so nothing is captured before the banner is answered

Flagged upfront

Webflow's form success is a div swap with no page load, so a signup event fires deliberately or never fires at all
Autocapture on a Webflow site keys off classes the Designer generates, so a restyle can quietly rename your events
The snippet goes in Webflow's site-wide code, which caps at 50,000 characters and has no build step
Session replay on a marketing site records real visitors, so which pages it covers is a privacy decision

The reason to put PostHog on the marketing site rather than a separate tool is that the interesting question spans both. Not “how many people hit the pricing page”, but “which of the people who read the pricing page twice ended up activating”. That only works if both halves agree on who the person is.

Autocapture is the feature to be careful with here. It works by recording the elements someone clicked, and on a Webflow site those selectors are class names the Designer generated. Restyle a button and the event describing it can change name without anyone touching analytics. I fire the handful of events that matter explicitly, and let autocapture be the safety net rather than the plan.

Session replay is worth having and worth limiting. Recording every visitor on every page produces hours nobody watches and a privacy question nobody asked for. Scoped to the pages where a replay would actually change something, it earns its place.

Other integrations

Wire up something else?

Reach out and see if we are a good fit.

Start a conversation

Currently booking two to four weeks out.