Feature · Notifications
Notifications: when it happens, act on it.
Create rules that watch for the events you care about and fire on their own. Filter by properties, write messages with variables, and send them where your team works.
- Event and funnel rules
- Property filters
- Template variables
Pieowl · #sales · now
New purchase: $49 from Germany via Google.
The basics
What are notification rules?
- 01Choose what to watch
- 02Add property filters
- 03Write a template
- 04Pick where it goes
Notification rules are the trigger layer in Pieowl. They decide when something should happen, and integrations decide where it goes.
A rule has three parts:
- What to watch: one or more events (for example
screen_view,purchase,signup), or a whole funnel being completed - Filters: optional property conditions that narrow the match (for example the path starts with
/onboarding) - Where to send it: in the Pieowl app, by email, or to connected integrations like Slack, Discord or a webhook
For event rules you can write a template with variables like {{country}}, {{path}} or any event property. When the rule fires, the variables are filled in with real values, so the message has the context you need.
An example: you want to know when new users reach your onboarding verification page. You create a rule that:
- Watches for
screen_viewevents - Filters where path starts with
/onboardingand ends with/verify - Uses the template "New user reached verification from {{country}}"
- Sends it to your Slack channel and a webhook
Now every time someone reaches that page, your team sees a Slack message with the country, and your webhook can start any follow-up you want.
The Notifications page keeps a list of every notification that fired, so you can look back at what happened and when.
Notifications on every plan
What you can do with notifications
From simple alerts to event-driven workflows, rules put you in control.
Event-based triggers
Pick which events a rule watches, such as screen_view, purchase, signup or any custom event. The rule fires on every match.
Funnel triggers
Fire a rule when someone completes a series of steps, like finishing onboarding, instead of a single event.
Property filters
Narrow a rule with property conditions on path, country, device or any event property. Stack several filters to match exactly the events you want.
Template variables
Write messages with {{variable}} placeholders, such as {{country}}, {{path}}, {{browser}} or your own properties. Values are filled in when the rule fires.
Send it anywhere
Show the notification in the Pieowl app, send it by email, or route it to Slack, Discord and webhooks. One rule can use several at once.
Notification history
Every notification that fired is listed on the Notifications page. Manage all your rules from a separate Rules tab.
Set up
How notification rules work
Define the trigger, write the message, pick where it goes.
- 1
Choose what to watch
Select the events the rule should watch, or the funnel steps someone has to complete.
- 2
Add property filters
Optionally narrow the rule. For example, only page views where the path starts with /onboarding and ends with /verify.
- 3
Write a template
Write the message with {{variable}} placeholders. "New user reached verification from {{country}}" becomes "New user reached verification from US".
- 4
Pick where it goes
Turn on in-app or email notifications, and attach any Slack, Discord or webhook integrations. All of them get the message when the rule fires.
Use cases
How teams use notifications
From team alerts to automation, notifications make analytics act.
New signup alerts
Get a Slack message for every new signup, with the country, source or any property in the text. The whole team sees new users as they arrive.
Onboarding milestones
Get notified when someone completes your onboarding funnel or reaches a key step, so you can follow up at the right time.
Purchase alerts
Fire a notification on every purchase event. Put the plan or product in the message. Send it to Slack to celebrate and to a webhook to update your CRM.
Watch for error events
If you track errors as events, get a message when one happens on an important page, so you can look into it quickly.
Related features
Works well with
Integrations
Integrations are destinations for notifications. Connect Slack, Discord or webhooks, then attach them to rules.
Event tracking
Rules run on the events you track. The more you track, the more precise your rules can be.
Funnels
Trigger a notification when someone completes a funnel, not just a single event.
FAQ
Frequently asked questions
Common questions about notification rules in Pieowl.
What's the difference between notifications and integrations?
Integrations are connections to outside services like Slack, Discord or a webhook. Notification rules decide when to send something. You create an integration once, then attach it to as many rules as you want.
What template variables can I use?
For event rules, any field of the event with the {{name}} syntax, for example {{country}}, {{city}}, {{browser}}, {{os}} or {{path}}. Your own event properties work as {{properties.name}}. Funnel rules use a simpler message with the rule name and the steps.
Can I have several filters on one rule?
Yes. Stack as many property filters as you need. All of them must match for the rule to fire. For example, path starts with /onboarding and path ends with /verify.
Can I send to several places from one rule?
Yes. Turn on in-app and email notifications and attach as many integrations as you like. When the rule fires, all of them get the message.
Can I see past notifications?
Yes. The Notifications page lists every notification that fired, so you can look back at what happened and when.
Your first dashboard in five minutes.
14-day free trial, no card needed. Cloud in the EU. No cookies.