Core features

Automations

See a behaviour, act on it — in the page, while the visitor is still there.

The shape of an automation

A trigger starts it, conditions decide which way it goes, and actions do something. You build it on a canvas by dragging nodes and connecting handles; branches can rejoin, so two paths can end at the same action and it runs once either way.

Everything runs in the visitor's browser, which is what makes an exit-intent popup possible at all — there is no round trip to wait for.

Triggers

Thirteen, all evaluated client-side.

Trigger	Fires when
`Page View`	A visitor lands on a page you specify.
`Click`	A visitor clicks an element you select.
`Scroll Depth`	A visitor scrolls past a depth.
`Time on Page`	A visitor has been on the page for a set time.
`Exit Intent`	The cursor moves as though leaving the page.
`Inactivity`	No interaction for a set period.
`Rage Click`	Repeated rapid clicks in one spot.
`Form Abandonment`	A form is started and left unsubmitted.
`JS Error`	A JavaScript error fires.
`Tab Hidden`	The tab is backgrounded.
`Tab Visible`	The tab is brought back.
`Custom Event`	You call `seentics.track()` with a matching name.
`Identify`	You call `seentics.identify()`.

Flow control

Node	Does
`If / else`	Splits on a set of rules. Two outlets, Yes and No.
`Switch`	Several cases, first match wins, plus an “otherwise” outlet.
`Wait until`	Holds until its rules pass, or until a timeout you set.
`Delay`	Pauses before the next on-page action.

Actions

Nine. Seven happen in the page; two leave it.

Action	Does
`Show Modal`	A popup with a title, body and optional button.
`Show Toast`	A small notification, positioned and timed.
`Show Banner`	A full-width banner, top or bottom.
`Show Tooltip`	A tooltip attached to any element.
`Highlight Element`	Draws attention to an element, optionally scrolling it into view.
`Personalize Content`	Swaps the text or HTML of an element.
`Redirect`	Sends the visitor to another URL.
`Tag Session`	Labels the session so you can filter on it later.
`Webhook`	POSTs to an endpoint you choose — Slack, your own API, anything.

Tag Session is quieter than it looks

It changes nothing the visitor can see, but it makes “sessions where X happened” a filter in replays. Useful as a branch of a larger automation.

Collecting emails with a form

Turn on Collect emails with a form in a modal action and the button is replaced by a form: an email field, up to seven more (text or phone), a thank-you message, and an optional consent checkbox. Submissions are listed on the automation's own page, under Submissions, where you can search them, export a CSV, or delete one. They are also sent on to the destinations you choose for that form: Zapier or any webhook, Mailchimp, Klaviyo or HubSpot (see Integrations).

Send submissions to. Under the form in the builder, send to every destination (the default, which includes ones you add later) or tick the ones this form should use. A form can send to several at once.
Kept for 90 days. Seentics is not a contact database: submissions stay on the automation's page for 90 days, then are deleted. Keep long-term contacts in the tool a destination feeds, such as your email platform, CRM or a spreadsheet.
Each submission records the popup, the A/B variant and the page it came from, so you can see which message produced it.
A successful submit records a lead_captured custom event, so you can build a goal or a funnel step on it.
Bots are filtered with a hidden honeypot field and a per-visitor rate limit; nothing is stored for a submission that trips either.

Submissions are personal data you collect from your visitors. Ask for consent where your jurisdiction requires it, using the consent checkbox, and delete a submission on request.

Popup types, prizes and coupons

A modal's Popup type chooses its layout, and a bar can carry the same mechanics. The builder shows a live preview that runs the same code as your site, so what you see is what visitors get. Nothing you submit in the preview is sent or stored.

Type	What it does
`Spin to win`	A prize wheel unlocked by an email. Each slice has a label, a relative weight and an optional coupon code; a slice with no code is a “try again”.
`Multi-step`	One to five one-tap questions, then the email. Answers are stored on the lead under each question’s name.
`Countdown`	A timer: per visitor (starts the first time they see it) or counting to a fixed date. It can close the popup or show a message when it ends.
`Teaser tab`	Shows a small tab on the page edge that opens the popup when clicked, instead of covering the page.
`Sticky bar`	A banner pinned to the top or bottom with an inline email form, and optionally a countdown or coupon.
`Coupon`	A code shown in the popup. Behind an email form it is revealed only after the email is submitted.

The wheel’s prize is chosen on the server, by weight, when the email is submitted — never in the visitor’s browser. Coupon codes are removed from the copy of the popup sent to the page and arrive only with the prize, so they cannot be read ahead of time.
Each email wins once per popup: submitting the same address again returns the prize it already won rather than spinning again. It does not stop a visitor using several addresses, so treat a prize as a marketing incentive, not a secured entitlement.
Teaser tabs, countdowns and coupons combine with any popup type. A wheel and a multi-step popup both need the email form, which the builder switches on for you.
Animations stop for visitors who prefer reduced motion, popups can be closed with Escape, and the dialog keeps keyboard focus inside while it is open.

Keeping it from becoming annoying

Frequency caps — how often a visitor may see this automation at all.
Cooldowns — a minimum gap between firings.
Priority — which automation wins when two could fire at once.
A/B variants — split traffic between versions and compare.

Firing one from your own code

A custom event trigger is the general-purpose hook. The same call also records the event and advances any matching funnel step.

cart.js

// Records the event, advances the funnel, and fires any
// automation with a Custom Event trigger for this name.
seentics.track('cart_abandoned', { value: 168 });

Checking it works

The automations list shows runs and a success rate per automation, so a webhook that started failing is visible without opening it. An automation with no runs has either never been triggered or is paused.