Voter data
Ballot Signal + L2
What is L2?
The most widely licensed commercial voter file. When a partnership closes, this is where 'resolve' starts to include party, vote history and district.
It sits in the Voter data category of a campaign stack. Honest about what we do not have yet.
Who uses it
Nonpartisan. Used across both parties and by nonpartisan organizations.
How the Ballot Signal + L2 integration works
Not publicly documented and not built. Matching a supporter record to a voter file record requires a commercial data agreement we do not have today. If you hold your own L2 license, export from Ballot Signal and match inside your own environment — that keeps your license intact.
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 | 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
Export identified supporters as CSV from Ballot Signal.
- 2
Match against your own licensed L2 data inside your own environment.
- 3
Do not send us voter file data to match on your behalf — we are not licensed for it.
Why it matters
The most widely licensed commercial voter file. When a partnership closes, this is where 'resolve' starts to include party, vote history and district.
Related integrations
All Voter data →TargetSmart
Deep Democratic-lane voter data and modeling — a high-value future partnership, not a current capability.
Data Trust
The Republican-lane data cooperative — the mirror of what TargetSmart anchors on the other side.
Ballot Signal + L2: questions
Is the L2 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 L2 integration use?
None — L2 is not a destination we authenticate against. See the mapping table above for what actually flows.
Will this create duplicate records in L2?
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 L2?
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 L2 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.