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.

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.