Skip to content

Property: first-touch and last-touch timestamp helpers (funnel reporting)

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.

Contact3 stepsUpdated for HubSpot seat pricing
OutcomeEvery contact carries a clean, report-friendly first-touch channel and date, plus a last-touch channel and date that updates on each new interaction, so funnel reports do not depend on parsing HubSpot's native analytics-source properties.
Workflow mapreporting-alerts-038
Contact created leads to Set first_touch_channel from analytics source. Set first_touch_channel from analytics source leads to Set first_touch_date = createdate. Last-touch analytics property changes leads to Set last_touch_channel = new value. Set last_touch_channel = new value leads to Set last_touch_date = today. Contact created Last-touch analytics property changes Set first_touch_channel from analytics source Set last_touch_channel = new value Set first_touch_date = createdate Set last_touch_date = today
Contact created leads to Set first_touch_channel from analytics source. Set first_touch_channel from analytics source leads to Set first_touch_date = createdate. Last-touch analytics property changes leads to Set last_touch_channel = new value. Set last_touch_channel = new value leads to Set last_touch_date = today. Contact created Set first_touch_channel from analytics source Set first_touch_date = createdate Last-touch analytics property changes Set last_touch_channel = new value Set last_touch_date = today

When to use it, when not to

Use it

  • Use it when the reporting team wants first-touch and last-touch as simple, stable properties they can drop straight into a report or a custom object without also pulling in HubSpot's broader analytics property set.
  • Use it as a foundation for attribution-style reporting that groups conversions by entry channel.
Read more on when to use itShow less

Skip it

  • Do not use it if the portal already reports directly off native analytics properties (hs_analytics_source, hs_analytics_last_touch_converting_campaign) inside the report builder; this fiche only helps when those native fields are harder to use directly in the reporting tool of choice.
  • Do not expect multi-touch attribution modeling from this. It captures only the first and the most recent touch, not the full path between them.
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 · 5 parts

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

Steps · 3 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 · 1 case, 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 Reporting and alerts 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