Consent & privacy

Ballot Signal + Osano

Live Native — API key Nonpartisan n/a (client-side signal)

What is Osano?

Common where an organization wants consent plus data-subject-request tooling in one place.

It sits in the Consent & privacy category of a campaign stack. Signals we consume, never signals we override.

Who uses it

Nonpartisan. Used across both parties and by nonpartisan organizations.

How the Ballot Signal + Osano integration works

A signal we consume. Ballot Signal subscribes to Osano consent events and normalizes MARKETING and ANALYTICS categories into our internal consent object.

What syncs

  • Consent categories
  • Consent change 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 Consent signal Notes
— (inbound) Consent category state Read from this platform, not written to it.
consentCategories Normalized internal consent object Their category names mapped onto ours.
consentTimestamp Captured at the moment of the affirmative act Stored on every supporter record produced afterwards.
consentVersion Your configured policy version string A version bump re-asks the visitor.
consentSource Page URL where the consent event fired Exact URL, not just the domain.

How to set it up

  1. 1

    Ensure the Osano script loads before the Ballot Signal snippet.

  2. 2

    Classify the Ballot Signal snippet under MARKETING in Osano.

  3. 3

    Install the snippet.

  4. 4

    Test decline, accept, and withdrawal.

Why it matters

Common where an organization wants consent plus data-subject-request tooling in one place.

Ballot Signal + Osano: questions

Is the Osano integration available today?

Live. Built, tested and available to every customer today. You can turn this on yourself without talking to us.

What authentication does the Osano integration use?

n/a (client-side signal). Credentials are stored encrypted and are never rendered back into the interface after entry.

Will this create duplicate records in Osano?

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

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.

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.