Outcome. The 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 map
Enrollment, branches and actions at a glance
marketing-ops-010
flowchart TD
A[Contact created] --> B{first_touch_capture_date blank?}
B -->|Yes| C[Copy Original source to first_touch_source]
C --> D[Copy drill-down 1 and 2]
D --> E[Set first_touch_capture_date to today]
B -->|No| F[No action, exit, already locked]
When to use it, when not to
- UseUse 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.
- UseUse 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.
- SkipDo not build this if your native
Original sourcefield 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. - SkipDo 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.
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.4 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.6 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 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.
