Ecwid Chatbot Builder

Ecwid by Lightspeed takes a different approach to e-commerce: instead of hosting your store on its own domain, it lets merchants embed a full storefront into any existing website - a WordPress blog, a Wix site, a hand-built HTML page, even a Facebook page. Hundreds of thousands of small businesses use it precisely because it meets them where their web presence already is.

That flexibility creates a specific support challenge: your store might live on several sites at once, and your customers ask questions wherever they happen to be shopping. Bolting a different chat tool onto each host site means fragmented conversations and settings scattered across platforms.

The Conferbot Ecwid app solves this at the right layer: it attaches the chat widget to your Ecwid store, not to any one website. Install the app once, paste your Chatbot ID, and the widget loads on your storefront wherever that storefront is embedded. Behind the widget sits the full Conferbot platform - a no-code visual flow builder, AI-powered answers, live agent handover, and a shared team inbox.

The only credential the app needs is your Chatbot ID. There are no API keys to manage and no code to paste into your host sites. Appearance and behavior are configured centrally in the Conferbot dashboard, so the same bot can also serve your main website, WhatsApp, or any other Conferbot channel.

This guide covers how the app works under the hood (OAuth, public app config, the storefront loader), real installation steps, what context is passed to the bot, use cases for Ecwid merchants, and an honest comparison with generic live chat options. The app is open source: Conferbot/conferbot-ecwid on GitHub, with the merchant guide on the Conferbot developer portal.

The Conferbot Ecwid app is a thin wrapper around the official Conferbot web widget embed, delivered the Ecwid-native way. Three pieces cooperate:

1. OAuth install

When you install the app from the Ecwid App Market, Ecwid redirects to the app's OAuth callback with an authorization code. The app exchanges it at Ecwid's token endpoint and receives an access token plus your store ID. That is the entire handshake - you never copy keys around.

2. Settings in Ecwid public storage

When you save your settings (Chatbot ID, embed type, on/off), the app writes them to your store's Ecwid app public storage via the Ecwid API. Public storage is Ecwid's built-in mechanism for making per-store app configuration readable by storefront scripts - no separate database lookup is needed at page load.

3. The storefront loader

On every storefront page load, Ecwid loads the app's registered storefront JavaScript. The loader reads your saved settings with Ecwid.getAppPublicConfig() and, if the widget is enabled and configured, injects the standard Conferbot loader:

<script src="https://cdn.conferbot.com/dist/v1/widget.min.js" async></script>

and boots it with:

window.ConferbotWidget("YOUR_BOT_ID", "live_chat", options)

The widget resolves everything else server-side from the Chatbot ID over Socket.IO (wdt.conferbot.com). No API key, no workspace ID, no per-site setup.

Try it before you sign up

The app offers a one-click demo bot: the public demo Chatbot ID (691c970890527a0468f9b2c9) works without any Conferbot account, so you can see a real AI conversation running on your storefront before creating an account at app.conferbot.com. When you are ready, build your own bot in the visual builder and swap in its ID.

There are two ways to get the Conferbot widget onto an Ecwid storefront: the app (recommended) or a direct embed in your site's custom-code slot. Both take minutes.

Option A: The Conferbot app (recommended)

One-click install from the App Market, and the app automatically passes store context to the bot (platform and store ID - Ecwid exposes no customer session to storefront scripts, as documented in the context section):

1. Install the Conferbot app from the Ecwid App Market - Ecwid runs the OAuth flow automatically and lands you in the app
2. Open the app settings: a Chatbot ID field and an on/off switch
3. Paste your bot's ID (or use the one-click demo bot to try it without an account). In the Conferbot dashboard the ID lives under Share > Embed into website; bare ID, full snippet, or dashboard URL all work - the app extracts the ID automatically
4. Save - the app writes your settings to Ecwid public storage, and the storefront loader picks them up via Ecwid.getAppPublicConfig() on the next page load
5. Open your storefront - on whichever site it is embedded - and the chat bubble appears. Conversations land in your Conferbot inbox tagged with your Ecwid store ID

Option B: Direct embed in your custom-code slot

The pre-app method still works: paste the canonical widget snippet into your storefront's custom-code / tracking-code box (on an Ecwid Instant Site: Settings > SEO, or a custom-code app):

<script src="https://cdn.conferbot.com/dist/v1/widget.min.js" async></script>
<script>window.ConferbotWidget("YOUR_BOT_ID", "live_chat");</script>

Note the trade-offs: a direct embed does not pass the platform and store ID context automatically (unless you hand-write the third options argument yourself), and it only covers the one site where you pasted it - the app follows your store to every embed location and manages the on/off state centrally.

Self-hosting the app (developers)

