Ads & analytics

Ballot Signal + mParticle

Coming soon Webhook Nonpartisan API key / secret

What is mParticle?

Enterprise CDP with a first-class consent model of its own — a natural fit once the connector exists.

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

Planned: supporter records as mParticle user profiles with consent state mapped to mParticle's own consent framework, and intent signals as custom events. Today, achievable through the universal webhook plus a translation layer.

What syncs

  • User attributes
  • Custom events

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 input in mParticle and copy the key and secret.

  2. 2

    Point the Ballot Signal universal webhook at mParticle's HTTP endpoint via a translation layer.

  3. 3

    Map consent state into mParticle's consent framework so downstream forwarding respects it.

  4. 4

    Verify events in the mParticle live stream.

Why it matters

Enterprise CDP with a first-class consent model of its own — a natural fit once the connector exists.

Ballot Signal + mParticle: questions

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

API key / secret. Credentials are stored encrypted and are never rendered back into the interface after entry.

Will this create duplicate records in mParticle?

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

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