Email & SMS
Ballot Signal + GetThru (ThruText)
What is GetThru (ThruText)?
Widely used peer-to-peer texting for progressive and nonpartisan organizing programs.
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 + GetThru (ThruText) integration works
Supporter records reach GetThru as a contact list import, with consent columns included, or through the universal webhook. Only records carrying SMS consent are included.
What syncs
- Contacts
- Campaigns
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
Confirm SMS-specific consent language on the capture page.
- 2
Export identified supporters with phone numbers as CSV including consent columns.
- 3
Upload the list to the GetThru campaign that will send it.
- 4
Retain the consent export for the life of the list.
- 5
Test with a small batch before a full send.
Why it matters
Widely used peer-to-peer texting for progressive and nonpartisan organizing programs.
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 + GetThru (ThruText): questions
Is the GetThru (ThruText) integration available today?
Via webhook. Not a native connector. This works today through our signed universal webhook, and someone on your side (or your consultant) wires up the endpoint. Full supporter record, full consent record, no UI.
What authentication does the GetThru (ThruText) integration use?
API key. Credentials are stored encrypted and are never rendered back into the interface after entry.
Will this create duplicate records in GetThru (ThruText)?
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 GetThru (ThruText)?
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 GetThru (ThruText) 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.
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.