The Workflow Library

Library / Reporting and alerts / reporting-alerts-037

Weekly digest: content/landing page performance summary (views, submissions)

Reporting and alertsContactMarketing Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. Once a week, the marketing channel gets one message showing each landing page's views and submissions for that week, so page performance is visible without opening the Content or Landing Pages tool.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-037
flowchart TD
    A[Weekly schedule: Monday 09:00] --> B[Report: page views by page, last 7 days]
    A --> C[Report: form submissions by page, last 7 days]
    B --> D[Combined on Weekly Content Performance dashboard]
    C --> D
    D --> E[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 on a portal running several live landing pages at once, where a weekly glance at views and submissions replaces individually checking each page's analytics.
  • UseUse it to catch a page that suddenly loses traffic or stops converting, faster than waiting for a monthly campaign wrap-up.
  • SkipDo not use it as a substitute for full page analytics (traffic sources, bounce rate, time on page). This digest reports views and submission counts only.
  • SkipDo not use it if the portal runs one or two pages total. Checking the page's own analytics tab directly is just as fast.
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.