Voter data

Ballot Signal + TargetSmart

Partner-only Partner-only Democratic lane

What is TargetSmart?

Deep Democratic-lane voter data and modeling — a high-value future partnership, not a current capability.

It sits in the Voter data category of a campaign stack. Honest about what we do not have yet.

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 + TargetSmart integration works

Not publicly documented and not built. Voter file matching requires a data partnership that does not exist yet. Bring-your-own-license matching on your side is the supported path.

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 Status Notes
Full supporter record CSV export you match on your side Under your own data license, in your own environment.
dedupeKey Your join key Lowercased email hash.
— (party, vote history, district) Not provided Requires a data partnership we have not signed.

How to set it up

  1. 1

    Export identified supporters as CSV from Ballot Signal.

  2. 2

    Match against your own licensed TargetSmart data in your environment.

  3. 3

    Tell us if a native partnership would change your buying decision.

Why it matters

Deep Democratic-lane voter data and modeling — a high-value future partnership, not a current capability.

Ballot Signal + TargetSmart: questions

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

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

Will this create duplicate records in TargetSmart?

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

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