Google Analytics 4 for Real Estate Websites: A Setup Guide

A marketing manager at a mid-sized developer spends ₹4 lakh a month across Google, Meta, and a couple of property portals. At month end, the CRM shows 60 fresh enquiries. Nobody in the room can confidently say how many came from which channel, because the website analytics still treats a form submission and a homepage visit as roughly the same kind of event. This is not a rare situation — it's the default state for most Indian developer websites that migrated to Google Analytics 4 without redesigning how they measure anything.

GA4 is not simply "the new version of the old Analytics." It's a different measurement model built around events rather than sessions and pageviews, and if your property site's GA4 setup was auto-migrated or left on defaults, it is almost certainly under-reporting the things that matter — enquiry form submissions, WhatsApp clicks, brochure downloads, and site-visit bookings — while over-reporting things that don't, like generic pageviews. This guide sets up GA4 correctly for a real estate context, from first principles to the reports you'll actually use every week.

GA4's Event Model vs the Old Universal Analytics

Universal Analytics, the version most developer websites were originally set up on, organized data around sessions and pageviews, with events bolted on as a secondary category. GA4 flips this: everything — a pageview, a scroll, a form submission, a WhatsApp click — is an event, and you choose which events matter enough to mark as "key events" (GA4's current term for what used to be called conversions).

This matters practically because a default GA4 property, freshly connected to a WordPress or custom-built property site, will automatically capture pageviews, scrolls, and outbound clicks — but it will not automatically know that a "Contact Us" form submission or a "Call Now" button click is meaningful to your business. You have to tell it. Skip this step, and GA4 will faithfully report thousands of pageviews and zero meaningful conversions, which is exactly the blind-flying situation most developer marketing teams find themselves in.

India's property-marketing technology stack is also evolving quickly enough that getting measurement right now compounds in value: IMARC projects the India proptech market growing from around US$1.31 billion in 2025 to US$3.82 billion by 2034, a CAGR near 12.26% (IMARC, 2026) — as more budget flows into digital acquisition for property, developers who can prove which channel produced which enquiry will out-compete those still guessing.

The stakes are rising in step with the broader sector: IBEF estimates India's real estate market at roughly US$200 billion in 2021, on a trajectory toward US$1 trillion by 2030, already contributing around 7.3% of GDP (IBEF, Feb 2026), and proptech-focused venture funding has itself recovered from a 2023 trough of around US$123 million to roughly US$550 million across 32 deals in 2025 (Entrackr, 2025-26) — a clear signal that measurement and martech tooling for property marketing is becoming a serious, well-funded category rather than an afterthought.

Step-by-Step: GA4 Setup for a Property Site

1. Create a GA4 property (if you don't already have one separate from a legacy Universal Analytics property) under Google Analytics admin, and add a web data stream pointing at your project's live domain.
2. Install the GA4 tag — either directly via gtag.js, or through Google Tag Manager (GTM), which is strongly preferable for a property site because you'll need to fire multiple custom events (WhatsApp clicks, call clicks, brochure downloads) without editing site code each time.
3. Verify the base pageview and engagement events are firing using GA4's DebugView before doing anything else — a broken base install invalidates every event you build on top of it.
4. Define your key events. In GA4, go to Admin → Events, and mark the events that represent real business value (form submissions, WhatsApp clicks, call clicks, brochure downloads, site-visit bookings) as key events, distinct from ambient engagement events like scrolls.
5. Set up enhanced or custom event tracking for the actions unique to a property site — most importantly the click-to-WhatsApp and click-to-call buttons that portals and developer sites rely on heavily, which GA4 does not track out of the box and which require a GTM trigger on the relevant button or link.
6. Connect Google Ads (and, where feasible, Meta) to GA4 so that key-event data flows back into the ad platforms' own optimization signals — this is what lets Google's bidding algorithms actually learn to find more people who submit enquiries, not just people who click.
7. Build a small set of standing reports — funnel exploration from landing page to key event, and a source/medium breakdown of key events — rather than relying on the generic default reports, which are built for general websites, not high-consideration property purchases.

Real Estate Events to Configure

Set form_submit_enquiry and site_visit_booking as your primary key events for Google Ads conversion optimization; treat whatsapp_click, call_click, and brochure_download as secondary signals that inform lead quality but shouldn't be over-weighted in automated bidding, since a WhatsApp click is a much lower-commitment action than a scheduled site visit.

DPDP Consent, WhatsApp/Call Tracking, and NRI Segments

A few India-specific realities shape how this setup should actually be built, not just how it's described in a generic GA4 tutorial:

• Consent-first data collection is now a compliance expectation, not an optional nicety. Under India's Digital Personal Data Protection framework, developers should be securing clear consent before analytics and marketing tools capture personal data such as phone numbers submitted via forms — Deloitte India's overview of the DPDP Rules 2025 notes that consent must generally be secured before data is shared with third parties, with penalties for non-compliance running into the hundreds of crores in serious cases (Deloitte India, 2025). This guide is general information, not legal advice — work with a qualified privacy or legal professional to confirm your consent banner, cookie policy, and data-sharing configuration meet current DPDP requirements for your specific setup.
• WhatsApp and call tracking need explicit configuration, because unlike a form submission, these actions leave the website entirely — GTM click triggers on the specific link elements (wa.me/ links and tel: links) are the standard way to capture them as GA4 events.
• Festive-campaign traffic bursts distort simple averages. A Diwali or Akshaya Tritiya campaign can 3–5x traffic for two weeks; build your reporting to compare campaign-period conversion rates against a rolling baseline rather than a flat monthly average, or the festive spike will make every other month look artificially weak by comparison.
• Regional-language landing pages need their own tracking dimension. If you run Hindi, Marathi, Tamil, or Telugu variants of a landing page, tag them with a custom parameter (e.g., page_language) so you can see whether a regional-language variant actually converts differently from the English default — often it does, in either direction.
• NRI traffic deserves geography-level segmentation. Configure GA4's audience or exploration reports to break out sessions from the Gulf, the US, and Singapore separately, since these segments typically convert on a longer timeline and respond better to WhatsApp or scheduled-call contact than to same-day form follow-up, given time-zone gaps.
• End-user demand, not just investor demand, should shape which events you weight most heavily. ANAROCK's Consumer Sentiment Survey H1 2025 found that more than 65% of roughly 8,250 surveyed respondents across 14 cities identified as end-users rather than investors (ANAROCK via MediaBrief, Sep 2025) — reinforcing why deep-intent events like site_visit_booking, which end-users are far more likely to complete than speculative investors, deserve more analytical attention than raw traffic volume.

Mini Scenario: A Chennai Developer Attributes a Booking Correctly

A developer running two live projects in Chennai launches a two-week Google Ads campaign around a specific project's near-completion possession status, alongside their always-on Meta retargeting and organic portal listings. Before the campaign, their GA4 setup only tracked generic pageviews — so at the end of the campaign, all they could say was "traffic went up."

After configuring form_submit_enquiry, whatsapp_click, and site_visit_booking as key events, tagged with UTM parameters carried through from each ad, they can see in a GA4 exploration report that the Google Ads campaign drove 34 WhatsApp clicks and 11 form submissions directly attributable to its UTM tags, while Meta retargeting — running the whole time in the background — quietly produced 6 form submissions from users who had visited the site organically weeks earlier. Cross-referencing this against their builder leads records, where each enquiry carries a source tag, they confirm that three of the Google Ads leads converted to actual site-visit bookings within ten days — a conversion rate they can now compare directly against the campaign's spend, something they could not do with pageview counts alone.

Building Useful Reports and Audiences

Once key events are configured, the reporting work that actually pays off is narrower than the default GA4 interface suggests:

• A landing-page-to-key-event funnel exploration, showing where visitors drop off between arriving on a project page and submitting an enquiry or clicking WhatsApp — this usually surfaces one or two friction points (a slow-loading brochure, a form asking for too much upfront) worth fixing before spending more on traffic.
• A source/medium breakdown of key events, not just sessions — sorted by form_submit_enquiry and site_visit_booking counts, so budget conversations are grounded in enquiries, not clicks.
• A remarketing audience of brochure downloaders and WhatsApp clickers who did not submit a form, since this group has shown clear interest without converting and is typically the highest-value retargeting audience available.
• A project-level view, using the project_page_view custom parameter, to see which of your live listings — published and kept current through publishing projects — are pulling disproportionate interest relative to their ad spend.

Pro Tips

1. Use Google Tag Manager, not hard-coded gtag.js calls, so your marketing team can add or adjust event triggers without needing a developer for every change.
2. Name events consistently and document them in a shared sheet — form_submit_enquiry everywhere, never formSubmit on one page and contact_form on another, or your reports will silently split the same conversion into two buckets.
3. Set a UTM-tagging convention before launching any campaign, covering source, medium, campaign name, and — where relevant — the language variant, so attribution stays clean months later.
4. Cross-check GA4 key-event counts against your CRM or builder dashboard enquiry counts monthly — a persistent mismatch usually means a tracking gap, not a data-quality mystery.
5. Revisit your key-event definitions every couple of quarters as your site adds new actions (a new site-visit calendar tool, a new brochure format) — GA4 configuration drifts out of date quietly if nobody owns it.

Common Mistakes to Avoid

1. Launching without a consent mechanism for personal data capture, which creates both a compliance risk under DPDP and a data-quality risk if browsers or extensions later block untagged tracking.
2. Double-counting conversions by marking both a "thank you page view" and the underlying form-submit event as separate key events for the same action — pick one canonical trigger per real action.
3. Leaving WhatsApp and call clicks untracked entirely, which for many Indian property sites represents the majority of real contact-intent actions, not a minor edge case.
4. Treating all key events as equally valuable in Google Ads bidding, which can lead the algorithm to over-optimize for a low-commitment action like a WhatsApp click at the expense of higher-value site-visit bookings.
5. Never checking DebugView after a site redesign, which is when tracking most commonly breaks silently — a new template or button component can quietly drop the click trigger a GTM tag depends on.

Where GA4 Fits With Your Broader DrawMagic Setup

GA4 tells you what happened on your website; it does not manage your actual enquiry pipeline. That's the job of your builder dashboard and builder leads system, where each enquiry — regardless of channel — becomes a trackable, actionable record. The two should be cross-referenced regularly: GA4 for channel- and campaign-level attribution, your leads system for what actually happens to an enquiry after it arrives (contacted, site visit scheduled, converted). Every project you publish through publishing projects should be treated as its own trackable destination in GA4 from day one, rather than retrofitting tracking after the project page has already been live and unmeasured for months.

If you're deciding how much of your marketing budget to allocate toward better measurement tooling and AI-assisted campaign work versus raw ad spend, it's worth reviewing DrawMagic's pricing and credit plans — proper attribution usually pays for itself quickly once you can see which channel is actually producing bookings, not just clicks.

Attribution Windows and Multi-Touch Reality

A single Google Ads or Meta click is rarely the whole story behind an enquiry. A typical Indian property buyer visits a developer's site multiple times across several weeks — first from an organic portal listing, later from a retargeting ad, and finally converting after a direct visit prompted by a WhatsApp message from a friend. GA4's default attribution model (data-driven attribution, where enough data exists) tries to account for this, but a few practical adjustments make the reported numbers more trustworthy for a property business specifically:

• Extend your conversion lookback window beyond the GA4 default where your ad platform allows it. A 7-day click window, common in ad-platform defaults, badly undercounts a category where the average consideration period runs into weeks or months; a 30-day window is a more honest baseline for property campaigns.
• Don't discard "direct" traffic as unattributable noise. A large share of direct-traffic conversions in real estate are actually delayed returns from an ad or podcast a buyer saw weeks earlier and didn't click through at the time — treat a spike in direct conversions during or after a campaign as a plausible campaign effect, not an unrelated coincidence.
• Compare GA4's assisted-conversion view to last-click, particularly for your top-of-funnel channels (organic social, content, portal listings) — these channels are systematically undervalued by last-click reporting because they rarely get direct credit for the final form submission.

A Lightweight Reporting Cadence That Teams Actually Use

The most common failure after a correct GA4 setup isn't technical — it's that nobody looks at the reports on a predictable schedule, so tracking drift and campaign underperformance go unnoticed for months. A realistic cadence for a small developer marketing team:

Skipping the quarterly audit is the single most common cause of GA4 data quietly going stale — a site redesign or new form vendor can silently break a tracked event, and without a scheduled check, teams often don't notice until a full quarter's reporting looks unexplainably off.

Key Takeaways

• GA4 is event-based, not session-based — nothing is a "conversion" until you explicitly mark it as a key event.
• The events that matter for a property site (form submissions, WhatsApp clicks, call clicks, brochure downloads, site-visit bookings) are not tracked automatically and need explicit GTM configuration.
• WhatsApp and call-click tracking are non-negotiable for Indian property sites, where these channels often outnumber form submissions.
• Secure consent for personal-data capture in line with DPDP expectations, and consult a qualified professional to confirm your specific setup — this guide is general information, not legal advice.
• Tag regional-language landing pages and NRI-geography traffic as separate dimensions; they typically behave differently from your default-language, domestic-buyer traffic.
• Build reporting around campaign-period-vs-baseline comparisons to avoid festive traffic bursts distorting your monthly view.
• Cross-check GA4's key-event counts against your CRM or builder dashboard monthly to catch tracking drift early.
• Treat GA4 as the channel-attribution layer and your builder leads system as the pipeline system of record — use both together, not as substitutes for each other.

FAQ

Do I need Google Tag Manager, or can I just use gtag.js directly? GTM is strongly recommended for a property site because you'll likely need to add or adjust several custom events (WhatsApp clicks, call clicks, brochure downloads) over time, and GTM lets your marketing team do this without a developer editing site code for each change.

How long does it take to get reliable GA4 data after a proper setup? Basic event data is available immediately, but most teams need 4–6 weeks of live traffic across a mix of campaigns before source/medium and funnel reports are stable enough to make confident budget decisions from.

Is GA4 enough, or do I still need a CRM? GA4 tells you what happened on the site before contact; a CRM or leads system (like builder leads) tells you what happened after — both are necessary, and they answer different questions.

Ready to see which campaigns are actually producing bookings? Set up your builder profile, keep your live listings current through the project publisher, and track real enquiry outcomes in your builder dashboard.