The Workflow Library

Library / Marketing ops / marketing-ops-027

Campaign ROI property rollup from associated deals

Marketing opsDealMarketing Hub EnterpriseAdvanced~60 min to buildFull spec

Outcome. Every deal associated with the same marketing campaign gets a shared, always-current revenue rollup written onto it, so campaign performance can be filtered and reported on outside the Campaigns tool, in any list, report, or workflow that reads deal properties.

Workflow map Enrollment, branches and actions at a glance marketing-ops-027
flowchart TD
    A[Deal stage = Closed won, has associated Campaign] --> B[Custom code: sum and count sibling deals, write to all]
    B --> C{result_code ok?}
    C -->|Yes| D[No further action, all associated deals updated]
    C -->|No| E[Notify marketing ops of rollup failure]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when you need campaign-attributed revenue available as a deal property, for example to build a list or a report that filters deals by campaign performance tier, something the native Campaigns tool's own reporting does not expose as a reusable field.
  • UseUse once every relevant deal is reliably associated with its originating Marketing Campaign record, since this fiche rolls up from that association.
  • SkipDo not use this fiche if the Campaigns tool's built-in revenue and deal reporting already answers your question. That reporting already aggregates associated deal revenue per campaign natively, with no custom code required; build this fiche only when that number needs to live as data on the deal record itself.
  • SkipDo not use on a portal without Marketing Hub Enterprise or without custom coded workflow actions available, since both the rollup calculation and the write-back depend on a custom coded action. The custom code action requires Data Hub Professional or Enterprise (https://knowledge.hubspot.com/workflows/choose-your-workflow-actions).
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.4 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.