GA4, Search Console and GTM Setup for Reliable Marketing Measurement

Google Analytics 4

GA4 measures website and application activity—users, sessions, traffic sources, landing pages, events, engagement, conversions or key events, ecommerce, revenue, campaigns, and user journeys.

Google Search Console

Search Console shows how the website performs across Google Search—queries, impressions, clicks, CTR, average position, ranking pages, countries, devices, search appearance, indexation, sitemaps, Core Web Vitals, and structured-data issues.

Google Tag Manager

GTM helps deploy and manage analytics and marketing tags without placing every tracking script into individual templates—supporting GA4, events, conversions, advertising tags, forms, clicks, data-layer events, consent controls, testing, and version management.

Analytics and Tracking Audit

I review the current analytics and tracking environment before creating or changing the setup—so existing systems are understood before new tags or events are introduced.

• Existing GA4 properties, data streams, and GTM containers
• Search Console properties and existing tracking scripts
• Conversion, ecommerce, form, and call tracking
• Advertising pixels, consent tools, and cross-domain tracking
• Referral exclusions, campaign parameters, and duplicate tags
• Broken events, missing data, internal/dev traffic, and existing reports

Measurement Strategy and KPI Plan

I create a measurement plan based on the business model and customer journey—preventing unrelated events from being added without a clear reason.

• Business objectives and primary vs secondary conversions
• Supporting engagement events and required parameters
• Traffic-source, landing-page, and reporting requirements
• Lead generation, ecommerce, bookings, quotes, and demos
• Calls, messages, downloads, account creation, and subscriptions

Google Analytics 4 Property Setup

I create or configure the appropriate GA4 property and website data stream to match the business’s websites, brands, markets, and reporting responsibilities.

• Account and property structure, name, time zone, and currency
• Website data stream and enhanced measurement review
• Data retention, collection, and internal-traffic rules
• Unwanted referrals and cross-domain measurement
• Search Console and Google Ads linking where relevant
• User access and permissions

GA4 Installation and Configuration

GA4 may be implemented through GTM, direct installation, CMS or ecommerce integration, application data layer, or custom development—depending on the website’s technology.

• Loads on correct pages with the correct measurement ID
• Fires only once and respects consent configuration
• Preserves campaign parameters and tracks page views correctly
• Handles SPA navigation and cross-domain journeys
• Avoids development and staging traffic where possible

Google Tag Manager Container Setup

I create or organize the GTM container so it is understandable by future analysts, marketers, and developers—replacing generic names with clear descriptions.

• Container creation and installation validation
• Tag, trigger, and variable structure with folders
• Naming conventions and workspace management
• Environment configuration and user permissions
• Version documentation and publishing process

Event Tracking Architecture

I define the event structure used to measure meaningful actions—with consistent names and parameters planned before implementation.

• Forms, phone, email, WhatsApp, Telegram, and bookings
• Quotes, demos, downloads, video, and product interactions
• Cart, checkout, purchase, registration, and login
• Internal search, outbound links, pricing, and service selection
• Parameters for page, form, service, product, market, language, and value

Conversion and Key Event Setup

Important business actions are configured as GA4 key events or conversions. Primary and secondary actions are not treated as equally valuable.

• Primary: contact forms, purchases, bookings, qualified calls, trials, demos
• Secondary: phone/messaging/email clicks, downloads, pricing visits
• Booking/checkout starts and form starts as supporting signals
• Documented definition, trigger, parameters, value, and testing method

Form Tracking

Where possible, successful form tracking is based on a confirmed completion event—not only the submit-button click.

• Form view, start, field interaction, and submission attempt
• Successful submission, errors, and confirmation pages
• Lead type, form name, page location, and service selected
• Distinction between click, attempt, and successful lead creation

Phone, Email and Messaging Tracking

For service and local businesses, I configure click tracking for contact actions while distinguishing clicks from qualified or completed leads.

• Click-to-call, email, WhatsApp, Telegram, and Messenger
• Booking links and external contact platforms
• Contact type, page URL, button location, service, language, and device

Booking and Appointment Tracking

For tourism, hospitality, healthcare, consulting, and appointment-based services, I track booking-journey stages where the platform allows.

• Widget open, date/service/room selection, and booking start
• Customer-details and payment steps
• Booking completion, failure, and external platform clicks
• Coordination with iframes, third-party platforms, and confirmation pages

Ecommerce Tracking

For ecommerce and marketplace websites, I review or implement GA4 ecommerce measurement based on a reliable data layer and validated against the platform.

