Roofing Lead Attribution

Connecting a roofing enquiry to its source site, page and territory

A roofing enquiry is tied to its source the moment it's saved: the record stores which site it came from, the page the visitor was on, UTM source/medium/campaign where present, the referring URL, and — for a call — the specific tracking number dialed. Each site and each tracking number is assigned to one site and one territory, so a call or form that lands on a given number or domain has a known origin by construction, not by guesswork after the fact.

This matters because a roofing company evaluating a territory needs to know which site produced which enquiry, not just that "the network" produced leads this month. If your territory has one live site and one tracking number, the attribution is simple. If it has a site plus a secondary landing page running a specific campaign, the UTM parameters stored on the form submission separate the two without needing a second phone line.

What gets recorded on arrival

• Source site and page the enquiry originated from
• UTM source, medium and campaign values present on the visit, where set
• Referrer URL, where the browser supplies one
• For calls: the exact tracking number dialed, tied to its assigned site and territory
• Timestamp and channel (call, form, chat) of the enquiry

Territory assignment then rides on top of the source data, not instead of it: a call to a tracking number assigned to your territory's site is a territory match by definition, independent of what the caller's ZIP turns out to be. The ZIP-to-territory match (covered on the lead routing and qualification pages) is a separate, additional check — attribution tells you where the enquiry came from, routing decides who it's delivered to.

Keeping calls, forms and repeat contacts from inflating lead totals

An enquiry count is only useful to a roofing company if the same homeowner calling twice, or filling out a form after already calling, doesn't quietly double the number. The system de-duplicates on phone number and on existing opportunity, so a second contact from the same person is linked to the existing lead record rather than created as a second, separate one.

This is a reporting integrity issue as much as a billing one. A roofing company reviewing "12 enquiries this month" from a territory needs that 12 to mean 12 distinct homeowner contacts, not 12 touches from a smaller number of people who called once, texted a follow-up, then called back two days later with a question. The de-duplication logic exists specifically so that number reflects unique opportunities.

What counts as the same contact

• Same phone number calling or texting again about the same property or service need
• A form submission from a homeowner who already has an open opportunity on record
• A chat conversation that continues an existing lead rather than starting a new service need

Where the same phone number clearly has a new, unrelated service need — a different property, a different problem months later — the record can open as a fresh opportunity rather than being folded into a closed one, but that judgment is made against the stored history, not assumed by default. The practical effect for attribution reporting is that your monthly lead count reflects distinct opportunities, and repeat contacts show up as activity on an existing record rather than as new volume.

Following the enquiry from delivery to an estimator appointment

Once a lead is saved and routed, the record's status can move through stages your team controls and reports: new, contacted, appointment, estimate, won, lost. The attribution trail doesn't stop at delivery — it's designed to keep accumulating evidence as the enquiry progresses, provided your team updates the status as it moves.

That "provided" is doing real work. The network can deliver a lead with full source and territory data attached, and can show when it was delivered and whether delivery succeeded. What it cannot do on its own is know that your estimator called back, booked a visit, or wrote a proposal — those are events inside your business, not events the network's tracking numbers or forms observe. If an appointment was booked through the public booking flow on a Calendar OS–connected site, that booking is visible on the record. If your team scheduled the visit by calling the homeowner directly and never updated the lead status, the system has no way to know that happened.

Why the appointment stage still matters for attribution

Even a partial record is useful. A territory where every delivered lead sits at "new" for months tells a different story than a territory where half the leads move to "contacted" within a day and a third reach "appointment." The gap between those two outcomes usually says more about your team's follow-up process than about the leads themselves, and attribution reporting is one of the tools that surfaces that gap instead of hiding it inside a single "leads delivered" number.

Connecting sold jobs and collected revenue when outcome data is available

When your team reports a lead as won and supplies a sold value, that figure attaches to the same record that carries the original source, site and territory data — which is what makes a closed-job ROI calculation possible at all. Without that reported figure, the chain stops at "delivered" or at whatever status your team last updated.

