Two Ways to Integrate
Both paths lead to the same result: the Alpheris widget appears in the bottom right of your site and answers customer questions grounded in your knowledge base. Pick whichever is more convenient:
Path 1 — One-Click Connect
The fastest way. You enter your website URL in the dashboard, get briefly redirected, and you're connected. Your domain is automatically marked as verified, a unique install ID is generated, and the knowledge base sync is kicked off.
https://your-shop.com. With or without www both work — the www. variant is created automatically as well.Path 2 — Script Snippet
The snippet is the universal way and works on any WordPress installation, regardless of the theme or page builder. You'll find your personal code in the dashboard under Integration → Code. It looks like this:
<!-- Alpheris Chat Widget -->
<script src="https://alpheris.com/widget.js" data-alpheris-key="INSTALL_ID" crossorigin="anonymous" async></script>
<!-- End Alpheris Chat Widget -->Don't replace INSTALL_ID by hand — copy the ready-made code from the dashboard, where your real install ID is already filled in. The attribute is called data-alpheris-key and connects the widget to your shop.
Where the snippet belongs on WordPress
The snippet must load on every page — so the safest place is just before the closing </body> or in the global header. Common ways to do this in WordPress:
- Theme customizer / header-&-footer plugin: Many themes and plugins (e.g. "Insert Headers and Footers"-style extensions) offer a field for global footer or header code. Paste the snippet there and save.
- Theme file
footer.php: In a child theme, insert the snippet directly before</body>. Only recommended if you're comfortable with child themes, otherwise the change is lost on the next theme update. - Block editor / custom HTML block: Not recommended for site-wide integration — the snippet would only load on that particular page.
What gets synced
The first time the widget actually loads on your site (not preview mode, valid install ID), Alpheris triggers an embed sync for a WordPress connection. It pulls in your site's public content via the WordPress REST API:
| Source | Endpoint | What gets imported |
|---|---|---|
| Pages | /wp-json/wp/v2/pages | Title and text content of every published page |
| Posts | /wp-json/wp/v2/posts | Title and text content of every published post |
The content is processed into searchable knowledge and stored in your knowledge base as a source of type wordpress_api_full. The chatbot then answers customer questions grounded in this knowledge. Which content ends up there, how you add to it, and how to upload files is covered under Data Sources & Knowledge Base.
Requirement: a reachable REST API
The sync only works if your WordPress REST API is publicly reachable. Alpheris checks this in advance via /wp-json/. If your site returns 401, 403 or 404 here (e.g. because a security plugin blocks the REST API), the embed sync is aborted with a corresponding error.
WooCommerce products
Important to understand: the embed sync pulls in pages and posts via the WordPress REST API — it does not read the WooCommerce product catalog through a separate WooCommerce API. There is no native, bidirectional WooCommerce product or order connector like there is for Shopify.
Your WooCommerce product pages are still captured — as perfectly ordinary content pages of your website. So the chatbot can absolutely provide information about products based on the text, descriptions and FAQ content on those pages. What it doesn't do: pull live stock levels, real-time prices or order status from the WooCommerce database.
Domain & Security
When you connect, Alpheris binds the install ID to your site's verified domain. By default, strict domain mode is active: widget and chat requests are checked against the host of the embed. This means your key can't simply be misused on someone else's domain.
- The
www.variant of your domain is verified automatically as well. - You can add more domains in the dashboard — details under Domains.
- You configure the privacy notice and optional per-shop consent under Security & Privacy.
