Enough events
Google advises choosing one funnel stage with a relatively short conversion delay and at least 15 conversions a month (Google Ads Help). Meta’s Conversion Leads needs at least 200 leads a month (Meta for Developers).
Industry playbook · Real estate
An enquiry is not a buyer. Optimise to the earliest stage that proves intent and that the ad platform can still learn from, usually an attended site visit, and use bookings to check you picked the right stage.
Short answer
Optimise to the earliest stage that reliably predicts a booking and happens soon enough for the ad platform to learn from it. For most projects that is an attended site visit, not an enquiry. Enquiries are cheap and plentiful; bookings arrive too slowly and too rarely to steer bidding. Check the choice each quarter against actual bookings.
This guide is for developers and large brokerages running Google and Meta Ads in India and the UAE, with a short note for US multifamily developers.
Short answer
One form collects end users, investors, renters, brokers and people with the wrong budget or city, and every one counts as a lead. Bookings arrive weeks or months later, after revisits and family decisions, while campaigns keep spending. Launch weeks inflate enquiry volume further. An enquiry count measures reach, not buyers.
Ad platforms find more of whatever you count. If you count enquiries, they find people who fill in forms cheaply, which in property often means people browsing prices, brokers collecting inventory and renters who clicked the wrong ad. Sales then pays for those enquiries twice: once in media and again in calls that go nowhere. That is why the cheapest channel per enquiry is so often the most expensive per visit.
Original framework
A deeper outcome is not automatically a better signal. Choose the earliest stage that passes three tests.
| Stage | Who records it | Noise | Use as an ad signal? |
|---|---|---|---|
| Enquiry | Website form or Instant Form | High: renters, brokers, wrong budget, unreachable numbers | Only at launch; never to judge channels |
| Contacted, budget and location match | Pre-sales caller | Medium: depends on caller discipline | When attended visits are too few per campaign |
| Visit scheduled | Pre-sales or CRM | Medium: no-shows | Weak: flatters channels with casual interest |
| Visit attended | Site team or sales | Low | The default optimisation signal |
| Revisit or expression of interest | Sales | Low | Large projects with volume; often too sparse |
| Booking | Sales or finance | Lowest | Validation, not steering: too slow and too rare |
Google advises choosing one funnel stage with a relatively short conversion delay and at least 15 conversions a month (Google Ads Help). Meta’s Conversion Leads needs at least 200 leads a month (Meta for Developers).
Google’s click-through conversion window can be set up to 90 days, depending on the conversion source (Google Ads Help). Meta’s Conversion Leads needs the stage within 28 days of the lead, reached by 1–40% of leads, using Instant Forms.
Last quarter’s attended visits for this project or price band should line up with its bookings. If they don’t, the stage definition or the site team’s logging has drifted.
When a small project produces only a handful of attended visits per campaign, step down to “contacted, budget and location match”: it is noisier, but it happens often enough to steer.
Worked numbers
A residential project in India spends ₹2,40,000 in one month across Google Search and Meta Ads.
| Channel | Spend | Enquiries | Cost per enquiry | Visits scheduled | Visits attended | Cost per attended visit |
|---|---|---|---|---|---|---|
| Google Search | ₹1,50,000 | 120 | ₹1,250 | 18 | 6 | ₹25,000 |
| Meta Ads | ₹90,000 | 45 | ₹2,000 | 30 | 24 | ₹3,750 |
| Both | ₹2,40,000 | 165 | about ₹1,455 | 48 | 30 | ₹8,000 |
On cost per enquiry, Google is 37.5% cheaper than Meta. On cost per attended visit, Meta is about 6.7 times cheaper: ₹3,750 against ₹25,000. Only 6 of Google’s 120 enquiries visited the site; 24 of Meta’s 45 did.
Act on clear waste: add negatives for rent agreements, property jobs and other cities. Review the remaining search terms with sales before cutting budget, and exclude out-of-area enquiries.
Investigate whether Meta’s visits come from one creative or audience, and whether any were channel-partner walk-ins logged as Meta. Wait before moving large budget until bookings from these visits arrive.
The failure mode to watch: a channel-partner walk-in who once filled in an Instant Form gets logged as a Meta visit, inflating Meta’s figure. The “sourced by” field below prevents it.
Short answer
Use both and judge them on attended visits. Google Search captures buyers already searching for a location and configuration, but broad terms pull rental, job and legal-format searches. Meta reaches buyers before they search and can deliver more visits per rupee when the creative states price band and location. Your own visit data should set the split.
Short answer
Record each visit against the enquiry’s click ID or contact details, inside the platform’s conversion window. Google accepts offline conversions through the Data Manager API, and Meta accepts CRM events through the Conversions API. A spreadsheet is enough to start. Zephra can send lead stages to both platforms, where configured.
Three things decide whether a visit counts:
The site team needs to log six fields for a visit to be usable as an ad signal: lead ID or the phone or email that matches the enquiry; visit date; project visited; attended (yes or no); sourced by (ad, portal, channel partner or walk-in); and budget fit. See CRM lead stages for ad platforms, offline conversion import and conversion tracking.
Short answer
Never send portal- or channel-partner-sourced visits to Google or Meta as ad conversions. Record who sourced each visit at the site, report portal and partner visits separately, and agree one written tie-break rule for buyers who both enquired through an ad and arrived with a partner. Otherwise campaigns learn from buyers they didn’t bring.
In India, portals such as 99acres, MagicBricks and Housing.com and channel partners bring a large share of visits; in Dubai, Property Finder and Bayut play the portal role. All sit outside your ad accounts. The tie-break rule should be simple and logged at the visit, such as “the source that booked the visit owns it”, so the same buyer is never credited twice.
| Rejection reason | Likely cause | Ad change |
|---|---|---|
| Budget mismatch | Price band missing from ad or form | State the price band in creative; add a budget question |
| Wrong location | Broad geo or interest-based location settings | Tighten geo targeting; add city exclusions and negatives |
| Investor, not end user | Message about returns rather than living | Match the message to the buyer the project is for |
| Broker enquiry | No question about who is enquiring | Add a “buying for yourself?” form question |
| Unreachable number | No validation; low-intent form type | Validate numbers; test a higher-intent Instant Form |
Keep the reasons to a short fixed list so they can be counted. Junk leads from ads covers the diagnosis, and the sales handoff guide covers response times.
Short answer
In India, a project must be registered with the state RERA before it is advertised, and its advertisements must prominently show the regulator’s website address and the registration number; states add their own directions. In Dubai, property advertising needs a permit from the Dubai Land Department. Confirm current requirements with the regulator before launch.
This is not legal advice. Rules and their enforcement change; confirm current requirements with the relevant regulator and your counsel before launch. See Meta ads policy compliance and lead generation compliance.
Zephra creates and runs all campaign types on Google, Meta and LinkedIn, new or existing. Its free ad account assessment reviews recent account history and covers wasted spend, campaign structure, performance constraints and measurement gaps. Where configured, Zephra sends CRM lead stages such as attended visits to Google through the Data Manager API and to Meta through the Conversions API, using a CRM or a spreadsheet. Recommendations are labelled act, review, investigate or wait; changes follow your approvals, permissions and spend boundaries; and every change is recorded in an audit log. There is no rollback, but you can tell Zephra in chat what should be done instead. Read lead quality optimisation, Zephra for Meta Ads, Zephra for Google Ads, which lead stage to optimise for, cost per qualified lead the admissions equivalent in lead generation for educational institutions, and the other segments on industries.
Questions, answered
Because the sales team pays for them in calls. A ₹1,250 enquiry that never visits the site wastes budget and a salesperson’s time, while a ₹2,000 enquiry that visits is good value. Compare channels on cost per attended visit and, once bookings arrive, cost per booking. Cost per lead only shows which channel fills the CRM.
The attended visit for steering, the booking for validation. Visits happen within weeks and often enough for platforms to learn from; bookings arrive later and too rarely. Check each quarter that campaigns sending more attended visits also produce more bookings.
Follow each platform’s own guidance: Google advises at least 15 conversions a month on the stage you bid to, and Meta’s Conversion Leads needs at least 200 leads a month. Below that, use “contacted, budget and location match” and judge campaigns on attended visits in your own reporting.
Report them separately, with their own cost per visit, and never send them to Google or Meta as ad conversions. Mixing them in makes ad campaigns look better or worse than they are.
No. A shared sheet with the six visit fields, lead ID or contact, visit date, project, attended, sourced by and budget fit, is enough to start and to send visits back to the platforms.
Meta requires the housing special ad category for ads reaching the United States, Canada and Europe, and Google restricts housing ad targeting in the United States and Canada. Campaigns aimed only at India or the UAE aren’t covered by those policies, but NRI campaigns reaching those countries are. Local rules such as RERA and DLD permits still apply.
Yes, when each visit is recorded against the enquiry’s click ID or contact details. Google accepts offline conversions through the Data Manager API, and Meta accepts CRM events through the Conversions API. Visits must be recorded inside the platform’s conversion window to count. Zephra can send lead stages to both platforms, where configured.
Avoid major edits while bidding is still learning, and decide on visit data rather than day-one cost per enquiry. Fix clear waste, such as irrelevant search terms, straight away; hold budget and targeting changes until attended visits from the first weeks are logged.
Your account
Run a free ad account assessment: 10–15 minutes, no CRM needed, no campaign changes during the assessment. Or book a demo to see site-visit stages sent back to Google and Meta.