Notifications

When an alert rule fires, Aperture delivers a notification on every channel you configured for that rule. A notification is a delivery of an alert, not a separate condition. The alert is what Aperture detected. The notification is how it reaches you.

Delivery channels

Each alert rule has its own delivery configuration. You set it in the rule creation wizard and can edit it afterwards. Aperture supports four channels.

Email

When email delivery is enabled for a rule, Aperture sends an “Alert Triggered” email to every recipient configured on that rule. Recipients can be:

Organisation members. Any member of your workspace, selected by name in the rule’s delivery step.
Additional addresses. One or more free-text email addresses. These are useful for shared inboxes or team distribution lists.

All configured recipients receive the same email at the same time. The email shows the rule name, its description and type, the number of violations found, and a list of the affected products with a brief trigger description for each. Where available, each product name links to its detail page in Aperture. Recipients who have the Ask page enabled also see an “Open in Ask” link after each product. It opens that alert as its own Ask thread.

Test notifications

You can send a synthetic test notification from the alert rules list at any time. Use the Test notifications button on the rule’s row. The test fires on every channel configured for the rule, so you can confirm that the email addresses are correct and that your Slack channel is connected before a real event occurs. It also sends a test message to the AI assistant chat, so you can confirm that the proactive chat channel works if it is enabled for your workspace. Test emails carry a [TEST] subject prefix and include placeholder copy, so they are easy to tell apart from live alerts. Test Slack messages are prefixed with 🧪 [TEST] on the title.

Slack

When Slack delivery is enabled, Aperture posts a message to the connected Slack channel each time the rule fires. The message shows the rule name and type, a description, and the list of affected products with their trigger descriptions and links to the product page. Before you can select Slack delivery on a rule, you must connect a Slack workspace in Settings → Integrations. See Integrations & API Keys for setup steps.

Delivering Alerts to Slack walks through the full Slack delivery flow, from connecting the integration to receiving an alert in Slack.

In-app alert inbox

Every fired alert also appears in the alert inbox. This is the Alerts page, reached from the bell-icon item in the sidebar. The inbox is the main place to triage alerts. Alerts arrive in an unread state. You can mark them read, or postpone them to a later time. The inbox is always active, regardless of email or Slack settings. The Alerts page documents inbox behaviour, state transitions, and bulk actions.

Proactive chat messages

When the proactive alerts feature is enabled for your workspace, Aperture also delivers new alert events to the AI assistant chat, even while the chat drawer is closed. The message lands in your daily brief thread for today, using your workspace’s timezone. When it lands in the thread you currently have open, which is normally today’s brief, a pop-out “AI Alert” tab appears briefly at the edge of the screen, and an unread badge lights up on the chat launcher. If you have a different thread open, the message does not appear there. Today’s brief thread is marked unread instead, and the launcher badge still lights up while the drawer is closed. Open the chat drawer to see the message itself. The message is phrased from your workspace’s perspective. Brand users see “Heads up — a new alert on your product” framing. Retailer users see competitor-move framing, such as “Heads up — a new competitor alert”. The message reaches the same organization members configured as recipients on the alert rule. Free-text additional email addresses are not app users, so this channel cannot reach them. When several alerts fire together, Aperture consolidates them into a single message that lists the first five affected products and summarises the rest. Proactive messages are de-duplicated per rule firing. Re-evaluating an already-open alert does not produce a second message. AI Assistant (Chat) documents the full chat assistant capabilities.

Postpone reminders (redelivery)

When you postpone an alert in the inbox, you choose a future time at which you want a reminder. Postpone times snap to the top of the hour, so the time you land on is always a whole hour, keeping the reminder predictable. When that time arrives, Aperture automatically re-sends the notification on the same email and Slack channels configured on the alert rule at the moment of redelivery. The reminder repeats the details recorded when the alert fired. Aperture does not re-evaluate the condition, so the reminder is sent even if the underlying issue has since cleared.

Reminder emails and Slack messages are marked as reminders:

Email. The subject line and the email heading gain a [Reminder] prefix, and a banner at the top of the email reads “You postponed this alert on <date and time>. Sending again as requested.” The date and time are shown in your workspace’s timezone.
Slack. The message title is prefixed with ⏰ “Reminder — Alert Triggered: …”

After Aperture sends the reminder, the alert returns to unread in your inbox so you can triage it again. You can postpone it a second time if needed.

If the alert rule is deleted or disabled between the postpone and the reminder time, Aperture skips the reminder. Aperture also skips the reminder when the rule has no live channel left. That means Slack delivery is off AND email delivery is either off or has no resolvable recipients. A rule with Slack delivery still on gets its Slack reminder even if no email recipients resolve. In each case where the reminder is skipped, the alert returns to unread in your inbox and no message is sent.

MAP violation outreach emails

Separate from alert notifications, Aperture supports sending a direct outreach email to a retailer about a MAP violation case. Your team composes these emails in a WYSIWYG editor and sends them manually from the MAP violation detail view. You can pick a tone (Professional, Assertive, or Friendly) to start from a matching template, then edit the message before sending. Sending moves the case to the notified status; a case already resolved cannot be notified. On a case that is already notified, the detail view offers Notify retailer again, so you can send another email. You can also ask the AI assistant to send the email. It shows a preview, and the email goes out only after you confirm. The assistant refuses to notify a case that is already notified. These emails are not automatic, and they are not configured through alert rules. See MAP Violations for details.