Skip to main content
Account notifications are emails Sequenzy sends to you about your workspace, as opposed to the emails you send to your subscribers.
Sequenzy notification settings with callouts showing subscriber and campaign alerts
Four events are available:

​
Modes

Each notification is set independently:
  • instant - one email per occurrence
  • daily - one summary per day, listing who joined (new subscribers only)
  • weekly - one report per week (weekly report only)
  • off - no email
The three per-occurrence notifications default to off - turn on the ones you want in Settings → Notifications. The weekly report defaults to weekly for the workspace owner; turn it off there if you would rather read the numbers on the Metrics page. Invited members (admins and viewers) default to off and can turn it on for themselves. form_submitted and campaign_completed do not support daily. Each submission and each campaign finish is its own event, so a daily rollup would almost always be a list with a single row in it. weekly_report supports only weekly and off. Use Form submitted when a form is a lead (quote request, contact form, demo request) and you need an email every time, not only the first time that address appears. New subscriber is the list-growth alert: it still fires only when a contact is created. To protect your inbox and Sequenzy’s system sender from abusive traffic on public forms, instant form-submission notifications stop after 50 accepted submissions per workspace per UTC day. Submissions continue to be processed normally; only the account-notification email is suppressed until the next UTC day.

​
What does not trigger a new-subscriber notification

Imports never notify. Uploading a CSV or running a migration creates thousands of contacts, and none of them produce an email. This holds even when you turn Enroll in sequences on for the import - that setting decides what happens to the contacts, not whether you hear about each one. The same applies to an integration’s initial backfill sync and to events replayed from more than an hour in the past. For a single contact created through the API, CLI or MCP, a supplied createdAt at most one hour old still qualifies for a new-subscriber notification. Older signup dates do not notify on creation; a later double opt-in confirmation can still notify. This does not change sequence enrollment defaults or the rule that bulk imports do not notify on creation. Everything that represents a real-time signup counts, whether or not it enrolls the contact in sequences: form and popup submissions, landing pages, the subscribers and events APIs, tagging a brand-new address, payment-provider and plugin webhooks, and adding a contact by hand from the dashboard. With double opt-in on, you are notified when the contact confirms, not when they sign up. Someone who requests the confirmation email and never clicks it never produces a notification, so what lands in your inbox matches who actually joined your list. A confirmation is a real person clicking a link, so it notifies even if the pending contact originally arrived in an import.

​
The daily cap

If you are set to instant and your workspace passes 50 signups in one UTC day, per-signup emails stop for the rest of that day. You get one email explaining the switch, and the remainder arrive as a single summary. This keeps a viral day from turning into hundreds of emails. Nothing is lost - the summary reports the true total for the day, including the signups that were not sent individually.

​
The weekly report

Every Monday from 08:00 UTC, each workspace that sent more than 10 emails during the previous Monday-to-Sunday week gets one short email. It fits on one screen:
  • One row of numbers against the week before: sent, open rate, click rate, and revenue (or new subscribers for workspaces that track no revenue)
  • Worth a look: up to two sequences whose open rate, click rate, unsubscribe rate, or attributed revenue got meaningfully worse, each linked to the sequence. A sequence needs at least 20 sends in both weeks and a change of at least one percentage point and 15% relative before it is called out, so a sequence that sent twelve emails does not read as a collapse
Per-sequence numbers, goal conversions, unsubscribes, and campaign counts stay on the Metrics page, which the report links to. If you belong to several workspaces, your two busiest ones share one email. The 10-send threshold is the whole gate: a workspace that did not send that week gets nothing, however its members’ settings are set. That keeps the report out of the inboxes of people who signed up, looked around, and moved on. By default only the workspace owner receives the report. Teammates who want it turn it on for themselves under Settings → Notifications, so inviting a large team never fans one workspace’s numbers out to a dozen inboxes unasked. Numbers come from the same analytics as the Metrics page and exclude test sends. If a worker outage delays the Monday run, the report goes out as soon as the scheduler recovers, up to Wednesday; after that the week is skipped rather than sent stale.

​
Unusual signup activity alerts

Separately from the notifications you opt into, Sequenzy watches each workspace’s public form signup volume. If a day’s signups climb far above the workspace’s recent baseline - the pattern of a bot scripting a public form (list-bombing) - every non-restricted workspace member gets one security alert email for that day, regardless of their notification settings. The email shows the day’s count against the baseline and suggests next steps: review the newest subscribers, pause any welcome sequence on the affected list, and consider enabling double opt-in so unconfirmed signups never reach your lists.

​
Per person, not per workspace

These settings belong to you, not to the workspace. Each teammate chooses their own, and changing yours never changes anyone else’s. Members with restricted (link-only) access do not receive account notifications at all. If you belong to several workspaces, you configure each one separately.

​
Changing your settings

Go to Settings → Notifications.

​
Sending this somewhere other than email

For Slack, Zapier, or your own service, use an outbound webhook on the subscriber.created event instead. Unlike the notification above, that event fires for every created contact, including imports, and carries a source field you can filter on.