CRM & voter contact
Ballot Signal + i360
What is i360?
Anchors the Republican data lane the way NGP VAN anchors the Democratic one.
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
Republican lane. Predominantly used by Republican and conservative 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 + i360 integration works
Not publicly documented. i360 does not publish open integration documentation; access runs through a partner relationship rather than a self-serve API. Until that relationship exists, the honest path is CSV export from Ballot Signal and import on your side using whatever list-loading process your i360 account team supports.
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
Export identified supporters from Ballot Signal as CSV, including the consent columns.
- 2
Work with your i360 account team on their supported list-import process.
- 3
Ask us to prioritize a native connector — partner demand is what moves this from partner-only to built.
Why it matters
Anchors the Republican data lane the way NGP VAN anchors the Democratic one.
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.
NGP VAN / EveryAction
The dominant Democratic and progressive campaign database — if your organizers live anywhere, they live here.
Ballot Signal + i360: questions
Is the i360 integration available today?
Partner-only. This platform does not publish open integration documentation. Access requires a commercial partnership we have not signed. CSV export is the honest path today, and we would rather say that than imply a connector exists.
What authentication does the i360 integration use?
None — i360 is not a destination we authenticate against. See the mapping table above for what actually flows.
Will this create duplicate records in i360?
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 i360?
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 i360 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.