Tawk.to Chat Integration: setup and help

On older PrestaShop versions, use the equivalent module installation page. Open this module through Configure whenever you need to return to its settings.

Read the two IDs from https://embed.tawk.to/PROPERTY_ID/WIDGET_ID. For example, the first part can be 5a1b2c3d9e4f6a7b8c9d and the second 1abc2def3. Paste only the IDs. The setup panel points to Administration > Chat Widget in Tawk.to.

Enter both fallback IDs or leave both empty. A rule can supply the widget without fallback IDs. If no rule matches and the fallback is empty or invalid, no chat is shown. Checkout covers cart, order, order-opc, orderopc, and checkout.

Click Manage widget rules in the Widget rules panel. Create a rule on the Widget Rule screen. Each rule selects a Tawk.to property and widget for a visitor context.

Every condition within a rule must match. The first matching active rule wins. If no rule matches, the configuration fallback and Fallback Widget Pages apply. The mobile, enable, customer data, traffic, and consent controls still apply to a rule-selected widget.

For example, create a higher-priority rule for one language and Logged-in Customers Only. Use the fallback for all remaining visitors. Verify the rule with a matching customer and with a guest who should receive the fallback.

The Internal traffic section can suppress chat for employees and listed IP addresses. Select one shop before editing. Shared shop settings require a shop administrator. Module overrides require permission to configure this module.

Use Save shared settings for shop-wide changes and Save module overrides for this module. Shared changes affect other participating modules. Overrides do not grant cookie consent. If the page reports that settings are read-only because no safe save lock is available, ask your administrator to resolve that server limitation. An optional Cloudflare synchronization control appears only when its package and permissions are available.

The front script loads from displayHeader. The module renders the footer control through displayFooterAfter on PrestaShop 1.7 and later, or displayFooter on 1.6. This version does not use a displayBeforeBodyClosingTag.tpl embed template.

Chat waits for an allowed internal-traffic decision. With MPR Cookies Revolution enabled, it also waits for functional consent. Chat stays blocked while the consent service is unavailable. The passive timer is not an extra delay after interaction. It can load chat without any interaction once traffic and consent allow it. The interaction events are scroll, click, touchstart, keydown, and mousemove.

The module adds the Tawk.to script from your selected IDs. On PrestaShop 1.7 and later, customer identification reads the logged-in customer object in the browser. On 1.6, the module supplies the customer data from PHP. Your team manages agents, widget appearance, routing, wording, offline forms, and conversations in Tawk.to.

Use Hide chat to hide the widget. Hiding from the widget asks for confirmation. Your choice is retained in this browser tab’s session storage. Use Open chat at the bottom of the page to reopen it. Consent withdrawal or a definitive internal-traffic exclusion stops an active chat. The module also hides chat while supported storefront overlays are open.

1. Start in a clean visitor browser. Employee exclusion can suppress chat in your usual back-office browser.
2. Confirm that a rule matches or that the fallback has both valid IDs.
3. If you use consent management, grant functional consent, then trigger interaction or wait for the fallback.
4. Confirm the correct property receives a test message. Test the logged-in identity setting separately.
5. Hide and reopen chat. Test your mobile setting and each rule’s language, group, page, and login conditions.

If there is no footer control, check the footer hook for your PrestaShop version and your theme. Reopen Configure to let the module reconcile its hook registrations. If no script loads, check consent, the internal-traffic decision, the mobile setting, and a prior hidden choice. If the external script fails, check browser network errors and blocking rules.

The Integrity page checks installation and configuration. Diagnostic controls are also available on the configuration page. When diagnostics are active, the browser console can inspect mprtawkChat.debugReport(). License, Support, and Update remain maintenance pages.

Turn off Enable Tawk.to Chat and save to retain settings and rules. Uninstall in the module manager to remove this module’s settings, widget-rule schema, menu entries, and its internal-traffic overrides. The shared internal-traffic policy remains. Your Tawk.to account and conversations remain with Tawk.to.