Consent & privacy
Ballot Signal + CookieHub
What is CookieHub?
Lightweight CMP that shows up frequently on small campaign sites.
It sits in the Consent & privacy category of a campaign stack. Signals we consume, never signals we override.
Who uses it
Nonpartisan. Used across both parties and by nonpartisan organizations.
How the Ballot Signal + CookieHub integration works
A signal we consume. Ballot Signal reads CookieHub's category state and change callbacks and maps them into our normalized consent object.
What syncs
- Consent categories
- Consent change callbacks
Field mapping
The supporter record is the same shape everywhere. What changes is where each field lands. The full record is documented on what you get.
| Supporter record | Consent signal | Notes |
|---|---|---|
| — (inbound) | Consent category state | Read from this platform, not written to it. |
| consentCategories | Normalized internal consent object | Their category names mapped onto ours. |
| consentTimestamp | Captured at the moment of the affirmative act | Stored on every supporter record produced afterwards. |
| consentVersion | Your configured policy version string | A version bump re-asks the visitor. |
| consentSource | Page URL where the consent event fired | Exact URL, not just the domain. |
How to set it up
- 1
Ensure CookieHub initializes before the Ballot Signal snippet.
- 2
Assign the snippet to the marketing category.
- 3
Install the snippet.
- 4
Test decline, accept, and withdrawal.
Why it matters
Lightweight CMP that shows up frequently on small campaign sites.
Related integrations
All Consent & privacy →Google Consent Mode v2
The de facto consent grammar for the web. If your Consent Mode implementation is correct, ours inherits it for free.
WP Consent API
The only standardized consent contract inside WordPress — and the reason our plugin can be honest about gating without asking you to write code.
Cookiebot
One of the most widely deployed consent management platforms — if a campaign has a banner at all, it is often this one.
CookieYes
Popular low-cost CMP on WordPress and hosted builders — common on down-ballot sites.
Ballot Signal + CookieHub: questions
Is the CookieHub integration available today?
Live. Built, tested and available to every customer today. You can turn this on yourself without talking to us.
What authentication does the CookieHub integration use?
n/a (client-side signal). Credentials are stored encrypted and are never rendered back into the interface after entry.
Will this create duplicate records in CookieHub?
No, assuming you leave deduplication on. We match on the lowercased-email hash first, then phone, then name plus address. On a match we update rather than create, and only the fields you have marked overwritable.
Does the consent record travel into CookieHub?
Yes. Consent timestamp, consent version, consent source URL and granted categories are included in every push, by default, and there is no configuration that strips them. That is the point of the product.
See what your own website already knows.
Book a 20-minute walkthrough. We will look at your site's current consent posture first — that part is useful whether or not you buy anything.