Outcome. Once a month, an admin gets a message showing how many contacts moved from each lifecycle stage to each other stage that month, so funnel movement is visible as transitions, not just stage totals.
flowchart TD
A[Scheduled trigger: monthly, day 1, 08:00] --> B[Custom code: query lifecyclestage property history, previous month]
B --> C[Tally counts per from-stage, to-stage pair]
C --> D{Any transitions found?}
D -->|yes| E[Format list sorted by count, descending]
D -->|no| F[Format fallback: no lifecycle stage changes last month]
E --> G[Send message to Slack or email]
F --> G

When to use it, when not to
- UseUse it when the standard lifecycle stage funnel report, which shows cumulative counts per stage, is not enough, and the team wants to know specifically how many contacts went from Lead to MQL versus MQL to SQL in a given month.
- UseUse it to spot a stage bleeding contacts sideways, for example a large number moving from MQL to Other, meaning disqualified, rather than forward.
- SkipDo not use it on a portal with fewer than a few hundred lifecycle stage changes a month. The transition counts will be small enough to read directly off each contact's property history.
- SkipDo not treat this as a substitute for the native lifecycle stage report on a dashboard, which is faster to build and easier to filter by date range for a single-stage question.
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.





