Outcome. A known contact who views a "versus [competitor]" page gets differentiation content right away, and a contact who visits more than once inside a week triggers a sales alert instead of staying inside marketing alone.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-019
flowchart TD
A[Page view: competitor comparison page] --> B[Set competitor_page_last_viewed]
B --> C{Which competitor?}
C -- A --> D1[Send: vs Competitor A email]
C -- B --> D2[Send: vs Competitor B email]
C -- C --> D3[Send: vs Competitor C email]
C -- Other --> D4[Send: general differentiation email]
D1 --> E{2+ competitor page views in 7 days AND alert not yet sent?}
D2 --> E
D3 --> E
D4 --> E
E -- Yes --> F[Notify owner] --> G[Set alert_sent = true]
E -- No --> H[No action]
When to use it, when not to
- UseUse when the site has one or more dedicated competitor comparison pages tracked well enough to identify which competitor a visit was about.
- UseUse it as an intent signal layered on top of general nurture, not a replacement for it. A single comparison-page view does not mean the contact is ready to buy.
- SkipDo not use it if comparison pages are not built as separate, trackable URLs per competitor. A single generic "competitors" page cannot drive the per-competitor branch in Steps.
- SkipDo not fire the sales alert on the very first visit. A single page view is common browsing behavior; the repeat-visit threshold in Steps exists to filter noise before a rep gets involved.
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.24 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 lead nurturing 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.
