Outcome. Every contact carries a fixed date for the first time it entered each lifecycle stage, so a funnel velocity report can show how long a contact spent as a lead, an MQL, or an SQL before becoming a customer.
Workflow map
Enrollment, branches and actions at a glance
reporting-alerts-015
flowchart TD
A[Lifecycle stage changes] --> B{Stage = Marketing Qualified Lead?}
B -->|yes| C{date_became_mql blank?}
C -->|yes| D[Set date_became_mql = today]
C -->|no| E[No action, already stamped]
B -->|no| F{Stage = Sales Qualified Lead?}
F -->|yes| G[Same blank-check and stamp pattern]
F -->|no| H{Stage = Customer?}
H -->|yes| I[Same blank-check and stamp pattern]
H -->|no| J[No action]
When to use it, when not to
- UseUse it as the data foundation for a funnel velocity or conversion-time report (lead to MQL, MQL to SQL, SQL to customer).
- UseUse it when marketing and sales both want a shared, timestamped record of lifecycle progression, not just the current stage value.
- SkipDo not build this from scratch without first checking Settings >
Properties > Contact properties for HubSpot's native
hs_lifecyclestage_<stage>_dateproperties, which are generated automatically for standard stages on most portals. (check in your portal: confirm these native properties exist, are populated, and use the internal stage names your portal actually uses, before duplicating them with custom properties) - SkipDo not use it if the portal uses fewer than three lifecycle stages in practice (for example skipping straight from Lead to Customer). The reporting value of extra stage timestamps drops sharply on a short funnel.
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.10 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 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.
