Website builders & CMS

Ballot Signal + CampaignPartner

Coming soon Embed / plugin Nonpartisan n/a (header script, where permitted)

What is CampaignPartner?

Long-running campaign website provider with a substantial down-ballot install base.

It sits in the Website builders & CMS category of a campaign stack. Where the tag goes. One snippet, or a native plugin.

Who uses it

Nonpartisan. Used across both parties and by nonpartisan organizations.

How the Ballot Signal + CampaignPartner integration works

Install target where header scripts are permitted. Confirm with support before buying.

What syncs

  • Page views
  • Intent signals

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 On the site Notes
— (install) Consent-aware script in the site header Loads after your consent platform initializes.
pagesViewed Page-intent signals reported post-consent Nothing is reported before consent.
consentCategories Read from the platform's consent state Denied or undecided means the script stays inert.
utmSource / utmMedium / utmCampaign Captured from the landing URL Carried onto the supporter record.

How to set it up

  1. 1

    Confirm custom header scripts are permitted on your plan.

  2. 2

    Add the Ballot Signal snippet to the site header.

  3. 3

    Confirm a consent banner initializes first.

  4. 4

    Test with consent denied, then granted.

Why it matters

Long-running campaign website provider with a substantial down-ballot install base.

Ballot Signal + CampaignPartner: questions

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

n/a (header script, where permitted). Credentials are stored encrypted and are never rendered back into the interface after entry.

Will this create duplicate records in CampaignPartner?

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

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