Integrations
Consent & privacy integrations
Signals we consume, never signals we override.
This category is inverted: these are not places we send data, they are the sources of truth we read before we do anything. Ballot Signal subscribes to your consent management platform's own events, normalizes them into a single internal consent object, and stays inert until the categories you have mapped are granted. If your CMP is silent, we treat that as denied.
Complianz
Implements the WP Consent API properly, which makes it the shortest path from 'installed' to 'provably gated'.
Cookiebot
One of the most widely deployed consent management platforms — if a campaign has a banner at all, it is often this one.
CookieHub
Lightweight CMP that shows up frequently on small campaign sites.
CookieYes
Popular low-cost CMP on WordPress and hosted builders — common on down-ballot sites.
Google Consent Mode v2
The de facto consent grammar for the web. If your Consent Mode implementation is correct, ours inherits it for free.
OneTrust
The enterprise CMP — where a state party or large advocacy organization has a privacy office, this is usually what they bought.
Osano
Common where an organization wants consent plus data-subject-request tooling in one place.
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.
Common field mapping
CMP category state → normalized internal consent object → gate. Nothing fires, and no identifier is generated, until the mapped categories read 'granted'.
See the full supporter record →Other categories
CRM & voter contact
Your campaign's system of record — where every supporter eventually lands.
Fundraising & payments
Match giving history to the visitor who never filled out the form.
Email & SMS
The channels that live or die on a defensible consent record.
Website builders & CMS
Where the tag goes. One snippet, or a native plugin.
Automation
The universal escape hatch — webhook, Zapier, CSV.
Voter data
Honest about what we do not have yet.
Ads & analytics
Server-side conversion signal — for consented supporters only.
Consent & privacy: questions
What if we do not run a consent management platform?
Ballot Signal ships its own consent banner you can use instead. It defaults every category to denied, records the choice in a first-party cookie with a version string, and gives you the same audit trail.
Which category do you require?
By default, marketing. You can additionally require statistics. We never fire on functional or strictly-necessary consent alone, because identifying a visitor is not strictly necessary to deliver a website.
What happens when a visitor changes their mind?
The CMP emits an update event, we re-read the state immediately, and we stop. A withdrawal is written to the supporter record as a consent-revoked event and propagated to your destinations as a suppression signal.
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.