Setting Up Notifications and Alerts

Notifications Overview

Notifications make sure the right people hear about important activity in your account without anyone having to go looking for it. That might be a new referral, a new reward, a low balance in a payment vault, or a system error that needs attention.

There are three pieces to it, and they work independently:

• Notification channels deliver alerts about account activity outside the platform, by email, webhook, or Slack.
• System Error Notifications is a separate setting that sends you a digest of platform errors.
• In-App System Error Notification in the top navigation gives you real-time visibility into system errors while you're working in the platform.

You'll find the first two at Settings → Notifications, with System Error Notifications in its own section further down the page.

In-App System Error Notification

The notification icon in the top navigation keeps you posted on critical system errors as they happen, so you don't need to keep the Logs page open.

Here's how it behaves:

• When a new Critical level event occurs, an orange badge appears on the notification icon with a count of errors you haven't seen yet.
• Click the icon to open a dropdown of recent error groups, organized by source system. Each group shows the source name, the error count, the severity, and how long it's been since the last occurrence.
• Click any group to jump straight to the System tab of the Logs page with that source already filtered.
• Click View All to open the full Logs page.
• Opening the dropdown marks everything currently in it as seen.

A few details that help set expectations:

• The bell shows Critical and Error level events from the last 48 hours.
• Once you pass 99 unseen errors, the badge shows 99+.
• The bell stays in sync across all your open browser tabs. Mark things as seen in one tab and the badge updates everywhere.
• Errors appear within seconds, no page refresh needed.

If you don't see the notification in your top navigation, it may not be turned on for your account yet. Reach out to your Customer Success Manager or our support team and we'll take a look. 🔔

Notification channels

A notification channel is a delivery method paired with an event. Think "email ops@ourcompany.com whenever a new reward is created." Each channel has a type, a subscribed event, and a frequency.

Channel types

Frequency options

Set up a notification channel

1. Go to Settings → Notifications.
2. Click Add to create a new channel.
3. Choose the channel type: Email, Webhook, or Slack.
4. Choose the frequency: Immediate, Daily, or Weekly.
5. Choose the event you want to subscribe to.
6. Fill in the settings for your channel type:
   • Email: select which team members should receive it.
     • Note: Instead of assigning to specific contacts, you can assign to a Group of contacts configured in your Users & Roles. This is idea for managing user changes to ensure notifications don’t get lost if someone leaves your organization.
   • Webhook: enter the destination URL. A webhook token is generated automatically so your system can verify the payload.
   • Slack: enter the Slack channel ID and bot token.
7. Click Save.

Manage existing channels

• Edit: update the frequency, recipients, or other settings. The channel type can't be changed after a channel is created, so if you need a different type, create a new channel.
• Enable or disable: toggle a channel off temporarily without losing the configuration.
• Delete: remove a channel for good.

System Error Notifications

System errors are configured beneath notification channels on the Settings → Notifications page. You're not creating a channel and picking an event here. You're turning on a digest of the platform errors recorded in your System Logs, such as integration sync failures, webhook delivery problems, and payment processing issues.

Set up your system error digest

1. Go to Settings → Notifications and scroll to the System Error Notifications section.
2. Choose how you want the digest delivered: Email, Webhook, or Slack.
3. Choose the frequency: Daily or Weekly. Immediate delivery isn't offered here, and there's a good reason for that (see below).
4. Fill in the delivery details:
   • Email: select which team members should receive the digest.
   • Webhook: enter the destination URL. A webhook token is generated automatically so your system can verify the payload.
   • Slack: enter the Slack channel ID and bot token.
5. Click Save, then use Test to confirm the digest reaches its destination.

If you don't see the System Error Notifications section on the page, it may not be enabled for your account yet. Let us know and we can help.

Why the digest is daily or weekly, never immediate

During an incident, the platform can generate hundreds of errors in a matter of minutes. If each one triggered its own email, Slack message, or webhook call, your inbox would fill up at exactly the moment you need a clear picture. Digests keep that noise down and give you one readable summary instead.

The in-app system notification handles the real-time side. It groups errors by source and shows counts, so even a high-volume incident reads as a clean summary rather than a flood of individual alerts.

Together, the two paths cover both situations:

A good default to start with

If you're setting up a new account, turning on a daily email digest is a solid starting point. You'll hear about integration or platform issues without having to check your Logs page every morning. This matters most if you're running active integrations like Shopify, HubSpot, or Salesforce.

Who can manage notifications

Notification settings are available to users with an Admin, Accounting, IT, or Marketing role.

Troubleshooting

The in-app notification isn't showing new errors.

• The in-app notification only triggers for errors with a critical status. Check the error in your Logs & Table to confirm if the status is critical.
• Some corporate firewalls block the real-time connection the bell uses. When that happens the bell falls back to checking for updates about every 30 seconds, so you may see a short delay. If it still isn't updating, check with your IT team about network restrictions, then reach out to us.

I turned on system error notifications but haven't received anything. The digest only sends on your chosen daily or weekly schedule, so give it until the next scheduled delivery. Use the Test button in the meantime to confirm the setup works. And keep in mind that no digest can also mean no errors, which is good news.

My webhook stopped receiving payloads. Check your System Logs for webhook delivery failures, and confirm the destination URL and token in the receiving system still match what's saved in your settings. If the webhook is coming from an Automation, check that the Automation is still active too.

Related articles

• Logs & Audit
• Webhooks Overview
• Managing User Roles and Permissions