Keragon
Connect Keragon to Ours Privacy to send conversion events from CRMs, EHRs, scheduling, and intake tools into your event pipeline using the Ingest API.
Keragon Integration
Use this page to send events into Ours Privacy from Keragon, a HIPAA-compliant workflow-automation platform that connects 400+ healthcare tools — CRMs, EHRs, scheduling systems, and intake platforms.
Keragon pushes events to the Ours Privacy Ingest API, so you can attribute conversions that happen across your healthcare tech stack without adding tracking code to each tool.
How It Works
Keragon runs automations that react to activity in your connected tools — a booking in your scheduling system, a completed intake form, a status change in your CRM. You add a step to a Keragon workflow that forwards that activity to Ours Privacy, where it flows through your mappings and on to your configured destinations.
Because events are sent server-to-server, this works for backend and offline activity that never touches the browser.
Setup Steps
1. Add an Ingest API Source in Ours Privacy
- Go to Sources > Add Source.
- Select the Ingest API source.
- Copy the API key. You'll use it to authenticate requests from Keragon.
2. Add an Ours Privacy Step in Keragon
- In Keragon, open the workflow you want to track.
- Add a step that sends a request to the Ours Privacy Ingest API.
- Use the
/api/v1/trackendpoint to record an event, or/api/v1/identifyto set visitor properties without firing an event. - Paste your API key as the
token, and map the trigger data from your healthcare tool into the event name and properties.
3. Identify the Visitor
Include one of these identifiers so the event is associated with the right person:
email— the patient or lead's email address.externalId— a custom identifier you use to group a visitor's activity.userId— the Ours Visitor ID from your web properties.
Use the same identifier across your web and Keragon workflows so backend events stitch to the same visitor as their web sessions.
Test Your Integration
Use a Test Mode API Key while you build. Events sent with a Test Mode key appear in your Recent Events Dashboard for review but are not dispatched to destinations. Once the events look correct, swap in your live API key to start dispatching.
Next Steps
- Ingest API Integration — full reference for the
trackandidentifyendpoints, backfilling, and key rotation. - Webhooks — other ways to send backend and operational events into Ours Privacy.
- Tracking and Debugging Events — confirm events are arriving as expected.
If you have questions or run into issues, contact support@oursprivacy.com.
How is this guide?

