6. Embedding Touchpoints

Touchpoints publish Klariton answers on your site. The first self-serve touchpoint type is FAQ. Wizard Legacy exists for migrated advisors. Chat Advisor and Infobox are prepared but not generally self-serve.

Supported Touchpoint Types

Type	Status	Use
FAQ	LIVE	Published BIQs as a question-answer block
Wizard Legacy	LIVE	Migrated classic advisors
Chat Advisor	COMING SOON / guided	Conversational advisor
Infobox	COMING SOON	Compact contextual message

Current Embed Contract

Always copy the snippet from the Studio. The current contract uses:

<script type="module" src="https://worker.klariton.com/v1/klariton-widget.universal.js"></script>

<klariton-widget
  mode="biq-bundle"
  org-slug="your-org-slug"
  touchpoint-slug="your-touchpoint-slug"
  locale="en"
  data-worker-url="https://worker.klariton.com">
</klariton-widget>

Do not use old examples with tenant-id and touchpoint-id for new embeds.

Shopify Example

Add the bundle once in theme.liquid:

<script type="module" src="https://worker.klariton.com/v1/klariton-widget.universal.js"></script>

Place the widget in a Custom Liquid section:

<klariton-widget
  mode="biq-bundle"
  org-slug="your-org-slug"
  touchpoint-slug="your-touchpoint-slug"
  product-id="{{ product.id }}"
  product-handle="{{ product.handle }}"
  locale="{{ request.locale.iso_code | default: 'en' }}"
  data-worker-url="https://worker.klariton.com">
</klariton-widget>

Use Custom Liquid or source HTML. Rich-text editors often strip unknown custom elements.

Required Checks

• Domain/origin must be allowed in Settings.
• Touchpoint must be live.
• At least one live-eligible BIQ must be published.
• Bundle request returns 200.
• Touchpoint data request returns 200.
• Shopify product context is present for product-specific widgets.

Custom Domains

Klariton can serve through worker.klariton.com or through a customer worker subdomain, for example chat.example.com. A first-party worker domain can improve cookie/session behavior and branding.

Configure domains in Settings.

API-First Embeds

If you build your own UI, use the API-key read API or the public touchpoint read endpoint documented in Developers. Keep API keys server-side.