FAQ

Does Humind slow down my site?

No meaningful impact. The scripts load with defer, so they never block page rendering or Time to Interactive. They're served from a CDN (embed.thehumind.com, widgets.thehumind.com), code-split into chunks, and only the entry chunk runs on mount. The rest is fetched on demand when the shopper interacts.

The widgets don't touch your critical rendering path and don't add blocking requests. If you measure Core Web Vitals before and after install, LCP and CLS should not regress.

What happens if the Humind script fails to load?

Nothing breaks. The <script> tag is defer-loaded, so a network error never blocks page rendering. The custom elements stay inert: no layout shift, no console error visible to shoppers, no exception thrown.

What happens during a Humind outage?

The chat overlay shows a fallback "unavailable" message and retries in the background. In-page widgets that depend on the API hide themselves silently (see Troubleshooting → Widget loads but shows "Loading…" indefinitely). Your host site continues to function as if Humind weren't there. Subscribe to the status page.

Is it an iframe?

No. Every widget (<humind-widget>, <humind-quiz>, <humind-gift-finder>, <humind-product-questions>) is a native HTML custom element, specifically a Web Component. No iframe overhead, no cross-frame postMessage, no separate document.

The chat overlay and two of the widgets (<humind-gift-finder>, <humind-product-questions>) use Shadow DOM internally for style isolation, so host-site CSS can't leak in or out. <humind-quiz> is the exception: it renders in the light DOM, so your CSS applies to it (see Troubleshooting → Styles bleeding).

Can I put multiple widgets on the same page?

Yes. Each custom element is independent: you can embed <humind-widget>, <humind-gift-finder>, and <humind-product-questions> on the same page, and they coordinate through the humind-open-chat event (widgets dispatch, chat listens).

Don't duplicate <humind-widget> itself. The loader registers it once and warns in the console on a second registration.

Does it work with SSR (Next.js, Nuxt, Astro)?

Yes. The custom elements render as empty tags on the server and hydrate on the client after the loader script runs. Nothing framework-specific is required beyond declaring humind-* as custom elements (see the install guide).

Does it work with SPA client-side routing?

Yes. If your router replaces page components on navigation (React Router, Next App Router, Vue Router, Angular Router), the widget re-mounts cleanly.

For the chat, we recommend keeping a single <humind-widget> mounted at the app root so conversation state survives client-side navigation. If you go that route, update the template-name attribute on navigation so the chat knows where the shopper is. cookie-consent reacts to attribute changes in real time too.

If you let the router mount and unmount <humind-widget> per route, the widget still works, but the current conversation resets on each navigation.

Is the content indexed for SEO?

Yes, especially for AI search, which is where it matters most in ecommerce today. The picture splits in two:

AI search (ChatGPT, Perplexity, Gemini, Google AI Overviews)

AI crawlers render pages and see the Humind widgets on your site, including the product questions and the knowledge base behind the chat (FAQs, policies, brand guidelines, anything you upload in the dashboard). Your catalog content becomes visible to AI summarizers in the exact form shoppers ask about it, which is the angle that compounds over time as AI search share grows.

The chat logs also double as keyword research: the real questions visitors ask about your catalog are the same questions AI engines will see other shoppers ask. You can feed them back into your own content strategy.

Classic SEO (Google, Bing)

Widget output is rendered client-side, so it's not a substitute for server-rendered product copy, structured data, or FAQ schema. Keep authoring those yourself.

What Humind contributes is indirect: the widgets answer shopper questions in place instead of sending visitors back to search, which tends to improve dwell time, pages per session, and bounce rate. These are all engagement signals search engines consider.

Is Humind GDPR-compliant?

Yes. Humind acts as a data processor under a DPA signed with each merchant. Ask your integration lead or support@thehumind.com for the current DPA and sub-processor list.

Where is the data hosted?

Default hosting is Azure multi-region (EU + US), with routing based on visitor proximity. EU-only hosting is available on request — contact support to set it up before go-live.

Are conversations used to train AI?

No. Merchant conversations, catalog data, and knowledge base content are never used to train foundation models. Conversations are processed through LLM providers under contracts that prohibit use of your data for training.

How do I handle cookie consent?

Pass the shopper's consent status via the cookie-consent attribute on <humind-widget>. The attribute is reactive: update it in place and the widget adjusts (analytics, session persistence, etc.) without a remount.

This integrates cleanly with consent platforms (OneTrust, Didomi, Cookiebot, Axeptio): subscribe to their consent event and mirror the result onto the attribute.

What personal data does Humind collect?

None by default. Widget traffic is tagged with anonymous IDs (x-session-id per browser session, x-visitor-id stable across sessions) that carry no PII. Chat content may contain personal info if a shopper types it, so handle that under your own privacy policy.

Can the widget run arbitrary JavaScript in my site?

No. The widget code is scoped to the custom elements served from embed.thehumind.com and widgets.thehumind.com. It does not eval, load remote scripts dynamically, or execute user-submitted content. Shadow DOM (where enabled) isolates DOM access from the host page. For a formal security review, ask support for bundle hashes and a CSP report.

I'm on Shopify but my storefront is headless (Hydrogen, Next.js, Remix). How do I install Humind?

You're on the hybrid path: Shopify backend + custom storefront. Install the Shopify app as usual so product webhooks and OAuth work. Then embed the widgets manually in your storefront code, like a non-Shopify merchant would:

<humind-widget
  shop-domain="your-shop.myshopify.com"
  template-name="product"
  integration="shopify"
  product-id="gid://shopify/Product/12345"
></humind-widget>

The key is integration="shopify" and passing Shopify GIDs (gid://shopify/Product/..., gid://shopify/Collection/...) from your storefront code instead of Liquid. See Shopify catalog sync → hybrid storefront for the full setup.

Does it work with Google Tag Manager?

Yes. Load the loader <script> via a Custom HTML tag on "All Pages". Don't inject <humind-widget> itself via GTM: it belongs in your page templates so routing and context attributes (template-name, product-id) stay in sync with navigation.

Can I forward widget events to GA4, Segment, or Mixpanel?

Yes. Listen to the custom events on window and forward them to your analytics SDK:

window.addEventListener('humind-open-chat', (e) => {
  analytics.track('Chat Opened', e.detail)
})

Events dispatched on window:

• humind-open-chat — chat overlay opened (any trigger).
• humind-continue-thread — shopper resumed a prior conversation.
• humind-quiz-completed — <humind-quiz> reached its final step.

Event dispatched on document (Shopify integration only):

• cart:updated — fires after the widget adds an item to the Shopify cart. Listen with document.addEventListener('cart:updated', ...), not window. The detail carries the updated cart and optional rendered sections, following Shopify's own cart:updated convention so any theme that listens to it will rerender.

For chat lifecycle events (message sent, handoff, session ended), the dashboard analytics page is the source today. Webhooks are on the roadmap.

Where do I see conversation analytics?

In the dashboard under Analytics. Volume, topics, deflection, revenue attribution, and top shopper queries all live there. CSV export is available; contact support for programmatic access.

Can I customize the AI's behavior?

Yes, from the dashboard. You configure brand voice, tone, forbidden topics, and upload a knowledge base (FAQs, policies, sizing guides, anything you want the AI to ground its answers on). The AI does not invent products or facts: answers are grounded on your catalog and knowledge base.