Email & SMS
Ballot Signal + Klaviyo
What is Klaviyo?
Increasingly the email and SMS platform of choice for advocacy organizations that run like consumer brands.
It sits in the Email & SMS category of a campaign stack. The channels that live or die on a defensible consent record.
Who uses it
Nonpartisan. Used across both parties and by nonpartisan organizations.
How the Ballot Signal + Klaviyo integration works
The supporter record maps to a Klaviyo profile, with consent fields written as profile properties and page-intent signals sent as events against a custom metric so they appear in the profile activity feed and can drive flows. Klaviyo's API is JSON:API, and OAuth2 with PKCE is required for a listing in their Integration Directory — private-key partner auth is being phased out. We are building against OAuth, and the listing itself is gated behind their tech partner program, so this stays 'coming soon' until it is genuinely live.
What syncs
- Profiles
- Lists
- Metrics / Events
- Profile properties
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 | Messaging object | Notes |
|---|---|---|
| firstName, lastName | Subscriber / profile | Left empty rather than guessed when resolution is not confident. |
| Subscriber / profile — primary identifier | Primary match key. Lowercased before hashing. | |
| phone | Subscriber / profile — phone field | Included only when SMS-specific consent is present. |
| addressLine1, city, state, zip | Subscriber / profile — address fields | Third dedupe fallback. |
| consentTimestamp | Custom fields or merge fields | ISO 8601, UTC. |
| consentVersion | Custom fields or merge fields | The language in force at the moment of consent. |
| consentSource | Custom fields or merge fields | The exact page URL where consent was captured. |
| consentCategories | Custom fields or merge fields | Normalized from your consent platform. |
| intentSignals | Tags, lists or segments | Donate-page, volunteer-page, issue-page and any you define. |
| utmSource, utmMedium, utmCampaign, referrer | Custom fields or merge fields 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
While native OAuth is in build, connect Klaviyo through Zapier or the universal webhook.
- 2
Create profile properties for consent timestamp, consent version and consent source URL.
- 3
Map supporter fields to profile properties and page-intent signals to a custom metric.
- 4
Build your flow off the custom metric rather than off list membership, so a re-identified supporter does not re-enter the flow.
- 5
When the native connector ships, reconnect via OAuth — your property mapping carries over.
Why it matters
Increasingly the email and SMS platform of choice for advocacy organizations that run like consumer brands.
Related integrations
All Email & SMS →Mailchimp
Still the default email tool for local and county campaigns that have not bought a political-specific platform yet.
ActiveCampaign
Deep automation for small teams — the tag that arrives from us can start a whole nurture sequence without staff touching it.
EZ Texting
Low-cost texting many local campaigns already have a login for.
Tatango
Heavy political and nonprofit use, and strict about opt-in — which is exactly why a real consent record is the thing that makes a list usable here.
Ballot Signal + Klaviyo: questions
Is the Klaviyo 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 Klaviyo integration use?
OAuth2 + PKCE. Credentials are stored encrypted and are never rendered back into the interface after entry.
Will this create duplicate records in Klaviyo?
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 Klaviyo?
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.
Does connecting Klaviyo make a phone number legal to text?
No. Nothing does. We capture and preserve the consent evidence in the form platforms and carriers expect, so the consent you actually collected is provable. If you did not collect express written consent to send automated texts, we will not manufacture one. Read the TCPA page first.
When will the Klaviyo 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.