• view_item_list, select_item, view_item, add_to_cart, view_cart
• begin_checkout, shipping/payment info, purchase, and refund
• Item ID, name, brand, category, variant, price, and quantity
• Transaction ID, revenue, shipping, tax, coupon, and currency

Data Layer Planning and Implementation Support

I define or review data-layer requirements and prepare implementation-ready instructions for developers where needed.

• Ecommerce, forms, bookings, and logged-in states
• Service selections, product categories, lead types, and transactions
• Content groups, languages, and markets
• Event name, fields, examples, naming rules, and acceptance criteria

Single-Page Application Tracking

For React, Next.js, Angular, Vue, Nuxt, and similar frameworks, I ensure navigation and conversions are measured correctly without traditional full-page reloads.

• Route changes and virtual page views
• Dynamic titles, URLs, and referrer behaviour
• Component interactions, forms, and ecommerce events
• Duplicate page-view prevention across SSR, SSG, and CSR

Outbound Link and File Download Tracking

I configure tracking for meaningful external links and downloadable resources—not every outbound click.

• Partner, booking, payment, supplier, and app-store links
• PDFs, brochures, price lists, case studies, and whitepapers
• Link URL, domain, file name/type, button text, and page location

Video and Content Engagement Tracking

Engagement events are supporting indicators rather than primary business conversions. Scroll thresholds do not prove content was read.

• Video/audio start, progress, and completion
• Accordion, tab, calculator, and comparison-tool interactions
• Careful interpretation of scroll tracking

Internal Site Search Tracking

Internal search data can support content, navigation, product, and user-experience decisions.

• Search terms and results count
• No-results events and selected results
• Search refinements and conversion after search
• Language-preference insights from search terms

Custom Dimensions and Content Grouping

I configure useful custom dimensions where standard GA4 information is not enough—limited to fields that will genuinely be used.

• Service, product category, content type, and topic cluster
• Author, language, market, user type, and membership status
• Lead type, form name, page template, location, and funnel stage
• Support for explorations, Looker Studio, and conversion reporting

Cross-Domain Measurement

Without correct setup, users may appear as new referrals when moving between related domains. The final approach depends on platform access and technical limitations.

• Website and booking, app, payment, shop, or portal domains
• Domain configuration, link decoration, and session continuity
• Referral behaviour, conversion attribution, and cookie configuration
• Form submission flows and payment-provider returns

Subdomain Measurement

I review whether subdomains should be measured together or separately based on whether they belong to one customer journey or separate products.

• www, blog, shop, app, and booking subdomains
• Shared property vs separate data streams
• Combined reporting, referral exclusions, and hostname reporting

Campaign and UTM Tracking Framework

I create a consistent UTM naming framework so channel and campaign reporting remains comparable over time.

• utm_source, utm_medium, utm_campaign, utm_content, utm_term
• Rules for paid, social, email, influencer, affiliate, and offline
• QR codes, messaging, PDF, and presentation links
• Allowed values, capitalization, separators, ownership, and examples

Traffic Source and Referral Cleanup

I review unexpected or misleading traffic classifications while preserving genuine referral information.

• Payment providers and booking systems overwriting sources
• Self-referrals, subdomain referrals, and direct misclassification
• Incorrect UTMs, development domains, and spam referrals
• Unwanted referral configuration and campaign-tagging rules

Internal and Developer Traffic Exclusion

Internal testing can distort website performance data. The appropriate method depends on remote work, dynamic IPs, privacy, and access.

• Office, employee, developer, staging, and QA traffic
• Agency traffic, monitoring services, and automated tools
• IP rules, debug parameters, developer cookies, and hostname filters
• Separate properties and environment-specific tags

Consent-Aware Tracking Setup

I configure technical measurement behaviour according to the customer’s approved consent requirements. This service does not replace legal advice.

• Consent-platform integration and tag firing rules
• Analytics, advertising, and personalization storage settings
• Consent-update events and default/regional behaviour
• Testing procedures for before-and-after consent states

Google Search Console Property Setup

I create or review the appropriate Search Console property structure—domain properties for broad coverage, URL-prefix for specific workflows.

• Domain and URL-prefix properties
• HTTPS, subdomain, staging, and legacy properties where relevant
• Ownership verification, permissions, and sitemap submission
• GA4 linking and domain-migration preparation

Search Console Verification

Where practical, verification should remain under an account controlled by the business.

