Skip to main content
Every configured widget can be opened on a hosted landing route at /c/:publicKey. The same route supports QR and ordinary link attribution through the source query parameter.
The owner-only QR generator builds the source=qr URL, renders a branded QR code, and can export a PNG. The landing page loads the regular widget bundle in fullscreen, auto-open mode.

​
Runtime behavior

1

Open the hosted route

The landing page normalizes source to either qr or link.
2

Record a scan

QR visits call /api/v1/widget/qr-scan with the public key for analytics.
3

Load the widget

The page injects the widget script with public key, fullscreen, auto-open, and source data attributes.
4

Attribute the conversation

Messages use the same widget configuration while retaining QR/link source context.

​
Deployment ideas

  • Product packaging and receipts
  • Store counters and venue signage
  • Equipment labels and service manuals
  • Email signatures and campaign links
A widget public key identifies public configuration; it is designed to appear in HTML and URLs. It must never authorize administrative operations. Protect all management routes with operator authentication and tenant checks.
Regenerate printed material only when the public key or hosted console origin changes. Test QR codes with multiple camera apps and confirm the destination uses HTTPS.
Last modified on July 17, 2026