Get your Ecwid by Lightspeed tracking to 95%+ accuracy guaranteed in writing.
Because Ecwid is embedded inside another site (WordPress, Wix, custom HTML), most pixel installs only fire on the parent page — not on Ecwid's product or checkout views. iOS users + cookie banners + cross-domain iframes = a tracking nightmare. We use Ecwid's storefront events + a server-side CAPI gateway so events fire reliably regardless of where Ecwid is embedded.
Free30 minutesNo obligation
Ecwid by Lightspeed · what breaks
Why Ecwid tracking is uniquely hard
- 01
Embedded inside another site
Pixels fire on the host, not on Ecwid views.
- 02
Cross-domain iframe = cookie loss
Safari ITP especially eats checkout sessions.
- 03
No server-side hook by default
Without a webhook gateway, iOS purchases vanish.
- 04
Native plans don't pass customer data
EMQ stays at 4–5.
Ecwid by Lightspeed · the fix
Outcomes — Ecwid by Lightspeed
Ecwid storefront events captured
view_item, add_to_cart, purchase — all firing.
Cross-domain dedup
Browser + server with consistent event_id.
Meta CAPI 8+ EMQ
Full advanced matching.
Webhook-driven Purchase
100% reliable, host-independent.
Ecwid by Lightspeed · architecture
How a Ecwid order should reach the ad platforms
Ecwid is a store embedded into someone else's site, which makes it the only platform here where the tracking has to work across two systems you may not both control.
- 1
Click identifiers captured at first touch
Click IDs are captured by the host site at landing and passed into the Ecwid JavaScript API, because the embedded store does not see the host page's URL parameters on its own.
- 2
The browser sends the fast, fragile copy
Ecwid's JavaScript API exposes page and cart callbacks that fire inside the embed. These are the correct hooks; a host-page listener will not see what happens inside the store.
- 3
The order itself is the source of truth
The Ecwid order webhook is the truth. The embedded confirmation view is not a page load and cannot be relied on.
- 4
A server container sends the authoritative event
The order webhook posts to a GTM server container on your own subdomain, keyed on the Ecwid order ID.
- 5
Customer identity raises match quality
The order carries customer email and billing address. Hashed server-side, these are the only strong identity signal available in an embedded store.
Ecwid by Lightspeed · events
The event set we build on Ecwid, and where each one comes from
Everything here depends on the JavaScript API and the webhook. Standard page-based triggers do not work inside an embed.
| Event | Fires when, on Ecwid | Key parameters | Sent from |
|---|---|---|---|
| view_item | The Ecwid API reports a product page view inside the embed | item_id, value, currency, event_id | Browser + server, deduped |
| add_to_cart | The cart callback fires | item_id, quantity, value, currency, event_id | Browser + server, deduped |
| begin_checkout | The checkout view opens | value, currency, num_items, event_id | Browser + server, deduped |
| purchase | The Ecwid order webhook fires against a paid order | order_id, value, currency, items[], hashed email/phone/name/address, event_id | Server authoritative |
Ecwid by Lightspeed · normal or broken
Embedded-store behaviors — Ecwid by Lightspeed
Almost every Ecwid tracking fault comes from treating the embed like an ordinary page.
Normal, not a fault
No page load when moving between store views
The embed changes state without navigating. Page-view triggers will never fire, and that is how embeds work.
The host site's analytics showing one page for the whole store
Expected without the API callbacks wired up.
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
Tracking installed on the host page only
The store's events are invisible. Typically only a single page view is ever recorded for the entire shopping journey.
Purchase tracked from a URL fragment change
Fragment-based triggers fire on back-navigation and refreshes, multiplying conversions.
Click IDs never reaching the order
The embed does not read the host page's URL, so nothing is attributable unless it is passed in deliberately.
Ecwid by Lightspeed · prove
How we prove the Ecwid build is correct
The tag firing proves the tag fires. These prove the numbers are right.
Source of truth
Ecwid order records
- Ecwid API callbacks confirmed firing for browsing, cart and checkout states.
- The order webhook confirmed delivering for a real paid order.
- Click IDs confirmed passed from the host page into the order record.
- Purchase count within a few percent of ecwid 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.
Ecwid by Lightspeed · free audit
What we check in the free audit
- Embedded inside another site
- Cross-domain iframe = cookie loss
- No server-side hook by default
- Native plans don't pass customer data
Ecwid by Lightspeed · when not to buy
When a Ecwid rebuild is not what you need
We would rather say this now than three weeks into an engagement.
- Your store is a handful of products with negligible ad spend.
- You do not control the host site and cannot add code to it. Much of this build requires that access.
- You are moving to a standalone store platform this quarter.
Ecwid by Lightspeed · what we deliver
Deliverables — Ecwid by Lightspeed
Ecwid storefront integration
JS + webhook
Server-side gateway
1st-party server-side GTM
Meta CAPI + Google EC + TikTok
Dedup-clean
QA + handover
Notion runbook
Written guarantee
95%+ tracking accuracy
Measured against Ecwid 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 Ecwid 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
- Ecwid 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 Ecwid 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 Ecwid 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
Ecwid by Lightspeed questions, answered
Yes — that's our most common Ecwid setup.
More on Ecwid by Lightspeed
- GuideServer-Side Tracking Explained: What It Is, How It Works, and Who Actually Needs It (2026)
- GuideServer-Side Tracking for Shopify: The 2026 Setup That Actually Works
- Free toolFree Ecwid audit
- Ecwid → Google AdsConnecting Ecwid to Google Ads
- Ecwid → MetaConnecting Ecwid to Meta Conversions API
- Ecwid → GA4Connecting Ecwid to GA4
WhatsApp