Outcome. Every 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 map
Enrollment, branches and actions at a glance
reporting-alerts-038
flowchart TD
A[Contact created] --> B[Set first_touch_channel from analytics source]
B --> C[Set first_touch_date = createdate]
D[Last-touch analytics property changes] --> E[Set last_touch_channel = new value]
E --> F[Set last_touch_date = today]
When to use it, when not to
- UseUse 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.
- UseUse it as a foundation for attribution-style reporting that groups conversions by entry channel.
- SkipDo 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. - SkipDo not expect multi-touch attribution modeling from this. It captures only the first and the most recent touch, not the full path between them.
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.5 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.3 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.PDF, Markdown, JSON
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 reporting and alerts 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.
