Popups and forms on your own site

The widget shows campaigns from the admin panel on top of your site: offers, forms and quizzes, coupons, timers. There is no need to move the site to our platform. Configuring campaigns is described in the article Engagement campaigns, and installing the shared tag — in My site.

Connecting#

In "My site" select the location and the "Popups and forms" card. This is a paid extension. Configure a campaign and enable it; an installed tag alone, without an active campaign, is not enough.

The "Create from template" button opens the gallery in the settings window. Check the text, the action, the pages and the display conditions before saving. A preview marked "Test display" does not send requests and does not add to the live statistics.

Conditions and actions#

A campaign can react to a page load, time spent on the site, inactivity, scrolling, the number of pages viewed, a click and a change in the cart. The exit offer is designed for a desktop browser. The audience can be restricted by pages, devices, schedule and other campaign conditions.

The form validates the required fields and the selected consent, shows an error on a failed submission and allows a retry. The coupon is validated before it is shown. The "Apply" link carries the code over to the storefront; when moving to another domain via an ordinary link, the coupon memory is not carried over automatically.

An in-page campaign needs a suitable container on your site. If the container is not found, the campaign is not shown. Installing the shared tag does not create such a container by itself.

What needs to be connected separately#

The widget does not read the cart of an external store by itself. The site developer must pass its state through CenalyEngage.cart(...) or the cenaly:cart event. Without this link, the conditions based on the total and on cart changes receive no data. Amounts are passed in the minor units of the currency.

The "Open chat" and "Open order" actions require the corresponding widget to be connected. The capabilities of an external site and of our storefront are not entirely identical: in-page placement and the popup of the nearest available slots are supported by the external embed, but not by every surface of the storefront.

The display frequency limits and the visitor's memory use browser storage. Clearing it, blocking it or moving to another domain changes that memory; this is not a single guest profile shared across sites.

If nothing is shown#

Check the tag's location, whether the campaign is enabled, its schedule, the page address and the frequency limits. For cart campaigns check that the state is being passed; for in-page placement — that the container exists. A closed third-party dialogue, the audience conditions or an already used display limit can also get in the way.

For a developer, window.CenalyEngage.getDiagnostics() is available: the load status, the link to the cart and the reasons why a particular campaign does not fit. The CSP requirements and the installation check are described in the general guide.