The Workflow Library

Library / Reporting and alerts / reporting-alerts-026

Anomaly alert: unsubscribe rate spike after a campaign send

Reporting and alertsContactMarketing Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. Once a week, the marketing channel gets a message flagging any send from that week whose unsubscribe rate crossed a set threshold, so a poorly received campaign gets reviewed without waiting for a monthly report.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-026
flowchart TD
    A[Weekly schedule: Monday 09:00] --> B[Report renders: sends from last 7 days, sorted by unsubscribe rate]
    B --> C[Highest unsubscribe rate at top]
    C --> D[Email sent to Slack channel inbound address]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on portals without Data Hub Professional that still want some visibility into unsubscribe spikes, on a weekly review cadence rather than real time.
  • UseUse it to catch a specific send, wrong audience, off-brand content, too-frequent cadence, worth a follow-up conversation with the sender.
  • SkipDo not use it expecting a true per-send, same-day alert. This is a periodic review digest built on native reporting, not an instant anomaly detector. See reporting-alerts-025's custom-code pattern for a real-time, per-send alert, which needs Data Hub Professional.
  • SkipDo not use it if unsubscribe rates are consistently low across all sends. There will be nothing to flag most weeks, and a plain weekly send-performance report is simpler to just glance at directly.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.2 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the reporting and alerts pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.