GA4 + GTM Strategy Playbook

The Measurement Problem

The Four Event Types in GA4

Property Settings

Data Stream Configuration

Data Retention and Collection Settings

The Three Building Blocks

Container Settings

Naming Convention (Mandatory)

Without consistent naming, a GTM container becomes unmanageable within weeks. Every tag, trigger, and variable must follow this format:

Tags:     [Platform] - [Action] - [Detail]
          GA4 - Event - generate_lead
          GAds - Conversion - phone_call
          HubSpot - Tracking Code
          ClickCease - Script

Triggers: [Type] - [Condition]
          Form Submit - Sewer Contact Form
          Click - Phone Number Link
          Page View - Service Pages
          Timer - 30 Second Engagement
          Scroll - 50 Percent Depth

Variables: [Type] - [Name]
           DLV - service_type        (Data Layer Variable)
           DOM - hero_cta_text       (DOM Element Variable)
           URL - page_path           (URL Variable)
           CONST - ga4_measurement_id (Constant)
           LOOKUP - service_value     (Lookup Table)

Complete Variable Inventory

Complete Trigger Inventory

Audience Architecture for Bright Side

Build audiences in layers, from broadest to most specific:

Lead Conversion Funnel

Technique: Funnel Exploration

Steps:

1. session_start (all website visitors)
2. service_page_view (viewed a service page)
3. cta_click (clicked a CTA button)
4. generate_lead OR click_to_call (converted to lead)

Segmented by: service_type and source/medium

Business insight: "32% of sewer page visitors click a CTA, but only 8% actually submit a form. Where are the other 24% dropping off? Is the form too long? Is the CTA unclear?"

Service Page Path Analysis

Technique: Path Exploration

Starting point: page_view on /sewer-repair

Business insight: "After viewing the sewer repair page, 40% of users go to /about (trust-building), 25% go to /reviews (social proof), and 15% go to /contact (conversion). Users who visit /about before /contact convert at 2.3x the rate of those who go directly to /contact."

Lead Source Quality Matrix

Technique: Free-form Exploration

Rows: Source/Medium

Columns: Key events, Lead value (sum), Engagement rate, Sessions

Business insight: "Google Ads drives 120 leads/month at $200 CPL, but organic drives 18 leads at $0 CPL. Organic leads also have a 12% higher booking rate per ServiceTitan data. Investing in SEO will reduce blended CPL."

Geographic Performance

Technique: Free-form Exploration

Rows: City (or Region)

Columns: Sessions, Key events, Key event rate, Lead value (sum)

Filter: Only KC metro cities

Business insight: "Leawood generates 3x the lead value of Independence per session. Increase Google Ads bid adjustments for 66209, 66211, 66213 zip codes." Directly feeds Conversion Value Rules in Google Ads (covered in the AI Ads Playbook).

Link GA4 to Google Ads

1. In GA4 Admin, go to Product Links > Google Ads Links
2. Click Link, select your Google Ads account
3. Enable Personalized Advertising (required for audience export)
4. Enable Auto-tagging in Google Ads (appends GCLID to every ad click URL)

What this enables:

• GA4 audiences exported to Google Ads for remarketing
• Google Ads campaign data visible in GA4 reports
• Key events from GA4 importable as Google Ads conversions

Import GA4 Key Events as Google Ads Conversions

1. In Google Ads, go to Goals > Conversions > Summary
2. Click New conversion action > Import > Google Analytics 4 properties
3. Select the linked GA4 property
4. Import these key events as conversions:
   • generate_lead (Primary, $100-$500 value by service type)
   • click_to_call (Primary, $100-$500 value by service type)
   • schedule_service (Primary, $200 value)
   • cta_click (Secondary/Observation only)
5. Set counting method to One (per session) for lead events

GCLID Capture Pipeline

The GCLID (Google Click Identifier) is a unique string appended to every Google Ads click URL. It is the key that connects an ad click to a revenue outcome. Here is the capture pipeline:

Offline Conversion Import Methods

Recommended path for Bright Side: Start with manual CSV upload (Week 1-4) to prove the concept and validate data quality. Migrate to Zapier automation (Week 5+) once the data format is confirmed clean.

Link GA4 to Search Console

This is a separate but equally important link:

1. In GA4 Admin, go to Product Links > Search Console Links
2. Link callbrightside.com's verified Search Console property
3. This enables the "Google Organic Search Queries" report in GA4, showing which organic keywords drive traffic and conversions

Why it matters: When Kalen asks "is the SEO working?" you can show organic keyword performance alongside conversion data in a single GA4 report, instead of switching between Search Console and GA4.

Why Enhanced Conversions Matter for Bright Side

