Website builders & CMS
Ballot Signal + PoliEngine
What is PoliEngine?
Purpose-built campaign sites with compliance-aware defaults — a natural fit for a consent-first layer.
It sits in the Website builders & CMS category of a campaign stack. Where the tag goes. One snippet, or a native plugin.
Who uses it
Nonpartisan. Used across both parties and by nonpartisan organizations.
How the Ballot Signal + PoliEngine integration works
Install target where header scripts are permitted. Confirm with support before buying.
What syncs
- Page views
- Intent signals
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 | On the site | Notes |
|---|---|---|
| — (install) | Consent-aware script in the site header | Loads after your consent platform initializes. |
| pagesViewed | Page-intent signals reported post-consent | Nothing is reported before consent. |
| consentCategories | Read from the platform's consent state | Denied or undecided means the script stays inert. |
| utmSource / utmMedium / utmCampaign | Captured from the landing URL | Carried onto the supporter record. |
How to set it up
- 1
Confirm with PoliEngine support that your plan allows custom header scripts.
- 2
Add the Ballot Signal snippet to the site header.
- 3
Confirm a consent banner initializes first.
- 4
Test with consent denied, then granted.
Why it matters
Purpose-built campaign sites with compliance-aware defaults — a natural fit for a consent-first layer.
Related integrations
All Website builders & CMS →WordPress
WordPress powers roughly 41% of all websites per W3Techs — a share that has been declining from its mid-2025 peak, but still by far the largest single install target. There is no credible public data on CMS share among political campaign sites specifically, so we prioritize on that directional evidence rather than a made-up number.
Squarespace
Common for first-time and local candidate sites built by a volunteer over a weekend.
Wix
A large share of small-business and first-run candidate sites, especially where a family member built it.
Webflow
The default for agency-built campaign sites that want design control without a CMS to maintain.
Ballot Signal + PoliEngine: questions
Is the PoliEngine integration available today?
Coming soon. Not built yet, or built and waiting on a marketplace review we do not control. We are not going to tell you a date we cannot hold. If it matters to your buying decision, tell us and it moves up the list.
What authentication does the PoliEngine integration use?
n/a (header script, where permitted). Credentials are stored encrypted and are never rendered back into the interface after entry.
Will this create duplicate records in PoliEngine?
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 PoliEngine?
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.
When will the PoliEngine integration ship?
We are not going to give you a date we cannot hold — several of these are gated behind a marketplace review or a partnership we do not control. If it matters to your buying decision, tell us, because demand is how we prioritize.
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.