Outcome. A contact who declines cookie tracking consent gets set to non-marketing status right away, so the portal stops sending to, and paying for, someone who explicitly opted out of tracking-adjacent marketing.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-033
flowchart TD
A[Cookie consent status changes to Declined] --> B{Currently Marketing contact?}
B -->|Yes| C[Set marketing contact status: Non-marketing]
C --> D[Notify marketing ops]
B -->|No| E[No action]
When to use it, when not to
- UseUse if your consent management platform (CMP) writes the decline decision into a HubSpot property, either through a native integration or a custom sync.
- UseUse to keep marketing send eligibility in sync with cookie-level consent choices, not only email subscription toggles.
- SkipDo not use if your CMP only manages cookies client-side and never syncs a decision into HubSpot as a property. There is nothing for this workflow to watch until that integration exists.
- SkipDo not treat this as your full consent record. Cookie consent and marketing-email consent are legally distinct in most frameworks; treat this as one input to your legal-basis approach in marketing-ops-005 and marketing-ops-007, not a replacement.
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.2 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.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.