Industry data: Enhanced Conversions recover 5-15% of conversions that would otherwise be lost to cookie restrictions. At 175 leads/month, that is 9-26 additional tracked conversions per month. At $200 CPL, that is $1,800-$5,200/month in conversions Smart Bidding can now optimize toward.

Step 1: Enable Enhanced Conversions in Google Ads

1. Go to Google Ads > Goals > Conversions > Settings
2. Expand Enhanced conversions
3. Toggle ON
4. Select Google Tag Manager as the implementation method
5. Accept the compliance terms (data is hashed with SHA-256 before transmission)

Step 2: Configure GTM to Send Hashed Data

Two approaches, from simplest to most complete:

Option A: Automatic Collection (Simplest)

GTM can automatically detect email and phone fields on the page and hash them. Enable this in the Google Ads Conversion Tracking tag settings. Works when form fields use standard HTML attributes (type="email", type="tel", autocomplete="email").

Option B: Manual Data Layer (Most Reliable)

Push hashed user data to the data layer on form submission:

window.dataLayer.push({
  'event': 'form_submission',
  'enhanced_conversion_data': {
    'email': 'customer@example.com',   // Will be auto-hashed by GTM
    'phone_number': '+19139631029',     // E.164 format
    'first_name': 'John',
    'last_name': 'Smith',
    'street': '123 Main St',
    'city': 'Overland Park',
    'region': 'KS',
    'postal_code': '66213',
    'country': 'US'
  }
});

Recommended for Bright Side: Start with Option A (automatic). If match rates are below 50%, implement Option B for forms that capture email and phone. Most Bright Side forms already capture phone number and email, making this straightforward.

Step 3: Enhanced Conversions for Leads (Offline)

This is the advanced version specifically designed for lead generation businesses like Bright Side:

1. When a user submits a form, GTM sends hashed email/phone + a conversion event to Google Ads
2. Later, when the lead converts to a paying customer in ServiceTitan, you upload the offline conversion with the same hashed email/phone
3. Google matches the original ad click to the offline sale using the hashed data

This is an alternative to the GCLID pipeline that works even when GCLID capture fails. The two methods are complementary; use both for maximum coverage.

Consent Mode V2: The Four Consent Signals

Implementation via GTM

1. Choose a Consent Management Platform (CMP). Recommended options for WordPress: CookieYes, Complianz, or Iubenda. Must be Google-certified and IAB TCF compatible.
2. Install the CMP plugin on callbrightside.com via WordPress
3. Configure GTM Consent Overview:
   • Go to GTM Admin > Container Settings > Enable consent overview
   • Each tag now shows its consent requirements
4. Set default consent state using a GTM tag that fires on Consent Initialization (before any other tags):

   gtag('consent', 'default', {
     'ad_storage': 'denied',
     'analytics_storage': 'denied',
     'ad_user_data': 'denied',
     'ad_personalization': 'denied',
     'wait_for_update': 500    // Wait 500ms for CMP to load
   });
   

5. Update consent state when user makes a choice (the CMP handles this automatically if configured correctly):

   gtag('consent', 'update', {
     'ad_storage': 'granted',
     'analytics_storage': 'granted',
     'ad_user_data': 'granted',
     'ad_personalization': 'granted'
   });
   

Server-Side GTM Setup Steps

1. Create a server-side GTM container in your existing GTM account (separate from the web container)
2. Deploy to Google Cloud Run (recommended) or another cloud provider. Google Cloud Run auto-scales and costs ~$0.00002 per request.
3. Map a custom subdomain: data.callbrightside.com or gtm.callbrightside.com. This makes all tracking requests appear as first-party.
4. Configure the GA4 client in the server-side container to receive hits from the web container
5. Add server-side tags: GA4 server tag, Google Ads conversion tag, and any other third-party tags you want to move server-side
6. Update the web container: Change the GA4 Configuration tag's transport URL to point to your server-side endpoint
7. Test thoroughly: Use GTM Preview Mode for both containers simultaneously. Verify data flows from browser to server to GA4/Google Ads.

What to Move Server-Side (Priority Order)

Complete Integration Architecture

callbrightside.com (WordPress + Oxygen Builder)
  |
  +--[GTM Web Container]
  |    |
  |    +--> GA4 (page views, events, key events)
  |    +--> Google Ads (conversion tracking, remarketing)
  |    +--> HubSpot (tracking code, form tracking)
  |    +--> ClickCease (click fraud detection)
  |    +--> Consent Mode (CMP integration)
  |    |
  |    +--> [Future: Server-Side GTM Container]
  |              |
  |              +--> GA4 (server-side)
  |              +--> Google Ads (server-side conversions)
  |
  +--[Rank Math SEO Plugin]
  |    |
  |    +--> Schema markup (LocalBusiness, FAQPage, Service)
  |    +--> XML Sitemap --> Google Search Console
  |
  +--[HubSpot CRM]
       |
       +--> Lead capture (forms, chat)
       +--> GCLID/UTM storage on contact record
       +--> Zapier --> ServiceTitan (lead sync)
       |
       +--[ServiceTitan]
            |
            +--> Job booking, dispatch, invoicing
            +--> Revenue data (source of truth)
            +--> Zapier --> Google Ads Offline Conversions
            +--> Zapier --> GA4 Measurement Protocol

