Conversion tracking for Homebot
You send ads to your "What's your home worth?" page, Homebot emails you about each new lead, and the Leads list grows. The counts never agree: Meta claims one number, Google Ads another, and the refi that funded four months later shows up nowhere. Homebot's lead pages live on Homebot, not your site, so your tags never see the signup and nothing in the lead record names the ad. We rebuild the loop from Homebot's own alerts and webhook so each lead, request and funded loan reaches Meta once by email, and Google Ads from a page you control.
Free30 minutesNo obligation
Homebot · what breaks
What goes wrong with Homebot
- 01
Your Pixel never sees the signup
Homebot's lead pages are unique to your account and can't be customized, so your Meta Pixel and Google tag stay on your site. An ad click to the Homebot page counts a view at best, and smart bidding learns from clicks instead of signups.
- 02
Address lookers get counted as leads
A visitor types an address, sees the teaser value and leaves. Homebot creates the lead only when an email opens the full report. Count the visit and your cost per lead reads far lower than it is.
- 03
Database engagement looks like ad results
A past client opening their digest or requesting a CMA lands the same kind of email alert and activity-feed entry as a brand-new lead. Count every alert as a conversion and your ads get credit for people you closed years ago.
- 04
The refi funds long after the click
Homebot nurtures with a report about every 30 days, so the lead that applies does it months later. By then Google Ads and Meta have stopped listening unless the funded loan goes back by hand, matched to the lead.
Homebot · the fix
What changes — Homebot
Each new Homebot lead reported once
Taken from the new-lead event, not the page view. Meta gets it matched on the email Homebot captured; Google Ads gets it from the widget on your own page, once we've confirmed the widget captures the email on your site.
Intent tracked as its own step
CMA requests, listing pre-quals, showing requests and direct messages become a qualified-lead conversion, separate from the raw signup.
Funded loans back in the platforms
Closed loans and transactions from your LOS or closing records go back to Google and Meta against the original lead, so return on ad spend is real.
Homebot · architecture
What Homebot actually lets you do
Everything below is from Homebot's help center. Where the docs are silent, it's a check, not an assumption.
- 1
Lead pages Homebot hosts
Homeowner, Buyer and Property Search pages, unique to your account and not customizable; Buyer and Property Search need a lender co-sponsor. No documented slot for a Pixel, Google tag or GTM.
- 2
Widget on your own site
Share, Embed a Widget, paste the code into your site. Homeowner, AirBnB Potential or Buyer types. We confirm whether the signup completes inside the widget.
- 3
New-lead alert and Leads list
Each signup emails you and lands on the Leads list; the activity feed logs it as a new client lead from a widget or PURL, without naming the campaign.
- 4
Webhook client via Zapier
Create Webhook Client posts events with a source, an action such as cma-request or homeowner-direct-message, a client ID and a timestamp; Find Client by ID returns name and email. The documented examples are engagement events, so a signup event is a check. No address, no click ID.
- 5
CRM connections
Follow Up Boss gets activity tags such as HB_Alert-home-digest-view; Total Expert, Usherpa, Sierra Interactive, Jungo and SureFire have guides. The Open API exposes 60+ events to lenders, banks and credit unions on request.
- 6
No ad-platform sending
Nothing documented posts conversions to Google Ads or Meta, and Homebot can't be embedded in a CRM by iframe.
Homebot · diagnose
Where Homebot tracking breaks, in diagnostic order
Start with the landing destination, because on Homebot the usual fault is a lead the platforms never saw, not one they counted twice.
- 01
Find where the ad actually lands
A Homebot-hosted lead page means no tag of yours fired on the signup.
- 02
Compare the Leads list with platform leads
Over a closed week, per email address.
- 03
Check what the "lead" conversion really is
Outbound click, teaser view or opened report? Only the last one is a lead.
- 04
Split new leads from database activity
CMA requests and digest views from past clients are not acquisition.
- 05
Trace one lead to funding
Did the funded loan ever go back to Google Ads or Meta? Usually not.
Homebot · prove
The QA evidence — Homebot
Run on a real signup through your live lead page or widget from an ad-tagged URL, not from the admin preview.
Source of truth
Homebot's Leads list and activity feed (new client lead, CMA and pre-qual requests) reconciled to your LOS or closing records for funded loans
- One test signup from an ad-tagged URL, with the new-lead email received and the webhook checked for a matching event.
- Exactly one lead conversion for that signup in Meta Events Manager, deduplicated on its event ID.
- Teaser-only address lookups confirmed absent from the lead count.
- A CMA or pre-qual request reported as its own event, once.
- Digest views and CMA requests from existing clients confirmed excluded.
- One funded loan sent back and matched to the original lead's email and date.
- Repeated 30 days later and after any change to your Homebot share settings or site.
Homebot · free audit
What we check in the free audit
- Find where the ad actually lands
- Compare the Leads list with platform leads
- Check what the "lead" conversion really is
- Split new leads from database activity
- Trace one lead to funding
Checked against
Homebot's Leads list and activity feed (new client lead, CMA and pre-qual requests) reconciled to your LOS or closing records for funded loans
Free30 minutesNo obligation
Homebot · when not to buy
When you don't need this on Homebot
Plenty of loan officers and agents use Homebot in ways that need no attribution work.
- If you run no ads to your Homebot pages and use it only to nurture past clients, the Client Engagement Portal already tells you who to call.
- If your ads land on your own page with the widget and the Pixel's lead count matches the Leads list, leave it alone.
- If you get a handful of leads a month, a spreadsheet with each lead's email and ad source beats a build.
- If your CRM already sends funded loans to Google Ads and Meta, we only check the Homebot leg and tell you if it's fine.
Homebot · what we deliver
The event map on Homebot
Lead page or widget reached
Page-level signal, fired from your own site when the ad lands on a page carrying the embedded widget.
New client lead
The lead conversion, from Homebot's new-lead email alert, with the Zapier webhook added once we confirm it carries the signup event. Keyed on the email the prospect gave to open the report.
Digest viewed, refi details viewed
Engagement, logged for reporting and kept out of the conversion columns.
CMA, pre-qual, showing or direct message
The qualified-lead conversion, one per contact, valued by what the request is worth to you.
Loan application started
For lenders, Homebot logs the click on your financing CTA; the application itself comes from your LOS.
Loan funded or transaction closed
The money event, from your closing records, sent back against the lead. Client referrals and past-client re-engagement are excluded.
FAQ
Homebot questions, answered
Not that Homebot documents. The help center calls the lead pages unique to your account and not customizable, and mentions no tracking field. If you need your own tags, put the widget on a page you control and send traffic there.
Not in anything Homebot documents. The activity feed logs a new client lead as coming from a widget or your personalized URL, and the webhook carries a client ID, not a click ID. Attribution is rebuilt outside Homebot, keyed on the lead's email.
For Meta, through the Zapier webhook client: a documented event such as a CMA request arrives with its action and client ID, Find Client by ID returns the email, and the hashed email goes to the Conversions API with one event ID per contact. Whether the raw signup arrives the same way is something we confirm; if not, the new-lead alert email feeds it. Google's enhanced conversions for leads expects the email captured by a tag on your own website form, so Google Ads traffic lands on your page with the widget.
All three, as separate events. The signup trains bidding on volume, the CMA or pre-qual request on intent, and the funded loan is the number you run the business on.
No. They were in your database before any ad ran, so they're retention. We key on the new client lead event so only prospects who signed up through a lead page or widget count.
It helps. Follow Up Boss receives Homebot activity as tags and the others have documented syncs, so the CRM is where lead, request and funded loan meet. The feed to the ad platforms still has to be built; none of those integrations send it.
More on Homebot
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Homebot, and what their bookings feed
- Unanet CRMOur pursuits live in Unanet CRM. Google Ads has no idea which ones it started.
- AnchorYour ads bring inquiries, but Google never sees who signs in Anchor
- BonzoBonzo is full of mortgage leads. Which ads actually funded loans?
- ConnectWise CPQConversion tracking for ConnectWise CPQ
- SteerSteer conversion tracking: which ads actually brought cars into your bays?
- Builder PrimeYour rep marks the job Sold in Builder Prime. Google Ads never finds out.
- PlaygroundPlayground conversion tracking that credits ads with enrollments
- AgencyZoomYour ads count quote requests. AgencyZoom knows which ones you wrote.
