The Workflow Library

Library / Reporting and alerts / reporting-alerts-049

Weekly digest: top marketing sources by contact-to-customer conversion count

Reporting and alertsContactMarketing Hub ProfessionalAdvanced~45 min to buildFull spec

Outcome. Once a week, marketing gets a message ranking the top original sources by how many contacts became customers that week, so channel effectiveness is visible beyond raw lead volume.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-049
flowchart TD
    A[Weekly schedule: Monday 09:00] --> B[Report: contacts became Customer, last 7 days, grouped by Original Source]
    B --> C[Sorted by count, top sources first]
    C --> D[Email sent to marketing distribution list or Slack address]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when marketing wants a conversion-weighted view of channel performance, not just a count of new contacts per source such as reporting-alerts-010.
  • UseUse it as a lightweight, always-on companion to a full multi-touch attribution report, for teams that do not need model-based attribution weekly.
  • SkipDo not use it as a substitute for a proper attribution report if the sales cycle is long; a contact converting to Customer this week may have entered the funnel through that source months ago, so this digest measures conversion timing, not the campaign that ran this week.
  • SkipDo not use it on a portal with very few weekly conversions; the ranking will be noisy with small sample sizes and swing widely week to week.
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.