Outcome. Historical contacts that were never formally associated with the HubSpot campaign they actually came from get associated in bulk, so campaign-level reporting stops silently excluding pre-automation-era leads.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-047
flowchart TD
A[List membership + status = Pending] --> B[Custom code: match proxy value to Campaign, associate]
B --> C{outcome?}
C -->|Associated| D[Set status = Associated]
C -->|Skipped| E[Set status = Skipped]
C -->|Failed| F[Set status = Failed, notify marketing ops]
When to use it, when not to
- UseUse once, when a portal starts using HubSpot's Campaigns tool for attribution reporting but a backlog of older contacts predates that setup and lacks the association.
- UseUse as a one-time or occasional cleanup, not an ongoing workflow.
- SkipDo not use for new, ongoing contacts. Wire proper campaign association into your live capture process (forms, ad integrations) going forward, and use this fiche only for the historical backlog.
- SkipDo not run this without Data Hub Professional or higher. This fiche depends on a scheduled, no-native-trigger batch operation and custom coded bulk association calls, both Data Hub-tier capabilities per this taxonomy row's declared minimum.
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, 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.
