The problem it solves
Healthcare marketing teams need conversion data to optimize ad campaigns, but standard pixel-based tracking sends patient data to ad platforms in ways that conflict with HIPAA. Without a compliant layer in between, teams either fly blind on performance or take on compliance risk to measure it.
What's included
- Webhook-based event forwarding from Healthie into Ours Privacy, supporting any Healthie event
- Enriched payloads for Appointment events (booked, completed, canceled)
- PHI filtering and anonymization before data reaches any destination platform
- Server-side connections to Google Ads, Meta, Google Analytics, GTM, GA4, and other ad/analytics tools
How it works
Once connected, Healthie sends events, like an appointment being booked or completed, to Ours Privacy over a webhook. Ours Privacy can work with any Healthie event, and fetches additional payload details specifically for Appointment events. Before any data leaves its platform, Ours Privacy filters or anonymizes PHI, then routes the resulting conversion data through secure, server-side connections to the ad and analytics platforms a team has configured, such as Google Ads, Meta, or Google Analytics.
Ours Privacy connects to Healthie via webhooks and forwards conversion events, such as appointments booked or completed, into its HIPAA-compliant customer data platform. It's for healthcare marketing and growth teams who want to send campaign performance data to tools like Google Ads, Meta, and Google Analytics without exposing PHI. Ours Privacy filters or anonymizes patient data before it reaches any ad or analytics platform, then routes the cleaned event data through server-side connections to each destination. Ours Privacy is a separate company from Healthie with its own security certifications and BAA, so compliance questions about its specific safeguards go to Ours Privacy directly.
