GA4 & GTM Setup — Build a Solid Measurement Foundation
Professional GA4 property configuration and Google Tag Manager setup. Custom events, e-commerce tracking, data layer architecture.
Structured GA4 configuration
Setting up a GA4 property goes far beyond pasting a snippet on your site. A rigorous configuration starts with property settings: timezone, currency, internal data filters, cross-domain tracking, and attribution reporting. Data streams are configured with the relevant enhanced measurements (scroll, outbound clicks, site search, video engagement) while irrelevant ones are disabled to reduce noise.
Google’s recommended events (page_view, scroll, click, view_search_results) are complemented by custom events aligned with your business goals: generate_lead, begin_checkout, purchase, sign_up. Each event is defined with its specific parameters and custom dimensions in GA4, so that data is immediately actionable in reports and explorations.
Google Tag Manager setup
The GTM container is the cornerstone of your measurement stack. We build a clean architecture: naming conventions for tags, triggers and variables (prefixed by tool, typed), folders organized by function (analytics, ads, consent, utilities). The data layer is defined upfront with your technical team: object structure, push timing, and e-commerce data schema.
Triggers are configured precisely to avoid spurious firings. We use trigger groups, sequences and exceptions where needed. Data layer variables are preferred over DOM variables, which are more fragile as front-end code evolves. A well-structured GTM container is one where any analyst can step in six months later without needing to reverse-engineer the logic.
E-commerce tracking and UA migration
GA4 e-commerce tracking follows the dedicated event schema: view_item, add_to_cart, begin_checkout, add_payment_info, purchase. Each funnel step is instrumented with the required parameters (items array, currency, value, transaction_id). We verify data consistency between the data layer, GA4 and your back-end to ensure reported revenue matches reality.
For sites still transitioning from Universal Analytics, migration is planned with a UA-to-GA4 event mapping, a dual-tracking period for data comparison, and documentation of expected discrepancies. The goal is to ensure continuity of your historical KPIs while leveraging GA4’s event-based model.