Outcome. A contact who goes quiet for a long stretch and then comes back through a completely different channel gets their attribution properties refreshed to reflect what actually brought them back, instead of permanently crediting a source from a year-old, unrelated first touch.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-028
flowchart TD
A[New engagement, prior engagement 180+ days ago] --> B[Capture new session source]
B --> C[Set attribution_reset_date]
C --> D[Set dormancy_reset_flag]
D --> E[Notify marketing ops, optional]
When to use it, when not to
- UseUse when your reporting relies on original source properties and stale attribution from long-dormant contacts is skewing channel performance numbers.
- UseUse when a meaningful share of your contact base goes dormant for months and later re-engages through a different channel than their original touch.
- SkipDo not use this fiche if your reporting model intentionally treats original source as permanent regardless of dormancy; some attribution models are deliberately "first touch forever" by design, and this fiche would work against that choice.
- SkipDo not use for contacts with continuous, regular engagement. This fiche is specifically about the dormant-then-returned pattern, not routine re-engagement within normal activity cycles.
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.4 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.4 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 marketing ops 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.
