Chatra Chat Integration

Yes. A mobile visibility switch lets you suppress the widget on mobile screens while keeping it on desktop. When it is turned off, the module skips the Chatra script entirely on mobile, so no chat button is added on phones and no extra script is loaded there.

Yes. Create an account at chatra.io, then open Settings > General > Widget code and copy the Widget ID from the installation snippet. Paste that ID into the module's Widget ID field. Until a Widget ID is saved the module stays inactive and the back office shows a reminder, so the widget never loads without a valid ID.

Yes, the module can limit Chatra by PrestaShop page type. Its configuration supports all pages, product pages, category pages and checkout-related controllers such as cart, order and checkout, so the widget is not necessarily rendered on every storefront page.

In the module configuration this is the PAGES setting. The built-in choices are all, product, category and checkout; checkout covers the cart/order controller family used by different PrestaShop versions, including cart, order, order-opc, orderopc and checkout. The widget is rendered from displayBeforeBodyClosingTag only when the module is enabled, the required Widget ID is present, the mobile setting allows the current device, and the page check passes.

There is one practical limit: this is page-type targeting, not a per-URL rule builder. When PAGES is set to product, category or checkout, other controller names do not fall through as allowed; they fail the selected page-type check. The permissive fallback is for an empty/all setting or an unexpected PAGES configuration value. If you need a single landing page or a very specific controller included or excluded, that would need a code-level rule or a more advanced targeting layer in Chatra itself.

Yes, but in this module's rendered Chatra snippet only the logged-in customer's email is passed to Chatra. The shared chat helper can collect both email and name when PASS_USER_DATA is enabled and the customer is logged in, but the Chatra template only writes the email as window.ChatraSetup.clientId.

To disable that data passing, turn off the Pass Customer Data switch in the Chatra module settings. Then the helper returns blank customer values and the template does not emit clientId. No customer name, order data, address data or group data is printed by this Chatra template.

Chat triggers, chat routing, operator assignment and widget design remain configured inside Chatra itself. The PrestaShop module is mainly responsible for loading https://call.chatra.io/chatra.js with the Widget ID and optional delay.

The default install value for PASS_USER_DATA is enabled, but the data is still conditional: the customer object must exist, the visitor must be logged in, and the storefront hook must be allowed to render. Guest visitors receive no customer identifier from this module. The delay setting is also handled locally: when DELAY is greater than zero, the template wraps the Chatra loader in setTimeout; when it is zero, the loader runs immediately.

For privacy reviews, the important distinction is that the helper can return a full name, but this specific Chatra template does not output it. The only customer-derived value emitted by the template is the email-based clientId, and only when PASS_USER_DATA remains enabled.

Yes, the Chatra script can be delayed by a configured number of seconds. In PrestaShop the template wraps the widget loader in setTimeout when the delay value is greater than zero, then loads the same Chatra script after that delay.

The saved setting is DELAY, exposed through the shared chat form as Fallback Delay (seconds). The module passes it to the Smarty template as an integer. When DELAY>0, the template wraps both window.ChatraID/window.ChatraSetup assignment and the script append block in setTimeout(..., DELAY * 1000).

When DELAY=0, the template does not wrap the loader in setTimeout, so Chatra is initialized immediately when the hook output is parsed. The current template does not implement scroll, click, touch or first-interaction loading; it is a simple seconds-based timer.

DELAY=0  -> load immediately
DELAY=3  -> wait 3 seconds, then load Chatra
DELAY=10 -> wait 10 seconds, then load Chatra

The delay setting only affects timing after the module has decided to render. The normal guard still applies first: the module must be enabled, WIDGET_ID must be saved, the mobile setting must allow the visitor's device, and the page targeting rule must match.

Add your Chatra Widget ID and enable the module. The PrestaShop hook renders the Chatra script before the closing body tag, assigns the ID to window.ChatraID, and loads https://call.chatra.io/chatra.js asynchronously on the storefront. This keeps the setup tied to module settings and PrestaShop runtime behavior.

On install, the Chatra module sets ENABLED=1, an empty WIDGET_ID, SHOW_MOBILE=1, PAGES=all, DELAY=0 and PASS_USER_DATA=1. The module can therefore be installed and enabled, but it still will not output the widget until a non-empty Widget ID is saved.

The configuration page labels the field Widget ID and the source help says to paste it from Chatra under Settings > General > Widget code. The required-config validator only checks that the value is not empty; it does not enforce a UUID-style format like the Crisp module does.

Before rendering, the shared chat guard checks that the module is enabled, the required WIDGET_ID is present, mobile display is allowed when the visitor is on mobile, and the selected page targeting rule matches the current controller. When those checks pass, the template sets window.ChatraID, creates window.ChatraSetup, and appends the Chatra loader script asynchronously.

Minimum setup:
Enable Chatra Chat = Yes
Widget ID = value copied from Chatra widget code
Show on Pages = all, product, category or checkout

If PASS_USER_DATA is enabled and the shopper is logged in, the template also places the customer's email into ChatraSetup.clientId. It does not send the customer's name, address, cart contents or order history in this template.