Skip to content

Cookie consent banner declined sets contact as non-marketing

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.

Contact4 stepsUpdated for HubSpot seat pricing
OutcomeA 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 mapmarketing-ops-033
Cookie consent status changes to Declined leads to Currently Marketing contact?. Currently Marketing contact? leads to Yes: Set marketing contact status: Non-marketing; No: No action. Set marketing contact status: Non-marketing leads to Notify marketing ops. Yes No Cookie consent status changes to Declined Currently Marketing contact? Set marketing contact status: Non-marketing No action Notify marketing ops
Cookie consent status changes to Declined leads to Currently Marketing contact?. Currently Marketing contact? leads to Yes: Set marketing contact status: Non-marketing; No: No action. Set marketing contact status: Non-marketing leads to Notify marketing ops. Yes No Cookie consent status changes to Declined Currently Marketing contact? Set marketing contact status: Non-marketing No action Notify marketing ops

When to use it, when not to

Use it

  • Use if your consent management platform (CMP) writes the decline decision into a HubSpot property, either through a native integration or a custom sync.
  • Use to keep marketing send eligibility in sync with cookie-level consent choices, not only email subscription toggles.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Marketing ops spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library