Skip to content

Attribution data lock after SQL handoff for reporting integrity

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.

Contact5 stepsUpdated for HubSpot seat pricing
OutcomeOnce 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 mapmarketing-ops-034
Lifecycle stage changes to Sales Qualified Lead leads to Attribution locked already true?. Attribution locked already true? leads to No: Snapshot original source and first touch campaign; Yes: No action. Snapshot original source and first touch campaign leads to Set attribution_locked = true. No Yes Lifecycle stage changes to Sales Qualified Lead Attribution locked already true? Snapshot original source and first touch campaign No action Set attribution_locked = true
Lifecycle stage changes to Sales Qualified Lead leads to Attribution locked already true?. Attribution locked already true? leads to No: Snapshot original source and first touch campaign; Yes: No action. Snapshot original source and first touch campaign leads to Set attribution_locked = true. No Yes Lifecycle stage changes to Sales Qualified Lead Attribution locked already true? Snapshot original source and first touch campaign No action Set attribution_ locked = true

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use 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.
  • Use alongside marketing-ops-010 (first-touch lock) to cover the fuller attribution set, not only first touch.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 5 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Marketing ops spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library