> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Conversion Rate, Ecwid > Orders / sessions. Below 1.5% usually = checkout / page-speed issue, not traffic. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Orders / sessions. Below 1.5% usually = checkout / page-speed issue, not traffic. ## At a glance > Orders divided by sessions over the rolling 30 days. Below 1.5% on an Ecwid-embedded widget typically means the checkout flow or host-page speed is broken, not that traffic is bad. The single most diagnostic card on the Ecwid dashboard for "where is my funnel leaking?". | | | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `COUNT(orders WHERE PAID) / COUNT(unique_sessions_visiting_widget)` over 30D. | | **Source data** | Numerator: Ecwid orders. Denominator: Ecwid widget analytics (`/v3/{store-id}/reports/storefront-views`) or where connected, GA4 sessions on the host page filtered by `event_name = ecwid_widget_loaded`. | | **What "session" means** | A unique visit to the widget over a 30-minute window per device. Ecwid's first-party tracking does not require GA4 but supplements with it when both are connected. | | **VAT / tax** | Not relevant (rate). | | **Refunds / cancellations** | Refunded orders count toward the numerator (the conversion happened); cancelled-before-payment orders do not. | | **Currency** | Not relevant (dimensionless rate). | | **Channel scope** | Aggregated across widget instances. If the merchant runs the widget on three sites (WordPress + Instagram + Wix), the rate is for total sessions across all. | | **Bot filtering** | Sessions flagged as bot or crawler are excluded from the denominator. | | **Time window** | `30D vsP`. | | **Alert trigger** | `<1.5%`. The hero-tier "your funnel is broken" floor for an Ecwid embedded widget. Healthy Ecwid stores run 2 to 4%. | | **Roles** | owner, marketing. | ## Calculation Calculated automatically from your Ecwid data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example **A small UK hobby photographer running an Ecwid widget on their WordPress blog, rolling 30D ending 27 Apr 26.** | Metric | This 30D | Prior 30D | Change | | --------------------------- | -------- | --------- | ------- | | Widget sessions | 1,820 | 1,650 | +10.3% | | Orders (PAID) | 47 | 52 | -9.6% | | Conversion rate (this card) | 2.58% | 3.15% | -0.57pp | ```text theme={null} Conversion Rate = 47 / 1,820 = 2.58% Above the 1.5% alert floor but trending down materially ``` **What it means.** 2.58% is healthy for an Ecwid hobby store but down from 3.15% the prior month. Sessions rose 10% while orders dropped 10%, meaning the widget is reaching more people who are not converting. Two usual causes for this pattern: 1. **Traffic-source mix shifted.** A new content piece (e.g. blog post that went viral) brought in browsers rather than buyers. The traffic is real but the intent is lower. Check the host site's referrer breakdown. 2. **Checkout broke partially.** Possibly a Stripe webhook issue, broken coupon code, or shipping-rate misconfiguration. Test the checkout flow as a buyer to confirm. For this seller, the cause was a viral Reddit post that drove 600 of the 1,820 sessions in 4 days; conversion on those sessions was \~0.5% (Reddit traffic is browse-heavy). Excluding the Reddit traffic, the underlying conversion rate held at \~3.4%. The headline number under-represents the funnel health. The action: nothing to fix; the funnel is intact. Optionally, retarget the Reddit visitors with a follow-up email-capture campaign to convert browse-mode visits into eventual buys. ## Sibling cards merchants should reference together | Card | Why it matters next to conversion rate | What the combination tells you | | ---------------------------------------------------------------------------- | -------------------------------------- | ---------------------------------------------------------------------------------------------------- | | [Total Revenue](/nerve-centre/kpi-cards/ecwid/total-revenue) | Outcome. | CR up + revenue flat = AOV dropped; CR down + revenue flat = traffic surged. | | [Total Orders](/nerve-centre/kpi-cards/ecwid/total-orders) | Numerator. | Order count drops without traffic drop = funnel issue. | | [Average Order Value](/nerve-centre/kpi-cards/ecwid/average-order-value) | Trade-off. | High CR + low AOV = mass-market impulse buying; low CR + high AOV = considered-purchase niche. | | [Out-of-Stock Products](/nerve-centre/kpi-cards/ecwid/out-of-stock-products) | Blocking input. | OOS hero SKUs convert at 0%; rising OOS depresses CR mechanically. | | [Refund Rate](/nerve-centre/kpi-cards/ecwid/refund-rate) | Quality. | High CR + high refund rate = low-quality conversions; check what is being sold. | | [New Customers](/nerve-centre/kpi-cards/ecwid/new-customers) | Acquisition. | Sessions and new customers should track; if sessions outpace new customers, traffic is browse-heavy. | | [Top Products](/nerve-centre/kpi-cards/ecwid/top-products-by-revenue) | Conversion concentration. | Identify which SKUs drive the bulk of conversions; OOS on those is high-impact. | ## Reconciling against the vendor's own dashboard **Where to look in Ecwid's own dashboard:** > **Ecwid Control Panel (`my.ecwid.com`) -> Reports -> Storefront analytics** > Shows session count, order count, and computed conversion rate for the chosen window. **Why our number may legitimately differ from Ecwid's Control Panel:** | Reason | Direction | Why | | -------------------------- | ------------- | ----------------------------------------------------------------------------------------------------- | | **Session definition** | Marginal | Ecwid uses 30-minute inactivity windows; some merchants use GA4-style 30-minute event-based sessions. | | **Bot filtering** | Either | Ecwid filters known bot UAs; we additionally filter on suspicious behaviour patterns. | | **Time zone** | Boundary days | Ecwid uses store-local; we use UTC. | | **Multi-instance widgets** | Identical | Both sides aggregate across widget instances. | | **Mobile app POS** | Either | POS sessions are typically not counted in storefront analytics; we follow Ecwid's exclusion. | **Internal identity:** `ecwid_conversion_rate = ecwid_total_orders / ecwid_widget_sessions` over the same window. ***
Documentation cross-reference (for agencies running multiple platforms) * [`shopify.ecommerce_conversion_rate`](/nerve-centre/shopify/ecommerce_conversion_rate) * [`bigcommerce.bigcommerce_conversion_rate`](/nerve-centre/bigcommerce/bigcommerce_conversion_rate) * [`google_analytics.ga_ecommerce_conversion_rate`](/nerve-centre/google_analytics/ga_ecommerce_conversion_rate)
## Known limitations / merchant FAQs **What is a healthy conversion rate for an Ecwid hobby store?** 2 to 4% for a typical embedded widget. Top-quartile Ecwid stores hit 5%+, often when the host site is brand-aligned and traffic is heavily intent-driven (e.g. a print-shop site where visitors arrive ready to buy). **My CR dropped to 1.2%; what should I check first?** (1) Test the checkout flow yourself end-to-end (Stripe + PayPal). (2) Check whether a hero SKU is OOS. (3) Check page speed on the host site (Ecwid widget is heavy; slow host pages tank the rate). (4) Review traffic source mix; a sudden surge from low-intent sources (Reddit, organic social) depresses CR mechanically. **Why does my CR look so much lower than the GA4 e-commerce CR for the same site?** GA4 measures conversions of "all sessions on the site"; this card measures "sessions that loaded the Ecwid widget". The widget loads on product pages, not blog homepage / about pages, so the session denominator is smaller and the rate is higher here than in GA4. **Does mobile traffic affect my CR differently?** Yes. Mobile checkout on Ecwid widgets is typically 30 to 50% lower CR than desktop, primarily due to checkout-form friction. If your traffic is mobile-heavy, expect a lower headline CR. The drill-down view splits by device class. **My CR is 5%; is that abnormally high?** For mass-market it would be; for hobby Ecwid stores with brand-loyal audiences arriving from the host blog, 5% is achievable and healthy. Best-in-class print sellers and zine makers hit 6 to 8% on niche audiences. **Does this include sessions where the widget failed to load?** No. Failed widget loads are excluded from the denominator; only successful widget renders count. If your widget has loading issues, CR looks better than reality but order count drops. **Can I see CR by traffic source?** Yes; the drill-down view splits by referrer / source. Use it to identify which channels have low CR (browse-mode) vs high CR (intent-mode) and adjust marketing spend accordingly. **Why is the alert at 1.5% and not 2% or 3%?** 1.5% is the rule-of-thumb floor for an embedded-widget store; below this, the funnel is almost always structurally broken. 2 to 4% is healthy; 3% is the comfortable median. Setting the alert at 2% would generate too many false positives during normal weekly volatility on small stores. **Will the card pick up Instagram-Shop conversions?** Only if the Instagram Shop links to the Ecwid widget (rather than using Instagram-native checkout). Instagram-native checkout does not flow through Ecwid; native conversions are not counted here. *** ### Tracked live in Vortex IQ Nerve Centre *Conversion Rate* is one of hundreds of KPI pulses Vortex IQ tracks across Ecwid and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.