Heat pump equipment is moving again. ACHR News reports that, after a slow start to 2026, cooling equipment shipments posted six consecutive months of growth. Its report on heat pump shipment growth is a useful market signal, but it is not proof that a contractor's local demand has increased.
Shipments measure equipment moving through the industry. A service company still needs to determine whether homeowners in its territory are reading heat pump pages, requesting estimates, approving replacements, and producing collected revenue. That requires a campaign gauge with every connection labeled before fall calls hit.
Start with the readings you actually have
Homecomfortdispatch.com currently has 2,709 pageviews, 1,079 visitors, 2,631 AI crawls, and 1,298 search crawls. Those readings establish activity, including substantial machine access, but they do not establish demand or revenue. No assist data, CRM records, query data, or growth history exists.
That distinction matters. A pageview is not a homeowner. A visitor is not necessarily a prospect. A crawler cannot buy a heat pump. Until traffic connects to an identifiable action and eventually to a closed job, the honest report is reach without attribution.
Give each campaign link a wiring diagram
Create one UTM convention for every link used to distribute the heat pump article. Record utm_source, utm_medium, utm_campaign, and utm_content. Keep values lowercase, use a controlled list, and document what each value means. An email link and a social post should not share the same medium merely because both point to the same page.
Use a campaign name tied to the subject and launch period, such as heat_pump_fall_2026. Reserve utm_content for the placement or creative, such as newsletter_button or maintenance_email_text. This makes comparisons possible without relying on somebody's memory three months later.
Internal editorial links need discipline too. A practical article may explain financing questions, cold-weather operation, sizing, duct restrictions, or the difference between repair and replacement. When a reader needs broader protection context, one natural reference to coverage for home systems and appliances is enough. Do not turn every paragraph into an exit ramp.
Configure Pulse around meaningful actions
In Pulse, define a short event ladder before publication. At minimum, capture article_view, engaged_read, internal_link_click, phone_click, form_start, and form_submit. Record the page URL, original landing page, referrer, UTMs, and a first-party visitor or session identifier with each applicable event.
Set engaged_read using a documented combination of active time and scroll depth. The precise threshold matters less than applying it consistently. Keep phone clicks separate from completed calls unless call-tracking data confirms the connection. Likewise, form_start indicates intent, while form_submit indicates delivery.
Carry the source into the CRM
The estimate form should send both visible customer fields and hidden attribution fields. Capture first-touch source, latest-touch source, landing page, campaign, content value, Pulse identifier, and submission page. Preserve the original values when a customer returns instead of overwriting the first visit with direct traffic.
Map those fields into the CRM record automatically. Use defined stage rules: inquiry when contact information arrives, qualified when the request fits the service area and work type, estimate scheduled when an appointment is booked, estimate presented when pricing is delivered, won when the customer authorizes the work, and collected when payment posts. Dates should accompany every transition.
Join revenue by a stable lead or opportunity ID, not by customer name alone. The closed record should retain job type, sold amount, collected amount, campaign fields, and originating content URL. That is the working foundation of a closed-loop demand system for home-service firms, although the homepage link should be replaced with the matching service page once its URL is confirmed.
Run the monthly meter check
Once a month, verify that UTMs survive redirects, Pulse events fire once, hidden form fields populate, phone numbers route correctly, CRM source values remain intact, stage dates are present, and won jobs join to collected revenue. Sample several records manually from article visit through payment. Flag missing IDs, duplicate submissions, unexplained direct traffic, and revenue without a source.
The shipment story can justify testing a timely heat pump campaign. It cannot tell a contractor whether that campaign worked. A labeled measurement chain can. Build it before publishing, then treat every broken field like a loose control wire: find it, repair it, and test the full circuit again.