The app is open source, and you can run your own instance: register an app in the Ecwid Developer Portal with the OAuth redirect set to your app URL's /auth/callback, request the read_store_profile and update_store_profile scopes, and register the app's /storefront/loader.js as the storefront JS (External files). Then configure the client ID/secret in the environment and start the Node.js server. Full details are in the GitHub README and the developer portal guide.

Troubleshooting

If the widget stays blank after install: confirm the bot is published, the widget is enabled in the app settings, and the Chatbot ID is the 24-character hex value. The loader reads its config from public storage, so it does nothing until you have saved the settings at least once. Testing with the demo bot isolates setup problems from bot configuration.

The app keeps merchant-facing configuration to the essentials. Everything you will iterate on regularly - greetings, colors, behavior - lives in the Conferbot dashboard, where changes apply at runtime to every channel at once.

Setting	Description
Chatbot ID	Required. The 24-character hex ID from the Conferbot dashboard (Share > Embed into website). Bare ID, full snippet, or dashboard URL all accepted - the ID is extracted automatically.
Enable widget	Master on/off switch. Settings persist either way, so you can toggle without losing configuration.
Embed type	Floating chat bubble (live_chat, default) or popup window (popup_chat).
Widget script URL	Advanced. Leave as is for the Conferbot CDN; useful for staging or self-hosted widget builds.

Forgiving Chatbot ID input

The ID field is designed for real-world pasting. Whether you paste the bare 24-character ID, the entire embed snippet copied from the dashboard, or a dashboard URL that contains the ID, the app extracts and validates the ID before saving. Invalid input is rejected rather than silently stored.

Page-level control

The widget loads wherever your Ecwid storefront renders. To suppress it on specific URLs (for example, a landing page on a host site where you do not want chat), use the disabled URLs setting in the Conferbot dashboard under Customize - the widget checks the list at runtime, so no Ecwid-side changes are needed. Per-page-type toggles inside a store admin are a feature of the PrestaShop and WordPress versions of this integration, which run on platforms that own the whole page.

Where nothing else is stored

The app stores only botId, embedType, enabled, and scriptUrl in your store's public storage. It does not read your orders, products, or customer records - the requested OAuth scopes cover store profile access and the storage write, nothing more.

Transparency matters here, so this section is precise: the Ecwid app passes less context than Conferbot's other e-commerce integrations, and that is a deliberate consequence of where it runs.

What is passed

The loader boots the widget with a customData object containing exactly two fields:

Field	Example	Purpose
platform	ecwid	Lets flows and analytics identify the sales channel
storeId	12345678	Identifies which Ecwid store the conversation came from

What is not passed

No user identity object is attached - no name, no email, no customer ID - and no cart data. The Ecwid storefront runs as an embedded script inside a host page, and customer session state is not exposed to third-party storefront scripts the way it is to a server-side plugin on WordPress or PrestaShop. Rather than approximate or scrape, the app passes only what is reliable.

What this means in practice

• Visitors are anonymous until they introduce themselves. Build your flows to ask for a name and email when the conversation needs follow-up - Conferbot's lead capture blocks make this a two-tap step, and the details attach to the conversation from then on.
• The store ID does the routing work. If you run multiple Ecwid stores into one Conferbot workspace, flows can branch on storeId and agents can see which store each chat came from.
• Everything else works normally. AI answers, flows, handover, and the shared inbox are unaffected - the difference is only in what is pre-filled about the visitor.

If automatic customer identity and cart context are hard requirements for you, and your Ecwid store is embedded in WordPress, consider running the Conferbot WordPress plugin on the host site instead - it passes the logged-in WordPress user and WooCommerce cart data where those exist. For a standalone Ecwid storefront, this app is the right tool.

Ecwid's superpower is that a single store can live in many places at once: your main website, a WordPress blog, a Wix landing page, a partner's site. The Conferbot app is built around the same idea, and this is where attaching chat at the store level pays off.

The widget follows the store

Because the loader is registered with Ecwid as the app's storefront JavaScript, it loads wherever the Ecwid storefront renders. Embed your store on a second site tomorrow and the chat bubble is already there - no new snippet to paste, no second configuration, no separate chat account for each host site.

One inbox, one history

Conversations from every embed location land in the same Conferbot inbox, handled by the same flows and the same team. A customer who asked about shipping on your blog's embedded store and returns via your main site is talking to the same bot with the same configuration.

Consistent branding everywhere

Widget appearance is configured once in the Conferbot dashboard and delivered at runtime, so the chat looks identical across all host sites - even if the sites themselves have different designs. Update the greeting for a sale and every embed updates on the next page load.

Pairs naturally with other channels

Ecwid merchants often sell across several surfaces already. The same Conferbot bot serving your Ecwid storefront can simultaneously serve:

• Your main website via the standard widget embed
• WhatsApp, Messenger, and Instagram for social commerce
• Other store platforms if you run them - Shopify, Wix, BigCommerce

