Notifications

A notification rule watches for something you care about, such as a sale, a sign-up, a goal or a funnel someone finishes, and tells you the moment it happens. Each notification says what happened, who did it, and opens the visit behind it.

Open Notifications, under Settings in the sidebar. The page has two tabs: Notifications, the ones your rules have sent, and Rules, the rules themselves.

Creating a rule

Click Create rule at the top of the Rules tab. Create notification rule in the sidebar's create menu opens the same window. The Create rule window asks for:

Click Create rule to save. A new or changed rule starts matching within a minute.

Without a name, the field says "Give the rule a name." and the window asks you to "Finish the highlighted fields first." A row with nothing picked, or a filter with no value, is highlighted the same way.

Slack also appears under Also send to, marked Coming soon. It cannot be picked yet.

Event rules

"Notify me when any of these events happen." Pick an event in the When row from the list of events your audience has recorded, the same list the report builder offers: page views, link clicks, scrolls and your own custom events. Events your server sends through the API set off rules too.

Add event adds another row, joined by or: the rule fires on any one of them. A rule takes up to 10 events.

Funnel rules

"Notify me when one visit does these steps, in order." The rows become Step 1, Step 2 and so on, and a funnel needs at least two. Add step adds one, up to 10. Other pages and events can come between the steps, as long as the steps happen in order within one visit.

A funnel rule is checked when the visit ends, as the visitor closes the page or switches away from its tab, so its notification arrives then rather than at the last step. On the Rules tab, a funnel rule reads as its steps joined by arrows, then "completes in one session".

Revenue rules

"Notify me when any of these payments come in." Each row is a kind of payment:

Payments come from the payment provider you connected, not from events your site tracks. What arrives lists which payments each provider reports as renewals. A new revenue rule starts on New sale. Payments you import from a provider's history do not set off notification rules.

Goal rules

"Notify me when a visit completes any of these goals." Pick from the audience's saved goals. A goal rule notifies once per visit, however many times the visit completes the goal. Goal rows take no filters: the goal itself already says what counts.

With no goals saved, the window says "This audience has no saved goals." and links to the Goals page.

Filters

Click the filter button at the end of a row to narrow it to some of its events. The first filter follows where on the same line, and each one after it starts a new line with and. Each row takes up to 5 filters.

A filter is a property, an operator and a value:

• Event rules and funnel steps can filter on the page's path, hostname and title, where the visitor is (country, region, city, timezone), what they use (browser, browser version, OS, OS version, device), and the event's own properties.
• Revenue rules filter on Amount, Product and Currency. The amount is compared in your audience's reporting currency, which the field's label names, such as Amount (USD). A payment that could not be converted has no amount, so an Amount filter never matches it.

Only page views and scrolls reach an event rule with their page. A custom event or a link click is checked without one, so a filter on path, hostname or title never matches it.

Channel, source, UTM and a visit's totals are not offered. They describe the visit as a whole, which is not known yet when an event arrives.

The operators depend on the property: is, is not, contains, not contains, starts with and ends with for text, greater than, greater or equal, less than and less or equal for numbers, and is null and is not null for any property.

• is matches the exact value, capitals included. contains, starts with and ends with ignore capitals.
• Several values in one filter match any of them, or, with is not, none of them.
• Several filters on one row must all match.
• An event without the property fails is and contains, and passes is not.

Snooze

Snooze after each notification keeps a busy rule quiet. After the rule sends a notification, it skips every match, from any visitor, until the snooze runs out. Skipped matches are not saved up and sent later: as the window puts it, "While the rule is snoozed, matches are skipped and never sent later."

Where notifications show up

The Notifications tab

The Notifications tab lists what your rules have sent, newest first, 50 to a page. Each notification is a card with the rule's name as its title, what happened under it, and when. An unread one has a dot beside its title.

Click a card to mark it read. When the notification came from a visit, the card also opens it underneath: the visit's session card, the same one the Sessions page shows, with where the visitor came from, the pages they saw and what they did. "Session details are no longer available." means that visit is gone. A notification without a visit, such as a Preview or a payment your provider reported without one, has nothing to open.

Mark all read, beside the tabs, marks every notification read.

