Integrations
CRM & voter contact integrations
Your campaign's system of record — where every supporter eventually lands.
Your CRM is the system of record. Every identified supporter should end up there with the consent evidence attached, not in a spreadsheet somebody forgets to import. Ballot Signal writes a normalized supporter record into your CRM and stamps it with the consent timestamp, the consent version, and the page URL where consent was captured — so the record can defend itself later.
HubSpot
The CRM most consultants and advocacy shops already run alongside a political database — often the reporting layer leadership actually looks at.
NationBuilder
All-in-one CRM and website builder — so it is both a destination for supporter records and a place the Ballot Signal tag itself gets installed.
Salesforce
The enterprise floor for large PACs, advocacy organizations and party committees with real IT governance.
Aristotle
Long-standing compliance and data vendor for federal committees — often the system that decides whether a record is reportable.
Campaign Sidekick
Widely used for field and canvassing on the Republican side, where the identified supporter needs to become a door on a walk list.
NGP VAN / EveryAction
The dominant Democratic and progressive campaign database — if your organizers live anywhere, they live here.
i360
Anchors the Republican data lane the way NGP VAN anchors the Democratic one.
Numinar
A modern data and analytics stack on the Republican side, increasingly the system of record for campaigns that want in-house modeling.
Common field mapping
Supporter record → a person/contact object, with consent fields written to custom fields or tags, and page-intent signals written as activity, tags, or survey responses.
See the full supporter record →Other categories
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.
Consent & privacy
Signals we consume, never signals we override.
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.
CRM & voter contact: questions
Do you overwrite existing records in our CRM?
No. We match on lowercased-email hash first, then phone, then name + address. On a match we update only fields that are empty or that you have explicitly mapped as overwritable. On no match we create a new record. You choose create-only, update-only, or upsert per destination.
What happens to a supporter who later withdraws consent?
Withdrawal writes a consent-revoked event to the same record, stops all future pushes for that person, and is available on your export. We cannot delete data already inside your CRM — that stays your controller-side action, and our documentation tells you exactly which field to filter on.
Can we route different supporters to different CRMs?
Yes. Routing rules can key off page URL, UTM parameters, geography, or the intent signal that triggered the record — so a donate-page visitor and a volunteer-page visitor can land in different systems.
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.