Frequently Asked Questions

EngageBox doesn't store any data in the database. EngageBox is the middle man between your visitor and the e-mail list service you're using such as Acymailing, MailChimp, GetResponse etc. This means that your contacts will be stored in these services and EngageBox is only displaying their forms through its popups. In case though you're looking for a Form Builder that can be integrated with EngageBox and can store contacts in your database have a look at Convert Forms

Yes, but it works in a different way. Given mobile devices are touch based, mobile exit is not based on mouse movement. Instead there are distinct actions and signals EngageBox uses to anticipate when the visitor is about to leave. To learn more visit Does Exit Trigger work on mobile devices?

EngageBox produces popups in a way which can't be blocked by the browser’s pop-up blocking feature or 3rd party extensions such as AdBlock or uBlock.

Yes, it sets cookies in the following two cases.

Visitor ID Cookie
A cookie with the name nrid is used to identify uniquely each visitor.

• The value of the cookie has a unique ID for each visitor
• Does not exchange information with other cookies
• Does not transmit any data to a third party app

This cookie is only created if any of the following requirements are met:

• The Statistics option is enabled
• The Limit Impressions option is enabled
• The Viewed Another Box Assignment is enabled

Close Event Cookie
A cookie in the form engagebox_ID is set every time a box is closed. Typically is used by the extension to decide if a box should stay hidden. This affects boxes that have the "After Close Stay Hidden" option enabled.

Visitor Persistent & Session Cookies
Two cookies named tvp and tvs are used by EngageBox when the Condition New/Returning Visitor is used in order to identify whether the user is new or returning.

No personal information such as IP address, User Agent string or the Joomla! User ID is stored in any cookie case.

To be able to install EngageBox on an older Joomla version such as v3.3, v3.2 or even v2.5, you'll need to use an older release of EngageBox as well. The last compatible release is v2.2.1 (back then the extension's name was Responsive Scroll Triggered Box) and can be downloaded from the Releases Section where you can access any release.

Notes:

• You will need an active subscription to be able to access any release.
• No support is provided for Joomla versions < 3.8.

The "Hidden by cookie" indication is just a notice to inform you that the box is no longer visible to you because you've (accidentally) clicked on the box's close button and a cookie is stored on your browser (as you have set). This cookie is preventing the appearance of the box only to you. To clear your browser's cookies read this tutorial.

On August 2016 Google announced that they will be able to track which pages use interstitials that block content by displaying ads or other obtrusive and irrelevant content. Read more on our blog post.

No. EngageBox is meant to be used in the front-end only. At the moment, the administrator area is not supported.

The rstbox_logs table is used by EngageBox to track the box "open" events for each user. The Limit Impressions option relies on this table to determine whether and when a user has opened a specific box.

The size of this table depends on the traffic the website gets and the total boxes published on the page. You can safely truncate (empty) that table whenever you wish.

Another thing you may consider is lowering the maximum days that EngageBox uses to truncate/empty the log table. You can find this setting on Global Configuration > EngageBox > Advanced.

EngageBox will focus on the first focusable element in your popup right after it appears. This may display the focusable element (link, button, etc...) with a blue border. To stop this from happening, add the following HTML Element at the start of your popup:

<button style="display:none;">hidden</button>