This is a deliberate design choice, not a gap we'd prefer to hide: the network does not have visibility into your invoicing, your collected payments, or your production costs, and it shouldn't claim to. A sold-value field only reflects what your team enters. A roofing company that wants an accurate ROI picture for a territory needs to treat updating won/lost status and sold value as part of using the program, not as optional record-keeping.

What a complete record enables

• Revenue attributable to a specific site and territory, summed across reported sold jobs
• Comparison of site rental or pay-per-call spend against reported revenue for the same period
• Identification of which lead sources (call vs. form vs. chat) are producing reported wins, not just contacts

A worked HYPOTHETICAL roofing economics example illustrates the mechanics, using assumptions a reader enters rather than a measured result: say a territory runs Site Rental at $997/month, and in a given month your team reports 6 delivered leads, with 2 marked won at a reported sold value of $9,500 each. The attribution record for that month would show $997 in rental cost against $19,000 in reported revenue — a ratio worth discussing on a Roofing Market Review, but built entirely from assumptions you supply, not a published or typical outcome, and it leaves out labor, materials and overhead entirely.

Reading attribution gaps without inventing a return on investment

Attribution has known limits, and naming them plainly is more useful to a roofing company than a dashboard that implies completeness it doesn't have. Cross-device journeys, dark social (a neighbor's text, a group chat, a referral with no link), direct or typed-in visits, and phone calls placed from a number a homeowner saved weeks earlier from offline memory are all paths this system — like essentially any marketing attribution system — cannot fully trace back to a specific campaign or ad.

What the system can tell you reliably: which site and tracking number a specific call or form used, whether that enquiry was a duplicate of an existing opportunity, and what status your team has reported for it. What it cannot tell you: the full marketing journey a homeowner took before they decided to call, or a guaranteed return on a given month's spend when outcome data is incomplete.

Treating gaps as information, not noise

• A high volume of direct or typed-in visits to a site's domain can suggest brand recall from an earlier interaction, even without a traceable first-touch source.
• Calls with no referrer or UTM data attached aren't errors — phone calls from a saved number rarely carry web analytics.
• A gap between delivered leads and reported outcomes usually reflects your team's reporting habits, not a tracking failure.

The honest version of a monthly attribution review names both what's known and what isn't, rather than forcing an ROI figure out of partial data. A roofing company that wants to compare a rented-site territory against its own paid search spend, for instance, should expect the same structural gaps on both sides — paid search attribution has its own blind spots for phone calls and offline conversion — and should treat any ROI comparison as directional, not exact.

Using a monthly source review to decide where to expand

A monthly review of source, delivery and reported-outcome data is the practical use of attribution: it tells a roofing company which territory, site or channel is worth the next dollar, based on what's actually been reported rather than on a general sense that "leads have been coming in."

The review works best as a short, repeatable routine: pull delivered-lead counts by site and channel for the period, check how many moved to contacted and appointment, check how many your team marked won with a sold value, and compare that against what was spent on rental or pay-per-call credits for the same period. Where a territory shows strong delivery but weak reported progression, that's usually a prompt to look at your team's follow-up speed before concluding the leads themselves are weak.

Bringing the review into a Roofing Market Review

A Roofing Market Review is the venue for turning a few months of this data into a decision about expansion: adding a second territory, moving from Pay Per Call to Site Rental in a market that's shown steady volume, or pausing a territory where reported outcomes haven't justified the spend. Inventory and territory availability are reviewed per market and are never guaranteed — the review confirms what currently exists in the markets you're asking about, using your own attribution history as part of the conversation rather than a published volume figure.

1. Pull delivered-lead counts by site and channel for the period under review.
2. Check status progression: how many moved to contacted, appointment, estimate.
3. Compare reported won jobs and sold values against rental or per-call spend for the same period.
4. Flag territories with strong delivery but weak reported progression as a follow-up-process question, not a lead-quality verdict.
5. Bring the summary to a Roofing Market Review to discuss expansion, plan changes or territory status.