Chatra Chat Integration: setup and help

You need an existing service account and its Widget ID. Configure conversations and the visible widget in the service account.

The module's Configure action opens Chatra Configuration. Its configuration controller also shows a required-configuration notice and an integrity banner. Use the module's Configuration, Integrity, License, Support and Update pages for the corresponding maintenance work.

Find the connection value

Copy ChatraID from your Chatra widget installation code. The setup panel points to Settings > General > Widget code. Paste the identifier only. Do not paste an entire URL or script.

The default is empty. For new or changed identifiers, the module expects 8 to 128 letters, numbers, hyphens or underscores. A rejected identifier keeps the previous saved configuration. Correct the value and save again.

Set these fields in Chatra Configuration, then click Save.

Page groups

Targeting uses controller names. A custom checkout controller outside this list is not included by Checkout Pages Only. There is no custom URL-rule field. Show on Mobile uses PrestaShop mobile detection rather than browser width alone.

Customer fields

When Pass Customer Data is enabled, the module sends the full name and email address of logged-in customers to Chatra through ChatraIntegration. Set it to No to omit both fields.

Guests do not receive PrestaShop customer identity fields from this module. The service can still collect information through its own widget. This module does not synchronize order history or cart contents.

Example configuration

For checkout pages on desktop, choose Checkout Pages Only, set Show on Mobile to No, and set Fallback Delay (seconds) to 2. The loader starts on the first interaction or after two seconds without interaction.

The module registers displayBeforeBodyClosingTag. It first checks the enable switch, connection value, device rule and page rule. It then places a deferred loader near the end of the page.

Scroll, click, touch or press a key to trigger the loader. Without interaction, wait for the configured fallback. The shared loader removes the inner template delay, so the two waits are not added together. With the installation default 0, allow 10 seconds before treating an idle page as a loading failure.

In browser developer tools, check for a request matching:

https://call.chatra.io/chatra.js

Open the widget and send a test message. Check that it reaches the service inbox. Test a logged-in account if you enabled Pass Customer Data, and verify which identity fields the service receives. Finally, test the excluded pages and mobile devices.

Manage agents, conversations, triggers and widget appearance in Chatra.

• If no loader is output, check Enable Chatra Chat, Widget ID, Show on Pages and Show on Mobile.
• If the page is idle, wait for the fallback or interact with it. Fallback Delay (seconds) set to 0 does not mean immediate loading.
• If saving fails, keep the identifier filled in, check its format, reload the configuration page and retry. Do not use placeholder credentials for a live test.
• If the external request fails, check browser console errors, script blocking, Content Security Policy and any consent tooling on your shop.
• If the script loads but the launcher is absent, check your service-side widget publication, account availability and display rules.
• If a customer field is missing, log in and confirm Pass Customer Data is Yes. Compare with the exact fields listed above.
• If another integration also inserts the service script, check the rendered page for duplicate or conflicting installation code.

Check a custom theme

Your theme must execute the closing-body hook. A developer can restore this call before </body> where the theme lacks it:

{hook h='displayBeforeBodyClosingTag'}

For a theme template adjustment, copy:

modules/mprchatra/views/templates/hook/displayBeforeBodyClosingTag.tpl

to:

themes/your-theme/modules/mprchatra/views/templates/hook/displayBeforeBodyClosingTag.tpl

Keep the module's Smarty variables and identifier escaping. The shared interaction wrapper still applies to this hook template.

The form uses the MPRCHATRA_ prefix for submitted field names. Current storage uses module mprchatra in the shared mpr_config table, with short keys:

ENABLED
WIDGET_ID
SHOW_MOBILE
PAGES
DELAY
PASS_USER_DATA

The database table uses your shop's table prefix, so ps_mpr_config is only an example name. Use the configuration form for normal changes. Do not treat form-field names as the current database keys.

Set Enable Chatra Chat to No and save with the identifier still present to pause this module's output. You can also disable the module in Module Manager.

To remove it, use Uninstall in Module Manager and confirm. The uninstall removes its module configuration and admin menu entries. It does not close the external service account or remove code inserted by another module or theme.