Read and unread are shared by the team: a notification anyone opens or marks read is read for everyone on the audience.

The date range at the top of the page narrows the list, and the footer counts it, such as "12 notifications in this period". The unread count is not narrowed: it always counts every unread notification. Notifications are kept until the audience is deleted, including those of rules you have since deleted.

The bell

The bell at the right of the top bar shows how many notifications are unread, up to 9+. Click it for a list of the newest ones, with Mark all read at the top and See all at the bottom, which opens the Notifications page. Click a notification in the list to open it on that page.

Closing the list marks the notifications it showed as read. With no notifications yet, it says "No notifications yet. Create a rule and they'll show up here."

Live cards

While the app is open, a card pops up at the top right of whatever page you are on the moment a notification arrives. View opens it on the Notifications page and Close dismisses it.

A card stays up for 8 seconds, and longer while the pointer is on it. Cards that arrive while the tab is in the background wait, and show when you come back to it. When a rule sends a burst, the first three in 10 seconds get a card each and the rest share one card that counts them, such as "4 more notifications".

The browser tab's title counts unread notifications too, such as "(2) Goals | Spreelytics".

Live cards are not shown on share links or in the demo.

What a notification says

A notification's title is the rule's name. Under it, a sentence says what happened, and a "by" line names who did it: the person's name, or their email, when you have identified them, otherwise "an anonymous visitor". A payment from someone you have not identified uses the name or email the payment provider sent. Icons follow for their country, browser, OS and device; hover one for its name.

A page view or a scroll names its page. A custom event or a link click does not, because it reaches the rule without one.

Amounts are in your audience's reporting currency. When the customer paid in another currency, their own amount follows in brackets, such as "€45.20 ($49.00)".

A notification email carries the same news as one sentence, such as "Jane Doe in Berlin, Germany just paid $49.00 for Pro plan".

Email

Turn on Email under Also send to and the rule also emails your team: everyone on it who uses Spreelytics, whatever their role, unless they have turned notification emails off. They are on until you turn them off.

Each rule emails at most 50 notifications a day, counted from midnight UTC. Past that, its notifications still reach the app and its live cards, but no more emails go out for that rule until the next day.

Each person decides for themselves. Email preferences in your account settings has a Notifications switch, described as "Emails from notification rules that have Email turned on." It covers every team you are in, and changes nobody's rules. The unsubscribe link in a notification email turns it off too, after asking you to confirm.

Managing rules

The Rules tab lists the audience's rules. Search rules matches their names, and the footer counts them, such as 4 rules.

Click a row, or Edit rule in its … menu, to change it in the same window, titled Edit rule. Save changes stores your changes.

Preview

Preview in a rule's … menu sends one notification now, titled "Preview: " and the rule's name, so you can see what the rule will say. It uses the rule's own first event, steps, payment or goal, with example values for the rest: done by "Jane Doe" in Berlin, Germany, on Chrome, on the page /pricing, and a payment of 49.00 in your reporting currency for "Pro plan". The page is an example too: a real notification for a custom event or a link click names no page.

A Preview pops up as a live card and is listed on the Notifications tab, unread. It is never emailed, it ignores the snooze, and it does not count towards Triggered or Last triggered.

Delete

Delete asks you to confirm first. The notifications the rule already sent stay in the list. Deleting cannot be undone.

Who can do what

Viewers do not get the Create rule button or the row menus, and their On switches cannot be changed. The server refuses rule changes from anyone with the Viewer role.

Other ways to manage rules

• From AI. The AI assistant, on the Growth plan, and an AI app connected over MCP can list, create and change rules, and pause or resume them, when you ask, for example "tell me when someone buys the Pro plan". Email stays off unless you ask for it. Making changes this way needs the Editor or Admin role, the same as in the app. Deleting a rule is done in the app.
• Through the API. The Notifications API lists, creates, changes, previews and deletes rules with an account key, and reads the notifications they sent and marks them read.

Related

• Goals: the goals a goal rule watches for.
• Funnels: build a funnel to explore, then watch for it with a funnel rule.
• Revenue: connect the payment provider that revenue rules listen to.
• Sessions: the visits notifications open.