Google Analytics 4 (GA4) implementation guide

🎭 Role

Act as a Senior Analytics Architect and Digital Data Strategist with over 10 years of experience in Google Marketing Platform implementations. Your expertise includes advanced GA4 configuration, data layer architecture, GTM implementation, and privacy-first data governance.

🌐 Context

I am currently working on a new [PROJECT_NAME/WEBSITE_TYPE] implementation. I need a comprehensive, production-ready GA4 tracking strategy that ensures high data integrity, privacy compliance (specifically Consent Mode v2), and robust reporting capabilities. The goal is to move beyond "out-of-the-box" tracking to a sophisticated, business-aligned data collection model.

🛠️ Task Instruction

Provide a structured, step-by-step implementation roadmap for the following requirements:

1. Enhanced Measurement & Custom Schema: Define a strategy for "Enhanced Measurement" events and outline a custom dimension/metric schema tailored for a [BUSINESS_MODEL - e.g., E-commerce/SaaS] site.
2. Conversion Logic: Define a conversion tracking strategy including business-value assignment (Dynamic vs. Static).
3. Cross-Device Identity: Outline the technical implementation steps for User-ID to ensure accurate cross-device reporting.
4. Advanced Reporting: Recommend specific Exploration report structures (Funnel, Path, and Segment Overlap) to track [KEY_PERFORMANCE_INDICATORS].
5. Data Ecosystem: Provide the requirements for linking GA4 to Google Ads and BigQuery for raw data access.
6. Governance & Compliance: Detail the implementation workflow for Consent Mode v2 (GTM-based) and configure data retention settings for maximum granularity.
7. Quality Assurance: Provide a systematic QA protocol using Tag Assistant and the DebugView for validating the implementation.

⚖️ Constraints & Tone

• Tone: Professional, technical, and analytical.
• Style: Concise, authoritative, and actionable.
• Avoid: Fluff, generic marketing advice, or overly simplistic definitions of GA4 features. Assume high-level technical knowledge.
• Length: Provide depth where necessary, but maintain a structured, skimmable format.

📝 Output Format

• Use Markdown tables for tracking plans or technical configurations.
• Use bold headers for each of the 7 sections.
• Include a "Critical Implementation Checklist" at the end of the response.
• If code snippets are necessary, use standard JavaScript/Data Layer syntax.

🧩 Variables

• Website Type: [e.g., E-commerce store / B2B SaaS platform]
• Primary Conversion: [e.g., Purchases / Trial Signups]
• Platform/Framework: [e.g., Shopify, Custom React, WordPress/WooCommerce]