Skip to main content

Client Landing Page Setup Guide

This guide describes how Pacing Agency sets up a client-owned Webflow landing page with the full tracking stack for paid ads campaigns: GTM, Stape server-side tagging, BigQuery, Google Ads events (page view, CTA click, lead form submit), and user-id propagation to forms and booking widgets.

Use case: A dedicated subdomain (e.g. get.clientdomain.com) hosts a Webflow landing page for Google Ads traffic. The main client website may remain on another CMS (e.g. Wix) during the transition.

What This Guide Covers​

PageContent
Migrating from another CMSDomain and DNS when the client site is on Wix or another platform; Wix name server limitations and workarounds.
Third-party embeds and trackingGTM and Google Analytics on the page that contains Cal.com (and similar); user-id in booking widgets and forms.
Full stack implementationPhase-by-phase setup: Cloudflare DNS, Stape, GTM (web + server), BigQuery, Google Ads events, Webflow code snippets, testing. Includes tables, diagrams, and code.

The Server-Side Tracking Guide covers Stape/GTM/BigQuery in more depth; this guide focuses on client landing page subdomain, Webflow, and CMS-migration specifics.

Prerequisites​

  • Client has (or will have) a Webflow site for the landing page.
  • Domain will be managed in Cloudflare (client account with Pacing as Super Admin is preferred; see Cloudflare (tool)).
  • GTM web + server containers (and Stape) for the client.
  • GA4 property and Google Ads linked; BigQuery dataset for event logging.

Access pattern (GA4 and GTM)​

  • Prefer client-owned Google Analytics and Google Tag Manager accounts: the client creates the account and property/containers, then adds Pacing (e.g. Ben and Cam) as administrators with Read, Write, and Publish (GTM). Default GTM invite is often read-only; ensure each user is set to full access so tags can be published.
  • Same pattern for GA4: client creates the property and adds Pacing as users with the needed role (e.g. Administrator).