• DNS, HTML file, meta tag, Analytics, and GTM methods
• Selection based on domain, hosting, platform, and ownership needs

XML Sitemap Submission and Monitoring

Submitting a sitemap does not guarantee indexation—it helps communicate which canonical and indexable URLs matter.

• Sitemap location, accessibility, and sitemap indexes
• Page, product, category, article, image, video, and language sitemaps
• Removal of redirected, noindex, non-canonical, and broken URLs

Search Performance Configuration

I organize Search Console reporting around important business dimensions to support later dashboards and SEO reviews.

• Branded vs non-branded queries
• Services, products, countries, languages, and devices
• Page types, locations, content clusters, and commercial pages

Search Console Indexation Review

The setup service identifies obvious measurement and configuration problems. A complete technical diagnosis may require a separate technical SEO audit.

• Indexed, redirected, not-found, and soft 404 pages
• Duplicates, alternative canonicals, and crawl coverage issues
• Blocked, noindex, and sitemap processing problems

GA4 and Search Console Linking

Where supported, I connect GA4 and Search Console. Their totals should not be expected to match exactly because they measure different systems.

• Search queries and organic landing pages
• Search impressions, clicks, engagement, and conversions

Advertising Platform Connection

Where relevant, I connect GA4 with Google Ads and validate conversion sharing carefully to avoid duplicates and weak engagement imports.

• Account linking, audiences, and conversion import
• Campaign attribution and auto-tagging review
• Remarketing requirements and consent dependencies

Debugging and Quality Assurance

I test the implementation using GTM Preview, GA4 DebugView, browser tools, Tag Assistant, real-time reporting, and end-to-end conversion tests.

• Correct trigger, event name, parameters, and value
• Duplicate or missing firing and page context
• Consent behaviour and reporting availability
• Forms, purchases, bookings, clicks, and cross-domain journeys

Duplicate Tracking Prevention

I identify and remove or document unnecessary duplication that can inflate page views, events, conversions, revenue, and advertising performance.

• Direct code plus GTM, CMS plugins, and ecommerce apps
• Old Universal Analytics and duplicate GA4 config tags
• Duplicate form triggers and double-counted conversions

Staging and Production Environment Review

Development and test activity should not contaminate the main business data unnecessarily.

• Local, staging, testing, and production behaviour
• Environment variables, GTM environments, and hostname conditions
• Debug flags, separate properties, and restricted advertising tags

User Access and Account Ownership

Where possible, the business should retain control of its primary analytics and search accounts—not depend permanently on one employee, freelancer, or agency login.

• GA4, GTM, Search Console, Ads, and Looker Studio access
• Owner, administrator, editor, and viewer roles
• Agency, developer, and client access with recovery ownership

Naming Conventions and Governance

Consistent naming reduces reporting confusion and makes future maintenance easier.

• GTM tags, triggers, variables, and GA4 events
• Event parameters, conversions, custom dimensions, and campaigns
• Lowercase rules, separators, ownership, testing status, and version notes

Analytics Documentation

I prepare documentation explaining the final implementation as a reference for marketing, analysts, developers, SEO, advertising, and business owners.

• Account structure, IDs, streams, and GTM container
• Events, parameters, conversions, and custom dimensions
• Data-layer requirements, cross-domain, consent, and UTM rules
• Search Console properties, testing results, and known limitations

Developer-Ready Tracking Specifications

Where development support is needed, I prepare implementation-ready requirements with examples, timing, consent, QA, and acceptance criteria.

• Event name, business meaning, and trigger
• Required and optional data-layer values
• Example code, page or component, and expected timing

Reporting Readiness

After setup, I organize the data so it can support Looker Studio, PowerPoint, Canva, Sheets, Excel, PDF, GA4 Explorations, and Search Console reports.

• Event naming and custom dimensions
• Landing-page, service, market, and language grouping
• Conversion definitions, campaign standards, and data-source docs

Post-Launch Monitoring

After publishing, I review whether expected data begins appearing correctly—using real-time tools first, then standard reports after processing.

• Page views, events, conversions, ecommerce, and revenue
• Traffic sources, referrals, campaigns, and Search Console data
• Sitemaps, data freshness, consent behaviour, and unexpected errors

Ongoing Tracking Maintenance

Tracking should be reviewed whenever an important customer journey or website component changes.

• New forms, bookings, products, checkout, domains, and languages
• Migrations, markets, campaigns, and consent requirements
• New conversions, GTM cleanup, data-quality reviews, and reporting changes