Ads & analytics

Ballot Signal + Segment

Coming soon Webhook Nonpartisan Write key

What is Segment?

Where a large organization already centralizes customer data, adding a source beats adding another point-to-point integration.

It sits in the Ads & analytics category of a campaign stack. Server-side conversion signal — for consented supporters only.

Who uses it

Nonpartisan. Used across both parties and by nonpartisan organizations.

How the Ballot Signal + Segment integration works

Planned: Ballot Signal as a Segment source, emitting identify calls for supporter records and track calls for intent signals, with consent fields as traits. Today the same shape is achievable by pointing the universal webhook at Segment's HTTP tracking API.

What syncs

  • identify calls
  • track calls

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 Event Notes
firstName, lastName Server-side conversion event Left empty rather than guessed when resolution is not confident.
email Hashed identifier (SHA-256) Primary match key. Lowercased before hashing.
phone Hashed identifier (SHA-256) Present does not imply consent to be contacted on it.
addressLine1, city, state, zip Not sent Third dedupe fallback.
consentTimestamp Event parameters (non-identifying) ISO 8601, UTC.
consentVersion Event parameters (non-identifying) The language in force at the moment of consent.
consentSource Event parameters (non-identifying) The exact page URL where consent was captured.
consentCategories Event parameters (non-identifying) Normalized from your consent platform.
intentSignals Event name Donate-page, volunteer-page, issue-page and any you define.
utmSource, utmMedium, utmCampaign, referrer Event parameters Carried verbatim.
dedupeKey Match key Lowercased email hash. Match order: dedupeKey, then phone, then name + address.

How to set it up

  1. 1

    Create an HTTP API source in Segment and copy the write key.

  2. 2

    Point the Ballot Signal universal webhook at Segment's HTTP tracking endpoint, or use middleware to translate the payload.

  3. 3

    Map supporter fields to traits and intent signals to track events.

  4. 4

    Confirm your Segment consent settings do not forward to destinations the visitor declined.

  5. 5

    Verify in the Segment source debugger.

Why it matters

Where a large organization already centralizes customer data, adding a source beats adding another point-to-point integration.

Ballot Signal + Segment: questions

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

Write key. Credentials are stored encrypted and are never rendered back into the interface after entry.

Will this create duplicate records in Segment?

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

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