Consent & privacy
Ballot Signal + WP Consent API
What is 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.
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 + WP Consent API integration works
A signal we consume. The Ballot Signal WordPress plugin registers as a consenting plugin and reads the WP Consent API category state both client-side and server-side, so a page cached by your host cannot accidentally serve a consented state to an unconsented visitor. Nothing fires unless the required categories read 'allow'.
What syncs
- functional
- statistics-anonymous
- statistics
- preferences
- marketing
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
Install the WP Consent API plugin if it is not already active.
- 2
Install and activate a consent banner plugin that implements it.
- 3
Activate the Ballot Signal plugin — registration as a consenting plugin is automatic.
- 4
Choose required categories in the plugin settings. Marketing is the default.
- 5
Verify with consent denied that no request is made, then accept and verify one is.
Why it matters
The only standardized consent contract inside WordPress — and the reason our plugin can be honest about gating without asking you to write code.
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.
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.
Complianz
Implements the WP Consent API properly, which makes it the shortest path from 'installed' to 'provably gated'.
Ballot Signal + WP Consent API: questions
Is the WP Consent API 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 WP Consent API integration use?
n/a (WordPress API). Credentials are stored encrypted and are never rendered back into the interface after entry.
Will this create duplicate records in WP Consent API?
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 WP Consent API?
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.