Microsoft Ads conversion tracking for chimney sweeps
A chimney sweep earns most of a year's revenue between September and December, which makes every annual average on every dashboard misleading. What Microsoft Ads adds on top of that is a mechanical requirement: msclkid has to reach the record that holds the money, because Microsoft can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in chimney sweeps, and what Microsoft specifically needs to accept it.
Free30 minutesNo obligation
Specific to Microsoft × Chimney sweeps
Microsoft Ads for chimney sweeps: older searchers, few clicks, phones
Track chimney sweeps on Microsoft Ads by installing UET, capturing msclkid on landing and storing it on the customer record, then importing completed jobs from the job system as offline conversion goals at invoiced value. Pair it with call tracking, because Bing's older searchers book by phone more often than by form.
Microsoft's search audience is older and desktop-heavy, which describes the typical homeowner with a fireplace well. It is also small: a sweep in one metro may see only a few dozen Microsoft clicks in October. That is too little for automated bidding on completed jobs, so treat Microsoft as a manually managed search line and use the imported job data to set budget, not to train a bid strategy.
The usual mess is an account imported from Google with the contact-form goal still primary and no call tracking attached. Fix it before the season: give Microsoft its own tracked number, record msclkid on the customer, and import two goals, sweeps and inspections in one and repairs in the other, valued from the invoice. Check that the job system writes msclkid to a proper field rather than a notes box the import can't read.
Seasonality hits harder on a small account. A campaign left at summer budgets misses the first cold week, and one left at October budgets in December spends against an empty calendar. Schedule the budget changes ahead of time, and when you compare Microsoft with Google, use cost per completed job inside the season only, because off-season months have too few Microsoft jobs to compare.
Microsoft · Chimney sweeps · what breaks
Why Microsoft under-reports for chimney sweeps
- 01
Annual averages hiding a four-month season
Cost per job in July and cost per job in October describe different businesses.
- 02
Inspections and repairs valued the same
A £90 sweep and a £3,000 reline are both one job in most reporting.
- 03
Phone bookings outside the measured funnel
Older homeowners call. A website-only measurement misses the larger half.
- 04
Msclkid never reaches the record
Microsoft's click identifier, appended when auto-tagging is enabled. It depends on the UET tag being present on the site — without UET, msclkid arrives in the URL and there's nothing consuming it, which is a common half-configured state on accounts imported from Google.
Microsoft · Chimney sweeps · the fix
What working looks like — Microsoft · Chimney sweeps
Completed jobs as the conversion
At the invoiced amount, from the job system.
Follow-on repair work joined to the original visit
So the inspection that found it gets the credit.
Season reported separately from the rest of the year
Because they are not comparable.
Microsoft · Chimney sweeps · architecture
How Microsoft and chimney sweeps actually connect
- 1
The conversion in chimney sweeps
The money event is a completed, invoiced job. A booked appointment in peak season is six weeks from being revenue and a share of them cancel.
- 2
Microsoft Ads needs a click to match
msclkid inside the import window, a conversion goal name matching one in the account, a timestamp and a value.
- 3
The identifier: msclkid
Microsoft's click identifier, appended when auto-tagging is enabled. It depends on the UET tag being present on the site — without UET, msclkid arrives in the URL and there's nothing consuming it, which is a common half-configured state on accounts imported from Google.
- 4
Where it gets sent from
The job system — completed and invoiced jobs by date, split by job type.
- 5
Deduplication and window
The same counting question applies: one conversion per click for lead-type goals, every conversion for ecommerce. Accounts imported from Google frequently carry over the goal structure and not the counting review, so it's worth reading every goal rather than assuming the import got it right. Check Microsoft's current offline import window and attribution settings directly. They resemble Google's closely enough to be assumed and differ enough to matter.
Microsoft · Chimney sweeps · events
The conversion map for chimney sweeps
Five events across a business where the second visit is usually worth more than the first.
| Event | What it means here |
|---|---|
| Enquiry, web or phone | Volume signal. Only the web half carries an identifier. |
| Appointment booked | Frequently weeks out in season. Not yet money. |
| Sweep or inspection completed | Low value, and the gateway to everything else. |
| Repair quoted | Where the real revenue is identified. |
| Repair completed and invoiced | The event worth optimizing toward. |
Microsoft · Chimney sweeps · diagnose
Diagnostic order — Microsoft · Chimney sweeps
- 01
Count records carrying msclkid
- 02
Extreme seasonality
Four months carry the year. Bidding strategies trained on summer data are wrong by October.
- 03
Two very different job values
Routine sweeps and structural repairs need separate conversion values or the average is meaningless.
- 04
Repair work booked as a new customer
If the job system starts a fresh record, the inspection that found the work loses its credit.
- 05
Read the upload's match rate and Microsoft's conversion goal diagnostics
Almost every Microsoft account we open was imported from Google Ads, and the import copies campaign structure without copying the tracking. The result is a live account spending money with UET missing, msclkid unconsumed, or conversion goals pointing at pages that don't exist on the site any more.
Microsoft · Chimney sweeps · prove
How it gets proven — Microsoft · Chimney sweeps
Source of truth
The job system — completed and invoiced jobs by date, split by job type
- Completed jobs reconciled per record against what each platform reports.
- Repair work joined to the visit that found it.
- Phone bookings counted separately with call tracking.
- Seasonal and off-season windows reported apart.
- The upload's match rate and Microsoft's conversion goal diagnostics read directly, not inferred from an upload succeeding.
Microsoft · Chimney sweeps · free audit
What we check in the free audit
- Count records carrying msclkid
- Extreme seasonality
- Two very different job values
- Repair work booked as a new customer
- Read the upload's match rate and Microsoft's conversion goal diagnostics
Checked against
The job system — completed and invoiced jobs by date, split by job type
Free30 minutesNo obligation
Microsoft · Chimney sweeps · when not to buy
When you don't need this — Microsoft · Chimney sweeps
- If Microsoft already reports conversions that reconcile against the job system within a few percent, this is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred records and count how many carry msclkid.
- If your Microsoft account is a straight import you've never separately configured, fix the account structure and UET installation first — offline import on top of an unconfigured account produces data nobody will trust.
Microsoft · Chimney sweeps · what we deliver
What gets built — Microsoft · Chimney sweeps
Click identifier captured and persisted
Through a booking that may be scheduled six weeks out in peak season.
Carried into the job system
Onto the customer record, not the individual job.
Completed job fires the conversion
At the invoiced value, after the work is done.
Follow-on work attributed to the first visit
The reline found in October belongs to whatever produced the inspection.
Dispatch via Microsoft's offline conversion import
Uploaded against msclkid, closely mirroring Google's approach. Because so many Microsoft accounts are imported wholesale from Google Ads, people assume full parity — verify the current column format and requirements in Microsoft's documentation rather than reusing your Google template unchanged.
Written guarantee
95%+ tracking accuracy
Measured against The job system — completed and invoiced jobs by date, split by job type. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Microsoft · Chimney sweeps questions, answered
Yes, as a small second search channel during the season. Its older audience fits, but volume is low, so manage it manually and judge it on completed jobs.
Through call tracking with a dedicated number, joined to the job system. Without it, most Microsoft-driven bookings go unrecorded.
Usually yes, at lower spend, because booking capacity in autumn is finite and pre-booking the season is worth something. What you should not do is judge summer campaigns against autumn benchmarks — they are not competing for the same job.
At its invoiced amount, and separately track the rate at which inspections turn into repairs. That rate, by campaign, is the number that tells you which traffic is actually worth having.
Yes, with call tracking. Without it you are measuring the minority of your funnel and every efficiency ratio you compute is wrong by a factor you have not measured.
Microsoft's click identifier, appended when auto-tagging is enabled. It depends on the UET tag being present on the site — without UET, msclkid arrives in the URL and there's nothing consuming it, which is a common half-configured state on accounts imported from Google.
Uploaded against msclkid, closely mirroring Google's approach. Because so many Microsoft accounts are imported wholesale from Google Ads, people assume full parity — verify the current column format and requirements in Microsoft's documentation rather than reusing your Google template unchanged.
By reading the upload's match rate and Microsoft's conversion goal diagnostics and reconciling against The job system — completed and invoiced jobs by date, split by job type. An upload that succeeds is not an upload that matched.
More on Microsoft · Chimney sweeps
- Chimney sweepsConversion tracking for chimney sweeps, measured in completed jobs
- Google Ads · Chimney sweepsGoogle Ads conversion tracking for chimney sweeps
- Meta · Chimney sweepsMeta Ads conversion tracking for chimney sweeps
RELATED GUIDES
More for chimney sweeps: other angles on the same outcome
- Chimney sweepsConversion tracking for chimney sweeps, measured in completed jobs
- Microsoft · Masonry contractorsMicrosoft Ads conversion tracking for masonry contractors
- Microsoft · Drywall contractorsMicrosoft Ads conversion tracking for drywall contractors
- Microsoft · Quote → closed jobHow to track quote request to closed job for Microsoft Ads
- Microsoft × Job SystemHow to reconcile Microsoft Ads against your job management system
- Microsoft · Septic servicesMicrosoft Ads conversion tracking for septic services
- Microsoft · Gutter installationMicrosoft Ads conversion tracking for gutter installation companies
- Microsoft · Deck buildersMicrosoft Ads conversion tracking for deck builders
Free · 30 min
Get Microsoft reporting what chimney sweeps actually earn
WhatsAppFree30 minutesNo obligation
