CRM & voter contact
Ballot Signal + NGP VAN / EveryAction
What is NGP VAN / EveryAction?
The dominant Democratic and progressive campaign database — if your organizers live anywhere, they live here.
It sits in the CRM & voter contact category of a campaign stack. Your campaign's system of record — where every supporter eventually lands.
Who uses it
Democratic lane. Predominantly used by Democratic and progressive campaigns and organizations. Ballot Signal itself is nonpartisan — we build to whichever platforms our customers actually run, and the directory is filterable by lane so you can see only what applies to you.
How the Ballot Signal + NGP VAN / EveryAction integration works
The supporter record maps to a VAN People record: name, email, phone and address go to the standard person fields; the consent timestamp, consent version and consent source URL are written as Survey Responses or as a custom field so the evidence lives beside the person rather than in a spreadsheet. Page-intent signals (donate page, volunteer page, issue page) map to Activist Codes, and the identification event itself is written to Contact History as a non-contact activity so organizers can see where the record came from.
What syncs
- People
- Contact History / Canvass Responses
- Survey Questions & Responses
- Activist Codes
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 | CRM object | Notes |
|---|---|---|
| firstName, lastName | Person / contact record | Left empty rather than guessed when resolution is not confident. |
| Person / contact record — primary identifier | Primary match key. Lowercased before hashing. | |
| phone | Person / contact record — phone field | Present does not imply consent to be contacted on it. |
| addressLine1, city, state, zip | Person / contact record — address fields | Third dedupe fallback. |
| consentTimestamp | Custom fields or survey responses | ISO 8601, UTC. |
| consentVersion | Custom fields or survey responses | The language in force at the moment of consent. |
| consentSource | Custom fields or survey responses | The exact page URL where consent was captured. |
| consentCategories | Custom fields or survey responses | Normalized from your consent platform. |
| intentSignals | Tags or activist codes | Donate-page, volunteer-page, issue-page and any you define. |
| utmSource, utmMedium, utmCampaign, referrer | Custom fields or survey responses or source fields | Carried verbatim. |
| dedupeKey | Match key | Lowercased email hash. Match order: dedupeKey, then phone, then name + address. |
How to set it up
- 1
Inside VAN, open the Administrative Menu and choose API Integrations.
- 2
Click 'Request an API Key'. This request must come from you — the client — because a vendor cannot request a production key on a client's behalf.
- 3
Select Ballot Signal from the vendor dropdown if it appears, or file a support ticket naming Ballot Signal as the vendor.
- 4
When the key is issued, paste the Application Name and API Key into Ballot Signal under Destinations → NGP VAN.
- 5
Map your consent fields to the Survey Questions or custom fields you want them written to.
- 6
Map each page-intent signal to an Activist Code, then run a test push and confirm the record in VAN.
Why it matters
The dominant Democratic and progressive campaign database — if your organizers live anywhere, they live here.
Related integrations
All CRM & voter contact →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.
HubSpot
The CRM most consultants and advocacy shops already run alongside a political database — often the reporting layer leadership actually looks at.
Salesforce
The enterprise floor for large PACs, advocacy organizations and party committees with real IT governance.
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.
Ballot Signal + NGP VAN / EveryAction: questions
Is the NGP VAN / EveryAction 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 NGP VAN / EveryAction integration use?
Application Name + API Key (HTTP Basic). Credentials are stored encrypted and are never rendered back into the interface after entry.
Will this create duplicate records in NGP VAN / EveryAction?
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 NGP VAN / EveryAction?
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 NGP VAN / EveryAction 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.