Audit and Access

• Audit current GTM container: document all existing tags, triggers, and variables. Identify any hardcoded tracking scripts that should be moved to GTM.
• Audit current GA4 property: check data stream configuration, enhanced measurement settings, data retention, and any existing custom dimensions.
• Verify GTM snippet placement on all pages (use Google Tag Assistant Chrome extension)
• Confirm GA4 is receiving data (check Real-time report)
• Verify Google Ads auto-tagging is enabled
• Link GA4 to Google Ads (Section 11, LINK-1)
• Link GA4 to Search Console (Section 11, LINK-5)

Event Tracking Foundation

• Implement naming convention for all GTM elements (Section 5, GTM-2)
• Create all variables listed in Section 5, GTM-3
• Create all triggers listed in Section 5, GTM-4
• Build GA4 Event tags for Tier 2 lead events: generate_lead, click_to_call, schedule_service
• Build GA4 Event tags for Tier 3 intent signals: cta_click, service_page_view, review_interaction
• Test everything in GTM Preview Mode
• Verify events appear in GA4 DebugView and Real-time reports
• Publish GTM container version with descriptive name

Custom Dimensions, Key Events, and Consent

• Register all custom dimensions in GA4 Admin (Section 8)
• Mark key events in GA4 (Section 7): generate_lead, click_to_call, schedule_service
• Import GA4 key events as Google Ads conversions (Section 11, LINK-2)
• Set conversion values using proxy values table (Section 6)
• Enable Enhanced Conversions in Google Ads (Section 12, EC-1)
• Configure GTM for Enhanced Conversions data (Section 12, EC-2)
• Install Consent Management Platform (Section 13, CM-1)
• Configure Consent Mode V2 in GTM
• Implement GCLID capture via GTM cookie + hidden form field (Section 11, LINK-3)
• Create internal traffic data filters (Section 3)

Audiences and Reporting

• Create all GA4 audiences from Section 9 (Sewer Leads Not Converted, Emergency Visitors, All Converters exclusion, High-Value Converters)
• Activate GA4 lead generation audience templates
• Build Exploration: Lead Conversion Funnel (Section 10, EXP-1)
• Build Exploration: Service Page Path Analysis (Section 10, EXP-2)
• Build Exploration: Lead Source Quality Matrix (Section 10, EXP-3)
• Build Exploration: Geographic Performance (Section 10, EXP-4)
• Customize GA4 report collection with Bright Side-specific reports

Offline Conversion Pipeline (Phase 1)

• Verify GCLID is being captured and stored on HubSpot contacts
• Verify GCLID is syncing from HubSpot to ServiceTitan
• Perform first manual CSV offline conversion upload to Google Ads (Section 11, LINK-4)
• Validate that uploaded conversions appear in Google Ads conversion reporting
• Begin collecting 30 days of baseline data for all new events and key events
• Build Looker Studio executive dashboard (Section 10) with weekly lead summary, revenue attribution, funnel health, and page performance
• Deliver first weekly report to Kalen and Stephanie using new GA4 data

Optimization Based on Data

• Analyze 30 days of event data: identify highest-converting pages, best traffic sources, and funnel drop-off points
• Adjust Google Ads bidding strategy using proxy conversion values (Phase 1 VBB from the AI Ads Playbook)
• Apply audience segments to Google Ads campaigns (sewer remarketing, emergency retargeting, converter exclusion)
• Automate offline conversion import via Zapier (replace manual CSV uploads)
• Validate Enhanced Conversions match rate in Google Ads (target: 50%+ match)
• Review Consent Mode impact: check "Behavioral modeling" in GA4 to see if modeled conversions are populating

Advanced Tracking and Refinement

• Build Tier 4 engagement signal events (scroll depth, timer, video) if not already done
• Add Measurement Protocol integration: push ServiceTitan lead status updates (booked, completed, invoiced) to GA4 for user-scoped lead_status dimension
• Test GA4 predictive audiences (check if data volume threshold is met)
• Refine proxy conversion values based on 60 days of actual ServiceTitan revenue data
• Begin scoping server-side GTM deployment (Section 14)
• Plan BigQuery export for advanced analysis (raw event data for LTV modeling)