All of it managed from one dashboard with one analytics view. For a small team, that consolidation is usually worth more than any single feature - see our overview of omnichannel deployment for the full picture.

For the technically curious (or anyone evaluating what this app can and cannot touch), here is the full runtime story.

The write path

When you save settings, the app makes one API call: a PUT to Ecwid's app storage endpoint for your store (app.ecwid.com/api/v3/STORE_ID/storage/public), authenticated with the OAuth access token from install. The payload is a small JSON document: botId, embedType, enabled, and scriptUrl.

The read path

Ecwid exposes that document to the storefront through its JavaScript API. On page load, Ecwid loads the app's registered storefront file (loader.js), which calls Ecwid.getAppPublicConfig() to read the saved settings. This is Ecwid's sanctioned pattern for storefront apps: configuration flows through Ecwid's own infrastructure, and the storefront needs no call back to the Conferbot app's server to render.

Why this design is robust

• No per-pageload dependency on the app server. Once settings are saved, the app's backend could be briefly unreachable and your storefront widget would keep loading - the config lives in Ecwid, and the widget script lives on the Conferbot CDN.
• "Public" means non-secret by design. Only the Chatbot ID and display preferences are stored - the same values any visitor could read from a standard widget embed's page source. The OAuth access token never reaches the storefront.
• Enable/disable is instant and safe. The loader checks the enabled flag before doing anything; if you switch the widget off, the loader becomes a no-op on the next page load.

Tested end to end

The app's test suite drives the whole journey against a mock Ecwid - OAuth token exchange, settings save, public storage write - and finishes with a real-browser e2e test in which the actual CDN widget mounts on a storefront page via loader.js. The suite and the code are open source (MIT) at Conferbot/conferbot-ecwid.

Ecwid skews toward small and growing businesses - makers, local shops, side projects becoming main projects. The highest-value chatbot patterns reflect that reality:

1. Answering pre-sale questions instantly

Shipping costs and times, stock, materials, sizing, customization options - the questions that decide a purchase. A Conferbot flow plus AI answers handles them around the clock, so an evening visitor gets the answer while their intent is hot instead of an email reply tomorrow.

2. Support without a support team

Most Ecwid stores are run by one or two people. The bot absorbs the repetitive majority of questions, collects contact details for anything it cannot resolve, and queues the rest in the shared inbox for when you have a moment between orders.

3. Lead capture for restocks and launches

Sold out is a lead-generation moment: the bot collects emails for back-in-stock alerts, new product launches, or market dates. Because Ecwid visitors are anonymous to the widget, the conversational ask is the natural collection point.

4. Guided product choice

A short flow - "Who is it for? What is the occasion? What budget?" - walks a shopper to the right product the way you would at a market stall. This works especially well for gift-oriented and craft catalogs.

5. Order status deflection

Collect the order number and email in a flow, and hand over to you only when a human genuinely needs to look something up. Most "where is my order?" chats never reach your inbox.

6. Consistent presence across your embeds

If your store lives on your blog and your main site, the bot gives both the same professional, instant front desk - one configuration, one inbox, no gaps. Browse ready-made flows in the template library, and see the broader strategy in chatbots for e-commerce and free chatbot for your website.

The Ecwid app contains no appearance settings, by design. Widget styling and behavior are configured once in the Conferbot dashboard under Customize and delivered to the widget at runtime. The app never duplicates those settings, so there is nothing to keep in sync between the Ecwid control panel and Conferbot.

What you control from the dashboard

• Position - bottom-right or bottom-left, with offsets, so the bubble does not collide with host-site elements
• Colors and theme - brand colors for the launcher, header, and messages; light and dark theming
• Launcher and avatars - bubble icon, bot avatar, agent avatars
• Greeting and language - welcome message, placeholder text, widget UI language
• Behavior - auto-open rules, load delay, proactive prompts
• Disabled URLs - suppress the widget on specific paths across any host site

Why this matters more on Ecwid than anywhere else

Your storefront may render inside several differently-designed host sites. Central, runtime-delivered styling is what keeps the chat experience identical on all of them - and lets you restyle everything in one place when your brand evolves. A dashboard change takes effect on the next page load of every embed, with no cache clearing and no touching the host sites.

Embed types

• Floating chat bubble (live_chat, default) - the familiar corner launcher, unobtrusive inside a host page
• Popup window (popup_chat) - opens the conversation in a centered popup, a good fit when the storefront occupies a small region of the host page and a corner bubble would sit outside it visually

The same central configuration also applies to the bot anywhere else you deploy it - your website, WordPress, or messaging channels - one brand, everywhere.

Installing the app connects your Ecwid storefront to the full Conferbot platform - the same engine behind every Conferbot channel.

