On-site triggers

/

5 min read

On-site triggers: show a popup or form when a visitor acts

Build on-site triggers under Automations → On-site triggers: pick what the visitor does, set the conditions, then the actions, and see each rule's views, submits and revenue.

On-site triggers (Automations → On-site triggers) respond while a visitor is still on your store. Each one is a rule: a trigger (what the visitor does), conditions (who it applies to, how often and when), and one or more actions (show a popup, embed a form, and so on).

On-site triggers run inside the Zalify pixel on your site. If the pixel isn't installed on a page, nothing fires there; see Installing the Zalify pixel.

The list

The On-site triggers page lists every rule with:

  • When a visitor… and Then…: the trigger and its actions in one line, with the number of actions when there's more than one.
  • Frequency: how often the same visitor can see it.
  • Last 30 days: views, submits and the submit rate of the popups or forms it showed.
  • Revenue: orders placed with the same email within 7 days of a submit. When a shopper submitted more than one rule, the order counts for the most recent one.
  • Status: Live or Paused.

Every enabled popup also has a Default row: it shows when a visitor lands on the site, once per session. Choose Customize on that row to give it its own timing, pages and audience. Only one popup shows automatically per event; a default row that loses to another popup is marked Not shown until you customize it.

The same rules, together with your email flows and what each earned, appear on Automations → Overview.

Create or edit an on-site trigger

1

Open Automations → On-site triggers and choose New on-site trigger, or open an existing rule.

2

The rule opens on a canvas: Trigger, then Conditions, then the actions in order. Select a step to edit it in the panel beside the canvas (below it on a phone).

3

Give it a name, set each step as described below, and Save. Missing fields are marked on the canvas when you save.

The pixel loads the saved rules on the next page load, so reload your store page before testing a change.

Trigger: what the visitor does

TriggerFires whenSetting
Views a pageA page whose address matches loadsURL pattern, matched as Glob, Exact or Regex (/* is every page)
Scrolls the pageThe visitor scrolls past a depthScroll depth in %
Stays a whileThe visitor has been on the page for a timeDelay in seconds
Adds to cartA product is added to the cart—
Leaves the pageThe visitor moves to leave the page—
Sees an element appearAn element matching a CSS selector is added or shown, once per elementCSS selector

For a form on your own site, Sees an element appear with the form's success message as the selector counts only submissions that went through.

Conditions: who, how often and when

  • Audience: Live — all visitors, or Preview only — just for testing while you test (see below).
  • Frequency: Once per session, Once per page or Every time. Once per session is the right default for most popups.
  • Schedule (optional): a start and end date, for a promotion. Leave it empty to keep the rule on.

Actions: what happens

A rule needs at least one action and can have several; they run in order, and you can move them up or down.

  • Show a popup: pick a published popup. Turn on Run as A/B test and choose an experiment to split visitors between popups; each visitor keeps seeing the same version. Experiments are created and ended in Storefront → Experiments.
  • Embed a form: pick a form and the DOM selector of the element it should render inside.
  • Record a standard event or Record a custom event: send an event such as a product view, or one you name, to Zalify.
  • Report a conversion: send a lead to Zalify and your connected ad platforms, valued by the visitor's form answers.

The popup's content and design are edited in Forms (Creating a form or popup); the list a form adds people to is a form setting (Connecting a form to a list).

Test with Preview only

1

Set Audience to Preview only and save. Real visitors don't see the rule.

2

Choose Open preview on your store. If no preview domain is listed, add your store's domain under Preview domains, or add ?zalify-preview=true to any page where the pixel runs.

3

Do what the trigger waits for: open a matching page, scroll, wait out the delay, add to cart or move to leave.

4

When it works, set Audience back to Live — all visitors and save.

If nothing shows, check that the pixel runs on that page, that the popup is published, and that the frequency hasn't already been used up in this browser session.

Pause or delete

Pause stops a rule on your site and keeps it, with its numbers, for later; Turn on starts it again. Delete stops it right away and can't be undone.

Sending events to Meta, Google and other ad platforms isn't an on-site trigger; that's set up under Connections → Ad Pixels.