Skip to content

Original source / first-touch attribution capture and lock

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.

Contact6 stepsUpdated for HubSpot seat pricing
OutcomeThe moment a contact is created, their first-touch original source gets copied into a separate, workflow-managed property set that nothing else ever writes to again, giving reporting a first-touch record that survives later imports, integration syncs, or CRM re-associations.
Workflow mapmarketing-ops-010
Contact created leads to first_touch_capture_date blank?. first_touch_capture_date blank? leads to Yes: Copy Original source to first_touch_source; No: No action, exit, already locked. Copy Original source to first_touch_source leads to Copy drill-down 1 and 2. Copy drill-down 1 and 2 leads to Set first_touch_capture_date to today. Yes No Contact created first_touch_capture_date blank? Copy Original source to first_touch_source No action, exit, already locked Copy drill-down 1 and 2 Set first_touch_capture_date to today
Contact created leads to first_touch_capture_date blank?. first_touch_capture_date blank? leads to Yes: Copy Original source to first_touch_source; No: No action, exit, already locked. Copy Original source to first_touch_source leads to Copy drill-down 1 and 2. Copy drill-down 1 and 2 leads to Set first_touch_capture_date to today. Yes No Contact created first_touch_capture_date blank? Copy Original source to first_touch_source Copy drill-down 1 and 2 Set first_touch_capture_date to today No action, exit, already locked

When to use it, when not to

Use it

  • Use when attribution reporting needs a guaranteed first-touch value and you have seen native source fields change unexpectedly after a later sync or manual edit.
  • Use when multiple integrations or a CRM migration write to the contact record after creation, since some of those can touch source-related fields as a side effect.
Read more on when to use itShow less

Skip it

  • Do not build this if your native Original source field has never been observed to change after creation in your portal. Adding a locked copy is only worth the property overhead if drift is a real, evidenced problem.
  • Do not use this fiche for multi-touch attribution across the whole customer journey. It captures first touch only; see marketing-ops-018 for a multi-touch approach.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 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 · 6 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