Outcome. Every 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 map
Enrollment, branches and actions at a glance
marketing-ops-018
flowchart TD
A[New session source signal] --> B[Custom code: create Touchpoint record]
B --> C{result_code ok?}
C -->|Yes| D[Set touchpoint_count]
D --> E[Set last_touch_source]
C -->|No| F[Notify marketing ops of logging failure]
When to use it, when not to
- UseUse when native first-touch and last-touch attribution properties are not enough, for example when a deal takes six or more touches across paid, organic, and email before converting and the team wants to see the sequence.
- UseUse when the account already has Marketing Hub Enterprise, since this fiche relies on a custom object and a custom coded action, both Enterprise-tier or Data Hub-gated capabilities. The custom code action requires Data Hub Professional or Enterprise (https://knowledge.hubspot.com/workflows/choose-your-workflow-actions) (https://knowledge.hubspot.com/object-settings/create-custom-objects).
- SkipDo 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.
- SkipDo 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.
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.5 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.
