Setup & Integration

Select your HEA, create a stable install_id, compare widget options, grab the embed snippet, and share whitelisting instructions when needed.
🧩 Install on your site
0. Select your HEA
We’ll customize the setup flow and links with the correct creator_id and hea_id. If an install_id exists, we’ll use it by default (recommended).
Pick a HEA to load its install, widget, and integration options.
creator_id: (pending)
hea_id: (none selected)
install_id: (none)
1. 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.
2. Select the HEA widget(s) you want to install
Open a live widget showcase for the selected HEA to compare the 4 main integration options: magic ask bar, conversation starter, floating pop-up, and side panel.

This opens hea_embed_showcase.html in a new tab with the current creator_id and hea_id, so you can preview all 4 widget styles on the same HEA before copying the final snippet.

Select a HEA first to open the widget showcase.
Start with the Ask bar, then add the pop-up if you want a global helper. 

            

              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).
            

          


          

            
            

              SVG overview for web and mobile. Use it in client decks to explain where HEA appears.
            

            
              🧩
              Open integration patterns
            
          


          

            
            

              Live demo pages for ask bar, floating pop-up, block embed, and side panel.
              We’ll propagate your creator_id and
              hea_id via query params (and keep install_id for embed).
            

            

              
                🔎
                Ask bar test
              
              
                💬
                Floating pop-up test
              
              
                📦
                Conversation block test
              
              
                📌
                Side panel test
              
            

          

        

      


      
      

        

          

            
3. Consent / Cookies (CMP)

            

              Optional but recommended. Add this above the HEA widget snippet so consent is available early.
            

          

        


        

          

            
            

            

              
              
              

                Native connectors: Cookiebot, Axept/Axeptio. Other common CMPs are prefilled via the generic template.
              

            

          


          

            
            

            

              Paste this near the top of <body> (before HEA).
              
            

            

          

        

      


      
      

        

          

            
4. Whitelisting (if your WAF blocks the crawler)

            

              Only needed when your site uses an aggressive Web Application Firewall or bot protection.
            

          

        


        

          Most sites work out of the box. If your job log mentions 403 / bot detection / WAF,
          send this guide to your webmaster or hosting provider.
        


        
          🛡️
          Open whitelisting guide
        

        

          The guide includes a ready-to-forward email with
          sales@hea-world.com in copy and the
          HEA-Crawler/1.0 user-agent to allow.