The Workflow Library

Library / Marketing ops / marketing-ops-034

Attribution data lock after SQL handoff for reporting integrity

Marketing opsContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Once a contact is handed to sales as a Sales Qualified Lead, the attribution values marketing reports on are frozen in a snapshot, so a later re-import, merge, or new campaign touch never quietly rewrites numbers already reported to leadership.

Workflow map Enrollment, branches and actions at a glance marketing-ops-034
flowchart TD
    A[Lifecycle stage changes to Sales Qualified Lead] --> B{Attribution locked already true?}
    B -->|No| C[Snapshot original source and first touch campaign]
    C --> D[Set attribution_locked = true]
    B -->|Yes| E[No action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse once your team has been burned by an attribution report changing after the fact because a later touch rewrote first-touch or last-touch fields.
  • UseUse alongside marketing-ops-010 (first-touch lock) to cover the fuller attribution set, not only first touch.
  • SkipDo not use if attribution fields already stop changing on their own after SQL handoff in your portal; check current behavior on a test record before building this.
  • SkipDo not expect this to prevent someone from editing the original fields directly. It creates a separate frozen snapshot for reporting; it does not lock the source field itself. See Known pitfalls.
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.5 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.