Get your Lightspeed eCom tracking to 95%+ accuracy guaranteed in writing.
Lightspeed eCom merchants typically run a default Pixel install plus GA. There's no CAPI, no offline conversion sync to bring in-store sales back to Meta and Google, and no audience-quality signal. You're optimizing online ads for online-only conversions while in-store revenue is invisible. We fix that with a server-side gateway + offline-conversion pipeline.
Free30 minutesNo obligation
Lightspeed eCom · what breaks
Where Lightspeed tracking falls short
- 01
POS sales invisible to ads
Bricks-and-mortar revenue never reaches Meta/Google.
- 02
No CAPI, low EMQ
Online tracking lags.
- 03
Manual reconciliation
Most merchants give up trying to attribute store visits.
Lightspeed eCom · the fix
Outcomes — Lightspeed eCom
Online server-side CAPI
Recover the iOS gap.
POS offline conversion sync
Bring brick-and-mortar revenue into ad reports.
Unified Looker dashboard
Online + offline in one view (premium tier).
Lightspeed eCom · architecture
How a Lightspeed eCom order should reach the ad platforms
Lightspeed serves retailers who also sell in store, so the same online-versus-in-person separation that matters on Square matters here.
- 1
Click identifiers captured at first touch
Click IDs are captured in the theme at landing and written to a first-party cookie ahead of checkout.
- 2
The browser sends the fast, fragile copy
Theme code fires browsing and cart events. Checkout access is limited, so the browser path thins out at exactly the point that matters.
- 3
The order itself is the source of truth
The Lightspeed order, via the API or a webhook, is the truth, and it is where online orders can be separated from point-of-sale ones.
- 4
A server container sends the authoritative event
The order webhook posts to a GTM server container on your own subdomain, keyed on the Lightspeed order number, filtered to ecom orders.
- 5
Customer identity raises match quality
The order carries customer email, phone and shipping address, hashed server-side.
Lightspeed eCom · events
The event set we build on Lightspeed eCom, and where each one comes from
As with any omnichannel platform, the source filter is the most consequential piece of the configuration.
| Event | Fires when, on Lightspeed eCom | Key parameters | Sent from |
|---|---|---|---|
| view_item | A product page renders | item_id, value, currency, event_id | Browser + server, deduped |
| add_to_cart | The cart updates | item_id, quantity, value, currency, event_id | Browser + server, deduped |
| begin_checkout | Checkout is entered | value, currency, num_items, event_id | Browser + server, deduped |
| purchase | The order webhook fires for an ecom order | order_id, value, currency, items[], hashed email/phone/name/address, event_id | Server authoritative |
| refund | A refund is recorded | order_id, value, currency | Server only |
Lightspeed eCom · normal or broken
Omnichannel confusion on Lightspeed
The retail side of the platform is what makes the numbers look wrong.
Normal, not a fault
Lightspeed totals far exceeding online conversions
Point-of-sale revenue is included in the platform's totals and correctly excluded from ad conversions.
Inventory syncing between channels
A platform feature, unrelated to tracking.
Ad platforms report more conversions than you have orders
Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.
Recent days always look worse than they finish
Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.
Actually broken
Point-of-sale orders counted as ad conversions
Every campaign's reported return is inflated by in-store revenue.
Purchase tracked only from the confirmation page
Orders where the customer leaves after paying are never counted.
No order number on the conversion
Reconciliation impossible, duplicates undetectable.
Lightspeed eCom · prove
How we prove the Lightspeed eCom build is correct
The tag firing proves the tag fires. These prove the numbers are right.
Source of truth
Lightspeed order records
- Ecom and point-of-sale orders confirmed separated, with POS excluded from ad conversions.
- The order webhook confirmed delivering with the order number present.
- Reconciliation run against ecom orders only.
- Purchase count within a few percent of lightspeed order records for a fully closed week, matched on order ID rather than on totals.
- No order ID appearing twice in any platform's event log.
- Deduplication confirmed at every destination that supports it.
- Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
- The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.
Lightspeed eCom · free audit
What we check in the free audit
- POS sales invisible to ads
- No CAPI, low EMQ
- Manual reconciliation
Checked against
Lightspeed order records
Free30 minutesNo obligation
Lightspeed eCom · when not to buy
When a Lightspeed eCom rebuild is not what you need
We would rather say this now than three weeks into an engagement.
- Most of your revenue is in store. Online tracking is a small slice of the picture.
- Low online ad spend.
- You are replatforming the ecom side.
Lightspeed eCom · what we deliver
Deliverables — Lightspeed eCom
Server-side CAPI gateway
Online events
POS → Ad-platform sync
Daily offline import
GA4 e-com + offline events
Clean schema
QA + Notion runbook
Plus 30-day support
Written guarantee
95%+ tracking accuracy
Measured against Lightspeed order records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Foundation pixel install for your Lightspeed eCom store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.
- One-time fee · zero monthly · zero SaaS lock-in
- Lightspeed eCom dataLayer (clean spec)
- GA4 e-commerce events
- Meta Pixel · Google Ads tag
- TikTok Pixel · Microsoft UET
- Consent Mode v2 banner integration
- QA test orders + 7-day support
- No CAPI · no iOS recovery
1st-party server-side
Recommended$800One-time fee · most popular
The done-for-you package every Lightspeed eCom store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.
- One-time fee · save vs SaaS subscriptions over 5 years
- Fully recovered + built in 2–4 days · accurate data in 7 days
- Everything in browser-side starter
- 1st-party server-side GTM (your subdomain)
- Meta CAPI · full advanced matching · 8+ EMQ
- Google Enhanced Conversions (Web + Leads)
- TikTok Events API · Microsoft UET server
- Deterministic browser ↔ server deduplication
- Live EMQ verification + screenshots
- Notion runbook + 30-day support · zero recurring
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel running 1st-party server-side, end-to-end. For Lightspeed eCom brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.
- One-time fee · save 6-figure SaaS subscriptions over 5 years
- Everything in 1st-party server-side tier
- Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
- Klaviyo identity stitching (if used)
- BigQuery export (server logs + GA4)
- Looker Studio attribution dashboard (branded)
- Multi-region / multi-currency / EU residency
- GDPR-audit-ready Consent Mode v2 wiring
- 60-day support · optional retainer · no lock-in
FAQ
Lightspeed eCom questions, answered
Yes — daily store-sales upload via API.
More on Lightspeed eCom
- GuideBrowser vs Server Tracking: Which Events Belong Where
- GuideWhat an Ecommerce Tracking Rebuild Actually Involves (Start to Finish)
- Free toolFree Lightspeed audit
- ChronogolfConversion tracking for Lightspeed Golf (Chronogolf)
- Lightspeed → Google AdsConnecting Lightspeed to Google Ads
- Lightspeed → MetaConnecting Lightspeed to Meta Conversions API
WhatsApp