CRM & voter contact

Ballot Signal + Aristotle

Coming soon Partner-only Nonpartisan

What is Aristotle?

Long-standing compliance and data vendor for federal committees — often the system that decides whether a record is reportable.

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

Nonpartisan. Used across both parties and by nonpartisan organizations.

How the Ballot Signal + Aristotle integration works

Not publicly documented as a self-serve API. Aristotle also sits in the setup path for federal committees using WinRed, so a campaign may encounter it as a compliance and routing layer rather than as a destination. CSV export is the supported path today.

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 field mapping
Supporter record CRM object Notes
firstName, lastName Person / contact record Left empty rather than guessed when resolution is not confident.
email 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. 1

    Export identified supporters from Ballot Signal as CSV, including consent columns.

  2. 2

    Coordinate the import with your Aristotle account team.

  3. 3

    If you are a federal committee routing WinRed through Aristotle, confirm which system should own the supporter record before you configure either.

Why it matters

Long-standing compliance and data vendor for federal committees — often the system that decides whether a record is reportable.

Ballot Signal + Aristotle: questions

Is the Aristotle 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 Aristotle integration use?

None — Aristotle is not a destination we authenticate against. See the mapping table above for what actually flows.

Will this create duplicate records in Aristotle?

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 Aristotle?

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 Aristotle 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.