Outcome. A lead a sales rep personally sourced, a referral, a cold outreach reply, a conference conversation, gets attribution correctly labeled as sales-sourced, instead of inheriting whatever marketing-tracked source happened to be present from an earlier, unrelated touch.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-050
flowchart TD
A[Sales sourced override set to true] --> B{Sales sourced context provided?}
B -->|Yes| C[Set attribution_source_final = Sales-sourced + context]
C --> D[Notify marketing ops with details]
B -->|No| E[Notify owner: context required before override applies]
When to use it, when not to
- UseUse when sales frequently sources their own leads outside marketing's tracked channels, and marketing's attribution reports currently misclassify those as a marketing channel because of an earlier stray touch, for example a person who once filled out an old form and years later gets personally prospected by a rep.
- UseUse to keep sales-sourced pipeline visible and separately reportable from marketing-generated pipeline.
- SkipDo not use to let sales relabel a genuinely marketing-generated lead as sales-sourced to claim credit. Pair the override action with a required reason field and periodic spot-checks to keep the data honest.
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.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.
