Embed snippet and page performance
Where to place the script
Follow the install guidance: typically just before </body>, loaded once on pages where the widget should appear. Avoid injecting duplicate snippets via tag managers on every virtual route change unless you know your SPA only mounts the root once.
If you use a tag manager, fire the tag on the same pages your marketing team expects the widget—excluding checkout, app shells behind login, or preview domains if those should stay quiet.
Layout shift and the launcher
Reserve space or accept a fixed launcher corner so the widget does not shove content when it hydrates. Collisions with cookie banners and mobile safe areas are the usual culprits—test on real devices, not only desktop.
Performance mindset
Treat the widget like analytics: if your page is already heavy, fixing images and main-thread JavaScript matters more than obsessing over the chat bundle. Still, keep the embed lean—one script, no double loads—and measure before/after in Lighthouse on a key URL.
Staging vs production
Validate the snippet on a staging host that mirrors production CSP and consent tooling. Blocked scripts there predict silent failures in prod.