GA4 Setup for Hospitals India 2026 — Multi-Property Architecture | ICG

Author: Deep Das · Co-Founder, ICG · IIT BHU · July 2026

A hospital's GA4 implementation is the foundation of all digital performance measurement. Get it wrong and every CPQL calculation, every channel attribution, every content performance report is built on flawed data. ICG audits hospital GA4 setups at engagement start — and 70-80% of the time, finds fundamental architectural problems that are silently corrupting the performance data.

The most common hospital GA4 architecture mistakes

Mistake 1: Single property for all specialties A single GA4 property for a multi-specialty hospital gives you aggregate traffic data with no specialty breakdown. You cannot determine whether the 500 monthly organic sessions came from cardiology queries or maternity queries. You cannot calculate CPQL per specialty. You cannot make channel allocation decisions by specialty.

ICG's architecture: One GA4 property per specialty as the recommended approach for hospitals with 5+ active marketing specialties. A hospital GA4 account structure: ``` GA4 Account: [Hospital Name] → Property: Cardiology (cardiology.hospital.com or hospital.com/cardiology/) → Property: Maternity (hospital.com/maternity/) → Property: Orthopaedics (hospital.com/orthopaedics/) → Property: Master Property (hospital.com — all pages, for hospital-level reporting) ```

Mistake 2: Default event tracking only GA4's default event tracking captures page views, sessions, and scroll depth. For a hospital, the events that actually matter are: WhatsApp click, phone number click, appointment booking form submission, doctor profile view (engagement intent), specialty page view (specialty interest signal), and — via Beacon — consultation attendance confirmation.

ICG's hospital custom event configuration: ```javascript // WhatsApp CTA click tracking document.querySelector('.whatsapp-cta').addEventListener('click', () => { gtag('event', 'whatsapp_click', { 'event_category': 'Lead', 'specialty': getSpecialtyFromPage(), 'doctor': getDoctorFromPage() }); }); ```

Mistake 3: No cross-domain tracking Many hospital websites have separate subdomains for their appointment booking system (book.hospital.com), their patient portal (patient.hospital.com), and their main website (hospital.com). Without cross-domain tracking, GA4 treats these as separate sessions — creating source attribution gaps (a patient who came from Google, browsed the main site, then booked on the booking subdomain appears as a "direct" conversion in the booking subdomain's data).

ICG's cross-domain configuration: all hospital-owned subdomains listed in GA4's cross-domain settings, ensuring unified session tracking across the booking journey.

Mistake 4: Missing DPDP compliance safeguards Default GA4 collection includes IP addresses and other potential personal identifiers. For healthcare websites, additional steps are required: IP anonymisation (enabled by default in GA4, but verify), no user-identifiable custom dimensions (never store patient name, phone, or email in GA4 custom dimensions), data deletion requests protocol (patients have the DPDP right to request GA4 data deletion — ICG configures the deletion request workflow).

Custom dimensions for hospital GA4

ICG's standard hospital GA4 custom dimension set:

These dimensions enable: specialty-by-specialty channel attribution, doctor profile engagement analysis, consultation type funnel analysis, and geographic catchment reporting.

yoda/10-traffic-source.png" alt="YODA Traffic Source Analysis — 6-month split of YouTube traffic sources: YouTube search, external search, suggested, browse, external" loading="lazy" decoding="async" style="width:100%;height:auto;display:block;">

FAQ

Q1: How many GA4 properties does a 200-bed hospital need? ICG's recommendation: one master property (all hospital traffic) + one property per actively marketed specialty (5-8 for most 200-bed hospitals). Total: 6-9 GA4 properties. This seems like more than necessary, but the specialty-level data quality improvement justifies the setup overhead — and GA4 is free regardless of property count.

Q2: Does GA4 work with healthcare CRMs for full-funnel attribution? GA4 captures the digital journey up to the conversion event. Full-funnel attribution (digital touchpoint → consultation booking → consultation attendance) requires CRM integration beyond GA4's native capabilities. ICG's Beacon platform bridges this gap — capturing the CRM consultation events and importing them to GA4 as offline conversion events, creating a complete funnel view within GA4.

Q3: Is Google Analytics 4 DPDP compliant for healthcare websites? With appropriate configuration: yes. Required steps: (a) IP anonymisation enabled (GA4 default), (b) no user-identifiable data in custom dimensions, (c) privacy notice updated to mention GA4 data collection, (d) data deletion request protocol established. ICG's standard GA4 configuration for healthcare is DPDP-appropriate.

Compliance note: GA4 data policies, DPDP Act 2023.