Google Analytics with Webflow

Before you wire it

Three things that commonly go wrong.

1. 01

   A checkout or booking on another domain can break attribution

   Without cross-domain measurement and the referral exclusions to go with it, a visitor who leaves for a payment processor or a scheduler comes back looking like new referral traffic. The conversion survives and the campaign that produced it is obscured, which is a configuration problem rather than something inevitable.

2. 02

   An inline form success is not a destination page

   For forms using Webflow's inline success message, the state swaps in without navigating, so a conversion configured as a destination never fires. It is tracked as an event on the successful submission instead, and the difference is invisible until the report is empty.

3. 03

   The container is where third-party scripts accumulate

   GA4 itself is small. Tags added through a container bypass the usual development workflow, so old campaign pixels, a second analytics tool and heavy vendor scripts outlive anybody's memory of why they were added. Tag Manager changes need the same ownership and review as other site changes.

What you are buying

What is included.

• GA4 through Webflow's Google integration, Tag Manager, or the agreed tag architecture

• A short list of conversion and engagement events

• Form submissions, outbound clicks and campaign attribution

• Consent Mode behavior connected to the banner

• Redirect and UTM handling across the site