Your RoofQuote PRO lead count doesn't match Google Ads or Meta. We fix that.
Your RoofQuote PRO dashboard shows one lead count, Google Ads and Meta show others, and none of them knows which ad sold a roof. The quote tool runs in an iframe from app.roofle.com, so your tags only hear what the widget announces. We wire those events correctly, keep address-only lookups out of bidding, and send signed roofs from your CRM back to the ad platforms.
Free30 minutesNo obligation
Roofle RoofQuote PRO · what breaks
What goes wrong with RoofQuote PRO tracking
- 01
Google Ads is bidding on people who only typed an address
Roofle's GTM guide suggests marking address_loaded as a GA4 key event. Imported as a primary conversion, it sends Smart Bidding after price-checkers who never left a name.
- 02
The estimator works, but GA4 shows nothing
The vendor's tag only fires when it finds the RoofQuote PRO script on the page. Wix and other iframe installs don't have it, so quotes never reach GA4 and your campaigns look like they're failing when they aren't.
- 03
Meta's Lead count never matches the dashboard
Roofle's recipe sends a browser-only fbq('track', 'Lead') and its own Meta steps disagree on which trigger to use. Without a matching Conversions API event, Safari and ad blockers drop leads and Meta optimizes on a partial count.
- 04
No one knows which ad sold the roof
The recipe keeps gclid and fbclid in the visitor's browser session, and Roofle's CRM integrations document no campaign fields. When a replacement or commercial reroof signs weeks later, nothing ties it to the campaign, so you can't cut the ads that only bring price-checkers.
Roofle RoofQuote PRO · the fix
What changes — Roofle RoofQuote PRO
Bidding learns from homeowners who asked for a price
Contact Form Submitted becomes the primary lead conversion; address lookups and map edits stay as secondary signals you can still read.
The click follows the lead into your CRM
gclid and fbclid captured at the estimator travel with the lead, so a signed contract in AccuLynx or JobNimbus can go back to Google Ads and Meta with its value.
One lead count across four screens
The Roofle dashboard, GA4, Google Ads and Meta reconcile on the same submissions, deduplicated on a shared event ID.
Roofle RoofQuote PRO · architecture
What RoofQuote PRO actually lets you hook into
Roofle documents its tracking better than most quote tools. Here's what its help center confirms, and what we still test.
- 1
Two install scripts from app.roofle.com
A slideout widget in the page head and a full-page embedded widget in the body, both loading the quote tool as an iframe from Roofle's domain.
- 2
Fifteen named JavaScript events
The iframe messages your page on steps like Address-loaded and Contact-form-submitted. Roofle says names won't change, though new ones may appear.
- 3
Roofle's GTM recipe
A Custom HTML listener maps seven events to roofquotepro_ dataLayer events and stores UTMs, gclid, fbclid and ttclid for the session. A starting point, not a finished setup.
- 4
Contact Form Completed webhook
Set under Developer, Webhooks. Roofle documents an External Url field holding the page address and query string; we confirm on a live lead whether gclid arrives in it.
- 5
CRM connections
AccuLynx, JobNimbus, Leap, ProLine and Rooflink are listed as CRM integrations, with HubSpot and Zoho through Zapier. Campaign fields in them aren't documented, so we check.
- 6
No native ad-platform server connection
Roofle points to Meta's GTM partner setup for the Conversions API and to GA4 import or a GTM tag for Google Ads. Server-side sending is ours to build.
Roofle RoofQuote PRO · diagnose
Where RoofQuote PRO tracking breaks, in diagnostic order
Start with what Google Ads is optimizing for, because a wrong primary conversion costs money every day it runs.
- 01
Check which RoofQuote PRO events are primary in Google Ads
An imported address_loaded key event is the most expensive mistake on this tool.
- 02
Confirm the listener loads on every estimator page
Especially Wix, iframe embeds and landing-page builders where the script check fails.
- 03
Count Meta Lead events on one test quote
One submission should produce one Lead, with matching browser and server event IDs.
- 04
Check event names as GA4 records them
Roofle's name template can produce spaces where your Google Ads import expects underscores.
- 05
Follow the click ID to the CRM record
Run a quote from a URL carrying a test gclid, then look for it on the new lead in AccuLynx or JobNimbus.
Roofle RoofQuote PRO · prove
The QA evidence — Roofle RoofQuote PRO
Run on a real quote through your live estimator page, with a Google Ads test click, not a preview.
Source of truth
RoofQuote PRO Analytics dashboard (Total Web Leads, Total Address Only Leads, leads by page) and the matching jobs in your roofing CRM
- A quote started from a gclid-tagged URL, with that gclid visible on the CRM lead.
- One Contact-form-submitted quote producing one Lead in Meta Events Manager, browser and server sharing the event ID.
- Address-loaded confirmed as a secondary conversion in Google Ads.
- Contact-form leads reconciled against the dashboard's Web Leads for a closed window.
- A signed contract uploaded to Google Ads and Meta with its value.
- Rechecked a month later and after any Roofle widget or website change, on both slideout and embedded pages.
Roofle RoofQuote PRO · free audit
What we check in the free audit
- Check which RoofQuote PRO events are primary in Google Ads
- Confirm the listener loads on every estimator page
- Count Meta Lead events on one test quote
- Check event names as GA4 records them
- Follow the click ID to the CRM record
Checked against
RoofQuote PRO Analytics dashboard (Total Web Leads, Total Address Only Leads, leads by page) and the matching jobs in your roofing CRM
Free30 minutesNo obligation
Roofle RoofQuote PRO · when not to buy
When you don't need this on RoofQuote PRO
Plenty of roofers are closer to right than they think.
- If you run Google Ads only, the slideout sits on a standard site, and conversions match Total Web Leads with address_loaded set to secondary, your setup is doing its job.
- If most quotes come from UTM-tagged links on yard signs, truck wraps and QR codes, the dashboard's ungrouped URL view tells you more than ad attribution.
- If the only fault is address_loaded marked primary, switching it to secondary in Google Ads takes five minutes, and we'll show you where on the call.
Roofle RoofQuote PRO · what we deliver
The event map on RoofQuote PRO
Estimator viewed and address loaded
From Roof-quote-pro-viewed and Address-loaded. Reported for funnel analysis, never used as a bidding goal.
Price lead submitted
From Contact-form-submitted. The primary lead conversion, carrying gclid, fbclid, UTMs and a shared event ID.
Product requested
From Product-requested-cta. A stronger intent signal when a homeowner picks a specific roof system, tracked once per session.
Get-help contact
From Get-help-form-submitted. Kept separate, because the dashboard files outside-service-area and data-unavailable cases alongside it, and those shouldn't train bidding.
Inspection set and contract signed
From your roofing CRM status, sent to Google Ads and Meta server-side with the contract value.
Excluded
Map interactions (slope changes, roof renames, add-roof clicks), invitation forms and QR or public-link visits with no ad click.
Written guarantee
95%+ tracking accuracy
Measured against RoofQuote PRO Analytics dashboard (Total Web Leads, Total Address Only Leads, leads by page) and the matching jobs in your roofing CRM. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Roofle RoofQuote PRO questions, answered
Not natively. Roofle documents two routes through Google Tag Manager: import GA4 key events into Google Ads, or fire a Google Ads conversion tag with the Conversion Linker on its widget events.
Track it, but not as a primary goal. A homeowner who sees a satellite view of their roof hasn't given you a way to reach them, and bidding on that teaches Google to find more browsers.
The recipe detects the widget by its script tag, and iframe installs like Wix often don't have one. Roofle suggests a custom-event trigger instead, and we confirm the message names your widget actually sends.
Roofle has no direct connection and points to Meta's GTM partner setup. We send the lead from a first-party server container with the browser Pixel's event ID, so Meta counts it once.
Yes, if the click ID reaches your CRM with the lead. Signed contracts then go back to Google Ads as offline conversions and to Meta through the Conversions API, with the contract value.
They can. Public-link and QR visits carry no ad click, so we keep them out of ad conversions and read them through UTM-tagged URLs in your Roofle dashboard.
More on Roofle RoofQuote PRO
- 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 Roofle RoofQuote PRO, and what their bookings feed
- Trimble ViewpointOur ads bring in leads. The contracts get signed in Vista or Spectrum. Google never finds out which ones.
- Sage constructionOur contracts live in Sage. Google Ads has no idea which ads won them.
- BuildertrendBuildertrend shows your sold jobs. Your ads still can't see them.
- CompanyCamYour ads count inspections. CompanyCam knows which jobs sold.
- JetbuiltJetbuilt shows the contract. Your ad accounts never hear about it.
- ProjulProjul conversion tracking for remodelers who can't tell which ads sign jobs
- BuildBookYour BuildBook pipeline shows signed remodels. Google and Meta never find out.
- JoistYour Joist estimates get signed. Google Ads never finds out.
Free · 30 min
Find out what your RoofQuote PRO leads are really telling Google and Meta
Free30 minutesNo obligation
