⏱ Triggers: When A Campaign Appears

When a campaign appears matters as much as what it says. Choose the trigger on the Triggers tab.

The nine triggers:

  • Immediately: fires as soon as the page is ready. Right for bars and announcements that should always be visible.
  • After a time delay: fires after a number of seconds you set. Gives the visitor a moment to settle before you ask.
  • After scrolling down the page: fires at a scroll depth percentage. Around 50 percent is the strongest trigger for blog posts, because it waits until somebody is genuinely reading.
  • On exit intent: fires when the cursor leaves the top of the window. The safest popup trigger, because it only runs as the visit is ending.
  • When a link or button is clicked: you supply a CSS selector and the campaign opens when a matching element is clicked. The listener is delegated, so it still works for buttons added later by another script.
  • After a number of page views: fires once the visitor has seen the number of pages you set.
  • On a repeat visit: fires on visit number two or later. A visit is a session, and a gap of more than 30 minutes starts a new one.
  • After the visitor goes idle: fires after a number of seconds with no mouse, keyboard, scroll or touch activity.
  • When an element scrolls into view: you supply a CSS selector and the campaign fires when that element is half visible.

Why exit intent is desktop only:

A phone has no cursor that can leave the window, so a mobile exit popup ends up firing on a back gesture and reads as a trap. Engage keeps exit intent to desktop by default. There is a setting that allows a touch based approximation on mobile, but it is off by default and is best left that way.

Triggers are evaluated in the visitor's browser, which is what lets them work correctly on a page served from a full page cache.

Only one trigger applies per campaign. If you want the same offer on two different triggers, duplicate the campaign and change the trigger on the copy. That also gives you two clean sets of numbers to compare.

Ready to stop reading and start using?

Every plugin documented here works alongside the others, managed from one ResultsAIx Hub.