Visual flow builder

Build conversations in the drag-and-drop builder: greetings, button menus, FAQ branches, lead capture, conditional logic. Since Ecwid visitors arrive anonymous, well-built flows ask for a name and email at the moment follow-up becomes likely - and the template library includes e-commerce flows that already do.

AI answers

Connect AI models to answer free-text questions from your own content: shipping policy, product care, store story, FAQs. The AI covers the phrasing your buttons did not anticipate, with knowledge and boundaries you control from the dashboard.

Human handover

When a conversation needs you - a custom order, a complaint, a wholesale inquiry - the bot hands over seamlessly. You reply from the Conferbot shared inbox on desktop or mobile; the visitor sees one continuous conversation. Every chat is tagged with platform: ecwid and your store ID, so multi-store operators always know which storefront a conversation belongs to.

One inbox across channels

Chats from your Ecwid embeds sit alongside conversations from your website, WhatsApp, and any other connected channel - same assignment, tags, canned responses, and analytics. For guidance on when automation should hand off to people, see chatbots for e-commerce.

An Ecwid storefront is already a script running inside a host page, so merchants are right to ask what another script costs. The answer: almost nothing, by construction.

Async, non-blocking loading

The Conferbot widget script loads with the async attribute from the CDN, after the loader has read your config from Ecwid. It never blocks the host page's rendering or the Ecwid storefront's own boot. Products, prices, and the buy flow render exactly as fast as they did before, and the widget mounts into its own container without shifting layout.

No dependency chain at page load

The loader reads settings from Ecwid.getAppPublicConfig() - data Ecwid has already delivered to the page - so the widget needs no round-trip to the Conferbot app's backend to appear. There are exactly two external pieces: the loader file and the CDN widget script. Chat traffic itself flows over Socket.IO directly between the visitor's browser and Conferbot's servers.

SEO considerations

• The widget renders client-side after load and does not alter the host page's crawlable content, headings, or structured data
• No render-blocking resources are added, protecting Core Web Vitals on the host site
• Chat content is not indexed - your product and landing pages remain exactly what search engines see

Graceful when disabled or unconfigured

If the widget is switched off or not yet configured, the loader is a no-op - it reads the config, finds nothing actionable, and exits without injecting anything. No dangling scripts, no console errors on the host site. For general best practices on adding chat to a site, see how to add a chatbot to your website.

Ecwid merchants typically weigh three options for chat: an Ecwid App Market chat app, a generic chat snippet pasted into the host site, or a full helpdesk suite. An honest comparison by category:

Capability	Conferbot Ecwid app	Chat snippet on host site	Full helpdesk suite
AI-powered answers	Built in	Varies by provider	Usually a paid tier
No-code flow builder	Included	Usually chat-only	Included
Follows the store to every embed site	Yes, automatic	No - one snippet per site	No - one snippet per site
Setup effort	Install app, paste one ID	Edit each host site	Account, snippet, onboarding
Ecwid store identification per chat	Yes (storeId)	No	Manual
Multi-channel inbox (web, WhatsApp, more)	Yes	Varies	Yes, at suite pricing
Typical cost for a small store	Free plan; paid from $19/mo	Varies	Often per-seat pricing
Open source integration code	Yes (MIT)	Rarely	Rarely

The honest trade-offs: a plain chat snippet is fine if you have exactly one host site and only want human-to-human chat. Full helpdesk suites make sense for larger teams that need ticketing, SLAs, and knowledge-base products in one contract - at a correspondingly larger price.

Conferbot's case for Ecwid specifically: the store-level attachment (one install covers every embed), automation that works while you pack orders, and pricing shaped for small merchants - a genuine free plan, with paid plans from $19/month. And because the integration is open source, you can verify exactly what runs on your storefront.

You can have a working AI chatbot on your Ecwid storefront in the next few minutes - and you can try it before creating an account:

1. Install the Conferbot app on your Ecwid store; the OAuth flow completes automatically
2. Try the demo bot - use the one-click demo bot (691c970890527a0468f9b2c9) in the app settings and save. The widget goes live on your storefront with a working AI bot, no account needed
3. Create your own bot - sign up free at app.conferbot.com, build a flow in the visual builder or start from an e-commerce template, and publish
4. Swap in your Bot ID - copy it from Share > Embed into website, paste it into the app settings, save - done
5. Iterate from the dashboard - refine flows, connect AI answers, style the widget under Customize, and track results in analytics

The app is free and the widget is included in all plans, including the free tier - see pricing.

Resources:

• App source code on GitHub (MIT)
• Developer portal: Ecwid integration guide
• Guide: chatbots for e-commerce
• Guide: free chatbot for your website
• Store on another platform too? See the Shopify, Wix, WordPress, and BigCommerce integrations