MsgHub WordPress plugin install

The MsgHub WordPress plugin drops the AI chat widget on any WordPress site in under 5 minutes — no theme edits, no FTP, no developer needed. Auto-detects logged-in users, plays nicely with WooCommerce, survives caching plugins. This guide covers install, configuration, and the most common gotchas.

Overview

The plugin is a thin wrapper around the MsgHub chat widget snippet — but with WordPress-native conveniences:

What the plugin actually does

It loads the MsgHub widget script (https://app.msghub.info/api/v1/widget.js) with your tenant's API key, applying display rules and identification data you've configured. That's it — small footprint, no shadow database, no PHP-side message processing.

Prerequisites

• WordPress 5.5 or newer. Older versions may work but aren't tested.
• Admin access to the WordPress site.
• A MsgHub tenant with the Chat Widget enabled in Settings and a tenant API key generated from the API Keys sidebar item.
• An HTTPS-enabled site (the widget script requires HTTPS).

Install

Activate

Configure the plugin

WooCommerce integration

If WooCommerce is installed and active, the plugin auto-detects it and surfaces commerce context to the AI:

• Cart contents — passed as session metadata; AI can answer "what's in my cart?".
• Order history — last 10 orders linked to the contact. AI answers "where's my order #4821?".
• Customer lifetime value — total spend; used for VIP routing rules.
• Currently viewed product — when widget is opened on a product page, the AI knows which product the customer is asking about.

Enable from MsgHub → Settings → WooCommerce tab. Granular toggles for each data type.

Caching plugin compatibility

Aggressive caching plugins can break logged-in user identification by caching the widget snippet with a previous user's data. The plugin handles this correctly, but for caches with custom rules, configure:

Test it live

Shortcodes & programmatic control

Trigger from a button

[msghub_chat_button text="Chat with us"]

Renders a styled button. Clicking opens the chat widget.

Open with a pre-filled message

[msghub_chat_button text="Ask about this product" prefill="I have a question about {product_name}"]

WooCommerce-aware placeholders: {product_name}, {product_price}, {order_id}.

From custom JavaScript

// Open the widget
MsgHubWidget.open();

// Open with a pre-filled message
MsgHubWidget.open({ prefill: 'I want to schedule a demo' });

// Pass extra metadata about the visitor
MsgHubWidget.identify({
  customer_id: 'CUST-4821',
  segment:     'enterprise-trial',
  source:      'google-ads-campaign-spring'
});

Troubleshooting

Widget doesn't appear after install + activate

• API key wasn't pasted or pasted with whitespace. Re-paste and Save.
• Display rule is hiding it (e.g. on all pages). Check Settings → Display Rules.
• Site is on plain HTTP. The widget requires HTTPS — install an SSL cert (Let's Encrypt is free).
• The widget domain (in MsgHub Settings) doesn't match your WordPress site domain. Add both www. and bare versions.

Widget appears but won't open when clicked

• A theme element has a higher z-index. Increase plugin's z-index setting to 9999999.
• A JavaScript error in another plugin is breaking the page. Check browser console (F12).
• Cache served stale widget script. Clear cache plugin's cache.

Logged-in user shows as "Anonymous" in MsgHub

• Identification toggle is off in plugin Settings.
• Cache plugin served the non-logged-in version of the page. See caching section.
• Cloudflare or CDN serving cached HTML. Bypass cache for logged-in users.

WooCommerce orders not appearing in chat context

• WooCommerce integration toggle is off. Settings → WooCommerce → enable.
• Plugin version is older than 1.4 (WooCommerce support added in 1.4). Update from Plugins page.
• Customer has placed orders as guest, not logged-in user. Guest orders aren't linked.

Widget conflicts with other chat plugins

• Position overlap — change MsgHub to bottom-left, leave the other one at bottom-right (or vice versa).
• Both widgets fighting for z-index — disable one. Running two live chat widgets at once usually hurts conversion anyway.

"Failed to load widget script" error in console

• app.msghub.info is blocked by an ad blocker or browser extension. Test in a clean profile.
• A security plugin (Wordfence, Sucuri) is blocking outbound to app.msghub.info. Whitelist the domain.

FAQ

What's next