Skip to content

Multi-touch attribution property update on each new session source

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

Enterprise

Seat pricing: Enterprise 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 Enterprise.

Contact5 stepsUpdated for HubSpot seat pricing
OutcomeEvery new traffic source a contact arrives through gets logged as its own touchpoint record, so marketing ops can see the full path a contact took, not just HubSpot's default first-touch and last-touch properties.
Workflow mapmarketing-ops-018
New session source signal leads to Custom code: create Touchpoint record. Custom code: create Touchpoint record leads to result_code ok?. result_code ok? leads to Yes: Set touchpoint_count; No: Notify marketing ops of logging failure. Set touchpoint_count leads to Set last_touch_source. Yes No New session source signal Custom code: create Touchpoint record result_code ok? Set touchpoint_count Notify marketing ops of logging failure Set last_touch_source
New session source signal leads to Custom code: create Touchpoint record. Custom code: create Touchpoint record leads to result_code ok?. result_code ok? leads to Yes: Set touchpoint_count; No: Notify marketing ops of logging failure. Set touchpoint_count leads to Set last_touch_source. Yes No New session source signal Custom code: create Touchpoint record result_code ok? Set touchpoint_count Set last_touch_source Notify marketing ops of logging failure

When to use it, when not to

Use it

Read more on when to use itShow less

Skip it

  • Do not use this if the native Marketing Hub Enterprise multi-touch revenue attribution report already answers the question. That report is read-only reporting built into the Campaigns and Analytics tools and needs no custom object; build this fiche only when you need the touchpoint history available as data on the record, for example to feed a list or another workflow.
  • Do not use on a portal without a reliable way to detect "a new session started with a different source." Native workflows do not have a single trigger named that way; this fiche depends on a session-source-changed signal from either a Marketing Hub Enterprise behavioral event or an external analytics integration writing to a contact property.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 5 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 · 2 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, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

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