Platform Updates: Global Consent Analytics, Zendesk, C# SDK, and Translations

Healthcare marketing teams need visibility into consent patterns, flexible ways to route data to support tools, and server-side SDKs that match their stack. They also need to reach visitors in their preferred language. This release adds analytics to the Global Consent Center, a new Zendesk destination, a C# SDK, and automatic translations based on visitor language.

Here's what's new:

Global Consent Center: See the Percentage of Your Events by Consent

The Global Consent Center centralizes consent rules so you can control dispatch across destinations without configuring consent logic in every mapper. Until now, understanding how much of your event volume was covered by those rules meant piecing together data elsewhere. We've added analytics directly in the Global Consent Center so you can see what share of your events fall under each consent category.

What's new:

• Event percentage by consent - see the percentage of your events that match each Global Consent Center category

• Visibility alongside consent rules - analytics live in the same place you configure category-based rules and destination assignments

• Complements the Consent Analytics Center - this adds event-level visibility on top of the existing consent analytics you already use

Why this matters:

You can now confirm that your consent rules are applied to the right share of traffic without leaving the Global Consent Center. Seeing the percentage of events per category helps you tune rules and spot gaps, and keeps consent analytics in one place alongside your category configuration.

New Destination: Zendesk

Support teams need tickets created from the same events and identities you already track, without building custom pipelines. We've added a Zendesk destination so you can create support tickets in Zendesk directly from Ours Privacy.

What it does:

• Create tickets from events - create Zendesk tickets based on events, user actions, or conditions you configure in Ours Privacy

• Map to ticket fields - map event data to subject, description, priority, type, and tags

• Requester matching - associate tickets with existing requesters or create new ones based on email

Why this matters:

You can automate ticket creation from key events (e.g. errors, feedback, high-value actions) while keeping event and identity data in one pipeline. The integration is designed to send data to Zendesk; ensure you have the right safeguards and agreements in place before enabling it.

Zendesk setup and requirements are documented here.

C# SDK: Server-Side Integration for .NET

Teams running .NET or C# backends need a first-party way to send events to Ours Privacy without hand-rolling HTTP calls. We've released a C# SDK available on NuGet so you can track events from your server in a few lines of code.

What's new:

• NuGet package -

• Simple event tracking - initialize the client and send events with typed parameters (e.g. event name, token, properties)

• Fits existing server-side patterns - use the same track-and-identify model as our other server SDKs

Why this matters:

.NET and C# teams can integrate Ours Privacy without maintaining custom API clients. The SDK follows the same patterns as our Go, Node, Python, and other server SDKs, so switching stacks or adding another service is straightforward.

Installation and usage are in the C# SDK docs.

Translations: Automatically Respect navigator.language

Consent and marketing experiences perform better when they match the visitor's language. We've added support for automatic translation based on navigator.language: when the visitor's browser language is not English, the experience can automatically translate to that language.

What's new:

• Respect navigator.language - the system uses the visitor's browser language setting to decide when to translate

• Automatic translation for non-English visitors - when the detected language is not English, content is translated to that language without extra configuration

• Consistent experience - consent and other customer-facing content can stay in sync with the visitor's preferred language

Why this matters:

Teams serving global or multilingual audiences can present consent and marketing content in the visitor's language by default. That typically improves comprehension and consent rates and aligns with expectations for localized, compliant experiences.

What's Next

These updates extend what you can do with the Global Consent Center, support (Zendesk), server-side tracking (C# SDK), and localization (translations). We're continuing to add analytics, destinations, SDKs, and tooling so you can run compliant, data-driven marketing and support from a single platform.

For setup and technical details, see our documentation.

Ready to see these updates in action? Book a demo to learn how we're making healthcare marketing compliance easier.