How to reconcile Microsoft Ads against your point-of-sale system
This is the check we run first on every account, written out so you can run it without us. It takes about thirty minutes and needs two numbers: what Microsoft says it produced, and what your point-of-sale system actually shows. The gap between them is the only honest measure of whether your tracking works — and if it comes back small, you do not need us.
Free30 minutesNo obligation
Specific to Microsoft × POS System
Microsoft Ads vs in-store sales: msclkid stops at the website
Microsoft's offline import keys on msclkid, which a walk-in customer never carries, so there is usually no per-record join with your POS. Check whether your account supports hashed email or phone matching for offline conversions. Otherwise compare a closed month's search-driven actions, such as store-locator clicks and calls, against in-store totals as a directional signal only.
Microsoft offline conversion import was built for leads that start with a click, so it expects msclkid on every row. Card terminals do not capture it. Check whether Microsoft's enhanced conversions or a hashed-identifier option applies to offline uploads on your account; if it does not, the practical bridge is a reserve-online or call-to-book step that stores msclkid before the customer walks in.
Microsoft reports conversions against the click date by default, like Google, so an in-store month never lines up neatly with its conversion month. The search audience also skews toward desktop users researching before a visit, which lengthens the gap between click and purchase. Use the conversion goals report filtered to location actions, such as directions and calls, and keep those goals separate from any online purchase goal.
A small Microsoft figure against in-store revenue is expected; a click-based platform cannot see a walk-in. Trouble shows up the other way: a Microsoft purchase goal that tracks your till totals. That almost always means the account was imported from Google with a shared conversion tag that a POS integration also feeds, so counter sales arrive as Microsoft purchases.
Microsoft × POS System · what breaks
Why Microsoft and your point-of-sale system disagree
- 01
Counter sales flowing into online conversions
Where the POS and the online store share an order table, the default integration sends everything. Reported return then climbs with footfall.
- 02
Store visits treated as attributable
Platform-reported store visits are modelled estimates, not counted events. Read them as directional and never sum them with online conversions.
- 03
Tips and taxes inside the conversion value
On food and service businesses tips are substantial and are not your revenue.
- 04
Offer codes never used
Without a code or a distinct landing path, there is no mechanism at all to connect in-store revenue to advertising.
Microsoft × POS System · the fix
What you get from this — Microsoft × POS System
A number instead of a suspicion
The likely cause, narrowed
A basis for deciding
Microsoft × POS System · architecture
What each side is actually counting — Microsoft × POS System
- 1
What Microsoft counts
msclkid inside the import window, a conversion goal name matching one in the account, a timestamp and a value.
- 2
How Microsoft attributes it
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.
- 3
The window it uses
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.
- 4
What your point-of-sale system counts
Transactions taken in person, which advertising cannot attribute to a click, found in Square, Lightspeed, Toast, Clover or whatever runs the till.
- 5
The filter that makes them comparable
In-person channel only, separated from any online orders in the same system.
Microsoft × POS System · events
Reading the gap — Microsoft × POS System
| What you see | What it usually means |
|---|---|
| 15%+ platform higher | Usually the wrong event entirely — the channel filter is missing, so counter sales are being counted as advertising conversions. |
| 20%+ platform lower | Usually structural — almost always correct rather than a fault. in-store revenue mostly cannot be attributed, and a small reported figure is the honest one. |
Microsoft × POS System · diagnose
Diagnostic order — Microsoft × POS System
- 01
Confirm both numbers cover the same period and channel
- 02
Counter sales flowing into online conversions
Where the POS and the online store share an order table, the default integration sends everything. Reported return then climbs with footfall.
- 03
Store visits treated as attributable
Platform-reported store visits are modelled estimates, not counted events. Read them as directional and never sum them with online conversions.
- 04
Tips and taxes inside the conversion value
On food and service businesses tips are substantial and are not your revenue.
- 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 × POS System · prove
How to know you did it right — Microsoft × POS System
Source of truth
your point-of-sale system — in-store transactions for a fully closed month
Microsoft × POS System · free audit
What we check in the free audit
- Confirm both numbers cover the same period and channel
- Counter sales flowing into online conversions
- Store visits treated as attributable
- Tips and taxes inside the conversion value
- Read the upload's match rate and Microsoft's conversion goal diagnostics
Checked against
your point-of-sale system — in-store transactions for a fully closed month
Free30 minutesNo obligation
Microsoft × POS System · when not to buy
When the answer is that you do not need us — Microsoft × POS System
- If almost all of your in-store transactions come from a channel with no click behind it, no tracking work will reach them — and knowing that is worth more than a build.
- 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 × POS System · what we deliver
The method, step by step — Microsoft × POS System
Pull what Microsoft reports
The upload's match rate and microsoft's conversion goal diagnostics.
Pull what your point-of-sale system shows
Export transactions by business date for a closed month, split by sales channel, and note the in-person share of total revenue.
Filter both to the same thing
In-person channel only, separated from any online orders in the same system.
Compare per record, not on totals
FAQ
Microsoft × POS System questions, answered
Check whether a conversion goal fires on an order confirmation that your POS also writes to. Imported Google setups often carry that shared tag across without anyone noticing.
Location actions such as directions and calls from local search, read as a trend against weekly in-store transactions rather than as a per-sale match.
Because you should know the size of the problem before anyone quotes you for it. If the gap is small, you have saved yourself a purchase. If it is large, you now know what you are buying rather than taking our word for it.
No. Both numbers come from systems you already own and neither leaves them. There is no tool to sign up for and nothing to upload.
Then compare totals for a closed period and treat the result as directional rather than exact. The upload's match rate and microsoft's conversion goal diagnostics is still the right place to read the platform's side.
Under five percent is working. Five to fifteen usually means reversals are missing. Above twenty is normally the wrong event being counted, not a broken tag — which is why debugging tags first wastes so much time.
Then fix the filter before drawing any conclusion. In-person channel only, separated from any online orders in the same system. A mismatch in scope produces a gap that looks like a tracking fault and is not one.
Book the free thirty-minute call and bring both numbers. We will tell you which of the causes above it is, and whether it is something you can fix yourself — which it sometimes is.
More on Microsoft × POS System
- Google Ads × POS SystemHow to reconcile Google Ads against your point-of-sale system
- Meta × POS SystemHow to reconcile Meta Ads against your point-of-sale system
- TikTok × POS SystemHow to reconcile TikTok Ads against your point-of-sale system
RELATED GUIDES
Systems of record beside pos in store, and the funnels it settles
- Microsoft × Enrolment SystemHow to reconcile Microsoft Ads against your application or enrolment system
- Microsoft × Invoicing SystemHow to reconcile Microsoft Ads against your invoicing system
- Microsoft · Reactivation → repeat purchaseHow to track lapsed customer reactivation to repeat purchase for Microsoft Ads
- Microsoft · Online → in-storeHow to track online research to in-store purchase for Microsoft Ads
- Microsoft · Auto repairMicrosoft Ads conversion tracking for auto repair and collision shops
- Microsoft · PhotographyMicrosoft Ads conversion tracking for photography businesses
- LoyaltyLion → Microsoft AdsConnecting LoyaltyLion to Microsoft Ads
- SpotOn → Microsoft AdsConnecting SpotOn to Microsoft Ads
Free · 30 min
Found a gap between Microsoft and your point-of-sale system?
WhatsAppFree30 minutesNo obligation
