EngageEngageStart Setup

Start here

How do I install Engage on a website?

6 minute read

Reviewed September 3, 2026

Short answer

Short answer

Add the AJAI widget bootstrap to the site once, using the company ID AJAI gives you. The stable loader reads the workspace's published widget settings and starts the compatible runtime without requiring the page to duplicate all of that configuration.

Before you start

  • The company ID supplied for your Engage workspace
  • Permission to edit the website template, tag manager, or site-wide code area
  • A published widget profile with approved brand and conversation settings

Add the stable loader

Place the configuration before the loader and replace your_company_id with the ID AJAI supplied. Add it to the site-wide template so the widget is not installed more than once.

<script>
  window.AJAI_WIDGET_CONFIG = {
    company_id: "your_company_id"
  };
</script>
<script async src="https://widget.ajai.pro/ajai-widget.js"></script>
  1. 01Open the website's global code, template, or approved tag-manager area.
  2. 02Add the company ID configuration before the loader script.
  3. 03Publish the website change.
  4. 04Open a public page in a private browser window and confirm the launcher appears once.
  5. 05Open the widget and send a synthetic, non-customer test question that is covered by approved knowledge.

Keep presentation settings in Engage

The published profile controls the supported visual and presentation settings, including the launcher, theme, layout, and opening behavior. Keeping those choices in the workspace makes later changes safer than maintaining different copies across website pages.

A page may carry a small approved override, but identity, API destinations, and transport behavior are validated by the runtime and should not be improvised in page code.

Verify the real site, not only a preview

Check desktop and mobile widths, confirm that the widget does not cover required navigation or form controls, and verify that the site security policy permits the AJAI widget and API origins. Repeat the check after major theme, consent, or content-security-policy changes.

Availability and limits

What to keep in mind

  • Website builders expose global code in different places; AJAI cannot name the exact menu for every platform.
  • A restrictive content security policy, script optimizer, or consent manager can prevent the loader from starting.
  • Do not copy another business's company ID or expose private keys; the public widget uses a tenant identifier, not a secret credential.

Keep going

Related guides

View all guides

What does AJAI Engage do?

Understand how AJAI Engage answers website questions, captures intent, routes next steps, and keeps a human in control.

Read guide

How do approved answers and source controls work?

Keep Engage answers grounded in reviewed business sources, clear boundaries, and an inspectable knowledge index.

Read guide

How do I troubleshoot Engage or contact support?

Check common widget, answer, lead, takeover, and booking problems before contacting AJAI Support.

Read guide

Need a specific answer?

Review your Engage flow with AJAI.

Book a Review

Already using Engage? Contact support or review the Privacy Policy.