Start with the Ask bar, then add the pop-up if you want a global helper.
Offsets are desktop-only. Mobile is centered by design.
Paste this near the end of your site’s <body>.
We pre-fill the creator_id and hea_id.
If an install_id exists, we’ll use it by default (recommended for domain whitelisting & transfers).
2. Install ID (recommended)
Create a stable install_id for your website integration. It enables domain allowlisting and safer HEA transfers.
Why use install_id?
• You can allowlist domains (allowed_domains) so only authorized sites can run the widget.
• Transfers are safer: your customer’s embed stays stable even if ownership changes.
• You can have multiple installs per HEA (e.g., staging + production domains).
Select a HEA to load installs.
install_id:(none)
If empty → all domains are allowed (not recommended for public production). Subdomains are allowed when you add the apex (e.g. domain.com allows www.domain.com).
Tip: Prefer Disable instead of deleting. ⚠️ Deleting an install_id can break a customer deployment with no rollback.
This list is read from KV via /api/hea/installs?action=list_installs&expand=1.
install_id
status
domains
updated
Select a HEA to load installs.
3. Consent / Cookies (CMP)
Optional but recommended. Add this above the HEA widget snippet so consent is available early.
Cookiebot is ready. Generic is a template for other CMPs.
Paste this near the top of <body> (before HEA).
4. Explore integration patterns & test pages
Visual overview and live test pages for the main integration styles:
magic ask bar, conversation block, and floating pop-up.
SVG overview for web and mobile. Use it in client decks to explain where HEA appears.
Live demo pages for ask bar, floating pop-up, and block embed.
We’ll propagate your creator_id and
hea_id via query params (and keep install_id for embed).