Skip to main content
KeragonPractice and clinic software

Keragon runs your intake. Your ads still can't see who became a patient.

You built Keragon workflows so a form lands in the EHR and a booking starts intake without retyping. The ad click that started it never makes that trip, so Google Ads and Meta stop at a page view and bid blind. We carry the click ID through the same workflows and send back booked visits and new members as conversions that hold no health details.

Free30 minutesNo obligation

Keragon · what breaks

What goes wrong when Keragon sits between your ads and your EHR

  1. 01

    Google Ads shows a handful of leads. The EHR shows a full week of new patients.

    Your intake form hands its answers to Keragon in the background, often with no thank-you page for a tag to fire on. Most new patients never register as conversions, and Smart Bidding learns from the few that slipped through.

  2. 02

    The click ID dies on the form

    Google matches an offline conversion to the ad by the GCLID saved with the lead. If your Jotform or EHR intake never captured it, there's nothing on the patient record for Keragon's Upload offline conversion step to send, so a paid-for patient looks like walk-in traffic.

  3. 03

    We're paying for form fills, not members

    A direct primary care practice needs enrolled members and a pain management clinic needs attended consults. When ads optimize to the raw submission, out-of-area and existing-patient forms count the same as a new patient.

  4. 04

    Someone wired patient data straight into an ad platform

    It takes one workflow step to push form answers into Upload user data or a customer list. Keragon's BAA covers Keragon, not Google or Meta, and Google doesn't let health advertisers use Customer Match anyway, so that step buys risk and no reach.

Keragon · the fix

What changes — Keragon

  • Bidding learns from real patients

    Google Ads and Meta receive the booked visit or membership start from the EHR, so the algorithm chases the campaigns that fill your schedule.

  • Clean, minimal payloads

    Outbound events carry a click ID, a neutral event name, a timestamp and a value. No diagnosis, form answers or visit reasons ever reach an ad platform.

  • You can tell which ads produce members

    Spend lines up against new patients by campaign, so cutting a keyword or an ad set is a decision you can defend.

Keragon · architecture

What Keragon actually lets you hook into

Keragon is an automation layer with a BAA included on all plans. Nothing in its integration listings places a tag on your site or records an ad click; it moves data between the form, scheduler, EHR and ad tools you already run.

  1. 1

    App triggers from forms, schedulers and EHRs

    Documented examples include Jotform's New submission and Healthie's Appointment created and Patient created.

  2. 2

    HTTP webhook trigger

    A unique URL for any system that can send outgoing webhooks, including ones without a native Keragon connector.

  3. 3

    Google Ads actions

    Listed actions include Upload offline conversion, plus customer list and user data actions we keep switched off for health advertisers.

  4. 4

    Meta actions

    Meta Ads lists Send conversion event and Facebook Conversions lists Send lead events. Facebook Lead Ads can start a workflow on New lead.

  5. 5

    Confirm the Google upload path

    Google is moving offline conversion uploads to its Data Manager API, so we confirm Keragon's action still lands conversions in your account before relying on it.

Keragon · diagnose

Where Keragon tracking breaks, in diagnostic order

We start with what leaves the building, because a leaky workflow is a bigger problem than a missing conversion.

  1. 01

    List every workflow step that sends data to Google or Meta

    Check the mapped fields for names, conditions or form answers.

  2. 02

    Submit a test intake from an ad-tagged URL

    Open the Keragon run and confirm the click ID arrived in the trigger output.

  3. 03

    Follow it into the EHR

    Check that the click ID is stored on the patient or appointment record, not dropped at the mapping step.

  4. 04

    Check the outbound action's response

    A Keragon run marked successful still needs a matching conversion in Google Ads or Events Manager.

  5. 05

    Compare new patients to reported conversions

    Per patient, over a closed week, with existing patients excluded.

Keragon · prove

The QA evidence — Keragon

Proven on a real intake submitted through your live form, run end to end through Keragon into your EHR.

Source of truth

Your EHR or scheduler records of new patients and first visits, cross-checked against Keragon's run history

  • A test intake from an ad-tagged URL, with the click ID visible in the Keragon run output.
  • The same click ID found on the patient or appointment record in the EHR.
  • Exactly one Google Ads conversion and one Meta event per new patient, with a shared event ID for Meta.
  • Every outbound payload reviewed and confirmed free of names, conditions and form answers.
  • New patients reconciled against both ad platforms over a fully closed window.
  • Rechecked 30 days later and after any workflow or form change.

Keragon · free audit

What we check in the free audit

  • List every workflow step that sends data to Google or Meta
  • Submit a test intake from an ad-tagged URL
  • Follow it into the EHR
  • Check the outbound action's response
  • Compare new patients to reported conversions

Checked against

Your EHR or scheduler records of new patients and first visits, cross-checked against Keragon's run history

Get my free conversion tracking audit

Free30 minutesNo obligation

Keragon · when not to buy

When you don't need this on Keragon

Some practices are better off with a short conversation than a build.

  • If you don't run paid search or paid social, attribution won't add anything to your Keragon setup.
  • If nearly all new patients come from referrals or employer contracts, ad conversions won't move your numbers.
  • If your intake form already captures the click ID and a working workflow uploads it, we'll confirm it and tell you to leave it alone.
  • If your compliance team won't allow any patient-linked event to leave the EHR, settle that policy before anyone builds tracking.

Keragon · what we deliver

The event map on Keragon

  • Ad click captured

    GCLID, fbclid and UTMs stored first-party on your site and written into hidden fields on the intake form.

  • Intake submitted

    The form trigger in Keragon fires a lead signal, deduplicated against any browser tag.

  • Qualified

    New, in-area patients only. Existing patients, duplicates and vendor spam are filtered out in the workflow.

  • Appointment booked

    Sent when the EHR or scheduler trigger fires for a new patient's first visit, such as Appointment created.

  • Visit completed or membership started

    The primary conversion, sent from whichever EHR event marks it in your setup (we confirm which one exists) and valued from the visit type or membership fee you choose.

  • Excluded

    Rescheduled visits, no-shows, follow-ups and anything carrying clinical detail never become ad conversions.

Written guarantee

95%+ tracking accuracy

Measured against Your EHR or scheduler records of new patients and first visits, cross-checked against Keragon's run history. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Keragon questions, answered

Yes. Keragon lists an Upload offline conversion action for Google Ads. Google matches those uploads to the ad click by the GCLID saved with the lead, so the click ID has to be captured on your intake form first, and we test the action's field mapping in your account before relying on it.

Free · 30 min

Get your Keragon workflows reporting real patients to your ads

Free30 minutesNo obligation