You do not need an SDK, npm package, or build step to put Lavenity on a site. One script tag is enough.
What you need before installation
Sign up, create a workspace, and add the domain where the chat should appear. The dashboard gives you a site ID — keep it handy for the snippet.
Paste the script before the closing body tag on any stack: WordPress, Shopify, a static site, or your own framework. The script loads asynchronously and weighs about 4 KB, so it should not block rendering.
Where to add the script and site ID
Open the site in a private window and send a test message. You should see it in the team inbox within a second, with presence and typing indicators if another agent is online.
If the bubble does not show, check that the domain matches your allowlist exactly (including www) and that no content blocker is stripping third-party scripts in your test profile.
How to test the widget after launch
When you are ready for the team, invite colleagues from the dashboard. Owners manage sites and billing; agents focus on conversations.
Common reasons the launcher does not appear
The most common issue is an exact domain mismatch: example.com and www.example.com need separate authorization, and a staging host is not the production domain. Also check the site ID, script address, Content Security Policy, and any consent manager that may delay third-party tags.
Test in a private window without the active operator session. Open the launcher, send a message, confirm it appears in the inbox, reply, and reload the page. History should return, and the domain should remain authorized without manual intervention.
Frequently asked question
Does installation require an npm package or a site rebuild?
No. A standard installation only needs the asynchronous script tag and site ID before the closing body tag. It can be added without an SDK to static HTML, WordPress, Shopify, Google Tag Manager, or a custom frontend.