Alive5

Alive5 embeds the Alive5 live chat widget on your Drupal site from the admin interface — with no theme, template, or code changes. Cache-safe display rules control exactly which pages, roles, and content types show the chat.

Features

• Point-and-click setup. Enable the widget and paste your Alive5 Widget ID on a single settings page — the chat appears the moment you save. No editing html.html.twig, page.html.twig, or any template.
• Precise display rules. Show the widget on the entire site, on selected pages only, or everywhere except selected pages, using Drupal path patterns (wildcards and the <front> token supported).
• One-click exclusions. Hide the widget on administration pages, user account pages (/user*), and cart/checkout pages.
• Audience targeting. Show it to everyone, anonymous visitors only, or logged-in users only; restrict by user role; and/or restrict to specific content types.
• Cache-correct by design. Every rule reports the right Drupal cache metadata, so the module works cleanly with Internal Page Cache, Dynamic Page Cache, BigPipe, and CSS/JS aggregation — with no cache poisoning.
• Faithful, safe injection. The vendor script loads asynchronously and exactly once (duplicate-load guard included), preserving the official Alive5 embed attributes.
• Exportable configuration. All settings live in Drupal configuration and round-trip through drush config:export / config:import.

AI disclosure

AI-Generated: Yes. AI tools were used while writing parts of this module (scaffolding and drafts). I directed the work, reviewed the code, and am responsible for what is in the repository.

Post-Installation

After enabling the module, go to Configuration → System → Alive5 (/admin/config/system/alive5) and:

1. Enter the Widget ID from your Alive5 account and keep Enable the Alive5 widget checked.
2. Choose where and to whom the widget appears using the Display rules and Audience sections.
3. Save. The widget is now live.

There is nothing else to configure — no content types, text formats, or blocks to place. Access to the settings page is controlled by the Administer Alive5 permission.

Additional Requirements

Drupal core 10 or 11. No other contributed modules or external libraries are required. You do need an Alive5 account to obtain a Widget ID; the chat runtime itself is served by Alive5.

Recommended modules/libraries

None are required. If your site sits behind a reverse proxy or CDN (Varnish, Cloudflare), pair this module with Purge so configuration changes invalidate the edge cache via cache tags. The module coexists with Google Tag Manager (Google Tag) without conflict.

Similar projects

These modules also put a vendor chat widget on the page. Alive5 is the Alive5 product, not a generic chat engine.

• tawk_to (covered). tawk.to widget, Drupal 10/11, extra visibility settings. Different vendor. Alive5 does not log the admin into the vendor dashboard from Drupal; the widget ID is pasted from the Alive5 account.
• tawkto. Another tawk.to integration, Drupal 8/9/10, not covered.
• drift (covered). Drift widget. Different vendor.
• crispchat. Crisp widget. Passes the Drupal username and email of a logged-in visitor to Crisp. Alive5's loader does not send Drupal user identity; it only sets the widget ID on the script tag.
• live_chat_for_drupal. LiveChat.com widget. Different vendor.
• signalzen. SignalZen widget via an external library URL.

The Drupal-specific difference is the cache-safe rule engine. Several chat widgets attach a script and stop there. This one treats "hidden on this page" as a cache-metadata problem, not a hook_page_attachments() early return with no contexts.

Supporting this Module

Issues and merge requests are welcome in the project issue queue. For questions about the Alive5 platform itself, contact Alive5 support.

Community Documentation

See the module’s README.md for installation, configuration, troubleshooting, and uninstall instructions. Alive5 platform documentation is available at alive5.com.