Ecwid → Amazon Ads · Conversion tracking
Connecting Ecwid to Amazon Ads
Ecwid is a store that embeds into someone else's website, which makes it the only ecommerce platform here where the checkout runs inside a widget on a page you do not fully control. Amazon Ads spans two entirely different situations, and most guidance discusses them as though they were one. The join between them succeeds or fails on one thing: whether a click identifier only for off-Amazon destinations reaches the Ecwid order before the conversion happens, because Amazon Ads can only match a conversion it can tie back to a click it recognizes.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Ecwid → Amazon Ads
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their Ecwid → Amazon Ads tracking rebuild — in their own words, on camera.
Why this join usually fails
A click identifier only for off-Amazon destinations never reaches Ecwid
The single most common cause. The store runs inside an embedded widget, so the host page's scripts and the widget's own context are not the same environment. An identifier captured by the host page does not automatically reach the order, and a purchase inside the widget does not automatically fire the host page's tags.
A checkout inside somebody else's page
The host site and the store widget are two contexts. Tags installed on the host page routinely miss purchases entirely, and nobody notices because the site looks like it is working.
Per-order attribution promised on Amazon-completed sales
It does not exist and cannot be built. Amazon owns the checkout and does not release the join. Any proposal offering per-order attribution on sales completing inside Amazon is describing something unavailable.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. For off-Amazon conversions, reconcile normally against your own records. For on-Amazon sales, Amazon Attribution is aggregated and delayed by construction — it cannot be reconciled per order and is not meant to be.
Architecture
How Ecwid and Amazon Ads actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Ecwid holds the truth
Ecwid is authoritative for the order. Because it embeds into WordPress, Wix, Squarespace and plain HTML sites alike, the surrounding page's own analytics frequently has no idea a purchase happened.
Step 2
Amazon Ads needs a click to match
For off-Amazon destinations, an event with a value and the click identifier. For on-Amazon conversions, nothing — the measurement is not yours to do and Amazon Attribution provides aggregated reporting instead.
Step 3
The identifier is the bridge
A click identifier only for off-Amazon destinations, captured at the visit and carried into the Ecwid order. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send from your server when Ecwid reports the order paid. The widget's own client-side events depend on the host page still being open and the embed having initialized correctly, neither of which is guaranteed.
Step 5
Deduplication at the destination
Only relevant for off-Amazon conversions where both a tag and a server event exist. For on-Amazon purchases the question does not arise, because you are not measuring the conversion at all.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the Amazon Ads dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
A click identifier only for off-Amazon destinations present on the order
Visible on the record itself in Ecwid, not merely captured somewhere on the site.
Sent from the Ecwid order webhook
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Only relevant for off-Amazon conversions where both a tag and a server event exist. For on-Amazon purchases the question does not arise, because you are not measuring the conversion at all.
Reconciles with the source
Amazon Ads's count and Ecwid's records agree within a few percent over a closed window.
Actually broken
A click identifier only for off-Amazon destinations missing on most records
The store runs inside an embedded widget, so the host page's scripts and the widget's own context are not the same environment. An identifier captured by the host page does not automatically reach the order, and a purchase inside the widget does not automatically fire the host page's tags.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. The host site and the store widget are two contexts. Tags installed on the host page routinely miss purchases entirely, and nobody notices because the site looks like it is working.
Counted twice, or not at all
It does not exist and cannot be built. Amazon owns the checkout and does not release the join. Any proposal offering per-order attribution on sales completing inside Amazon is describing something unavailable.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Ecwid. A wrong number that nobody checks is indistinguishable from a right one.
Diagnostic sequence
Diagnostic order
Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.
- 1
Count orders carrying a click identifier only for off-Amazon destinations
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Ecwid and into Amazon Ads.
- 3
Open a recent Ecwid order and check its extra fields
If the identifier is not on the order, the host page captured it and never passed it across the embed boundary.
- 4
Establish which Amazon product and which destination you are running
On-Amazon and off-Amazon are different measurement problems, and conflating them wastes the entire engagement.
- 5
Read the match rate, not the success message
For off-Amazon conversions, reconcile normally against your own records. For on-Amazon sales, Amazon Attribution is aggregated and delayed by construction — it cannot be reconciled per order and is not meant to be.
Source-of-truth validation
How it gets proven
Against Ecwid's own records, not against either platform's dashboard.
- A click identifier only for off-Amazon destinations confirmed present on a live order.
- A real conversion followed from click through Ecwid to Amazon Ads.
- The ad product and destination confirmed in writing before any build, so the right measurement question is being answered.
- A purchase completed through the embedded widget, confirmed to report with the identifier attached.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later.
Straight talk
When you don't need this
Worth reading before paying anyone, including us.
- If Amazon Ads already reports conversions that reconcile against Ecwid's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred orders and count how many carry a click identifier only for off-Amazon destinations. Ten minutes, free, and it tells you whether any of this is worth doing.
- If your Ecwid store is a small add-on to a content site with modest volume, the native integrations may be adequate — measure the order volume before commissioning anything.
- If all your Amazon spend drives to Amazon listings, there is no conversion tracking build here — only a reporting exercise in Amazon's own tools.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run Ecwid → Amazon Ads (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What working looks like
A click identifier only for off-Amazon destinations on every order
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in Amazon Ads
8+ EMQOff-Amazon conversions appear against the campaign. On-Amazon sales appear in Amazon's aggregated attribution reporting, delayed.
Reconciled against the source
DedupedEcwid's own records are the reference, not either dashboard.
What gets built
Identifier capture into Ecwid
Capture the click identifier on the host page and pass it into the Ecwid order through its order-extra-fields or the storefront API, so it lands on the order record rather than staying on the page.
Event source: the Ecwid order webhook
Send from your server when Ecwid reports the order paid. The widget's own client-side events depend on the host page still being open and the embed having initialized correctly, neither of which is guaranteed.
Dispatch to Amazon Ads
Conversion upload for off-Amazon destinations. For on-Amazon sales, Amazon's own attribution reporting is the only view.
Reversals where they exist
Ecwid records refunds and cancellations against the original order, so reversals can be wired properly.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Wires the join and verifies it on a live conversion. Honest about its ceiling where the source can only be read from the browser.
- The join built and tested end to end
- Verified on a real conversion
- Reconciled against the source's own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
The join built server-side from the source's own records, so it does not depend on a browser being present when the conversion happens.
- Events sourced from the system of record, not the browser
- Identifier captured and persisted end to end
- Deduplicated at the destination
- Reversals wired where the source supports them
- 95%+ accuracy guaranteed in writing
Full 1st-party stack
Every destination fed from one place, plus monitoring so a broken join surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- All paid destinations from one container
- CRM and offline loop
- Refunds and cancellations reversed everywhere
- Monitoring per destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Why aren't my Ecwid conversions showing in Amazon Ads?
Almost always because a click identifier only for off-Amazon destinations never reached the Ecwid order. The store runs inside an embedded widget, so the host page's scripts and the widget's own context are not the same environment. An identifier captured by the host page does not automatically reach the order, and a purchase inside the widget does not automatically fire the host page's tags. Measure coverage before debugging the dispatch.
02What identifier does Amazon Ads need?
This is the distinction that decides everything. Sponsored formats driving to an Amazon listing produce conversions inside Amazon's checkout — no click identifier reaches you and no per-order join is available to anyone. Amazon DSP driving to your own site is an ordinary integration where a click identifier lands on your page and can be captured like any other network's. Establish which you are running before anything else.
03Where should the event come from?
The Ecwid order webhook. Send from your server when Ecwid reports the order paid. The widget's own client-side events depend on the host page still being open and the embed having initialized correctly, neither of which is guaranteed.
04How do I know it worked?
For off-Amazon conversions, reconcile normally against your own records. For on-Amazon sales, Amazon Attribution is aggregated and delayed by construction — it cannot be reconciled per order and is not meant to be.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourEcwid → Amazon Ads setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact Ecwid → Amazon Ads setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get Ecwid and Amazon Ads joined properly
Book a free 30-minute call. We measure your identifier coverage live on your own account, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
