The Workflow Library

Library / Marketing ops / marketing-ops-031

Custom object campaign/event attribution rollup to contact

Marketing opsCustomMarketing Hub EnterpriseAdvanced~60 min to buildFull spec

Outcome. Contacts show which HubSpot campaigns actually touched them and how many times, directly on the record, without anyone cross-referencing engagements against the Campaigns tool by hand.

Workflow map Enrollment, branches and actions at a glance marketing-ops-031
flowchart TD
    A[latest_campaign_engaged changes] --> B[Custom code: create Campaign Touch record, recount]
    B --> C{result_code ok?}
    C -->|Yes| D[Set campaigns_touched_count]
    D --> E[Set primary_campaign]
    C -->|No| F[Notify marketing ops of logging failure]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when you run several parallel campaigns and need "campaigns touched" visible on the contact record itself, not only inside the Campaigns tool's own reporting.
  • UseUse when native first-touch and last-touch properties alone are not enough to see the breadth of campaign engagement for a contact.
  • SkipDo not use if you only run one or two campaigns at a time. The native Campaigns tool's own reporting already answers "who did this campaign reach" without a custom object.
  • SkipDo not use without Marketing Hub Enterprise. This fiche depends on a custom object and a custom coded action, both Enterprise-tier or Data Hub-gated capabilities. A Professional-tier substitute is in Variants.
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.