Jane App to Google Ads
Jane App bookings, reported back to Google Ads.
A physiotherapy or chiropractic clinic on Jane App needs to know which keyword filled the schedule, without sending Google anything about a patient's health. We build that line carefully.
- 10% of ad budget, $600 a month minimum
- No contracts, month to month
- Free proposal within one business day
The workflow
What connects a Jane App booking to a Google Ads bid.
The click hand off
If your booking button sends a visitor from your own site to a Jane App hosted booking page, the click identifier needs to be passed through that link, or it gets lost at the handoff. We check this first, since it quietly breaks more clinic setups than anything else, often without anyone noticing until the numbers stop making sense.
The identity match
We match a booking back to its ad click using the click identifier where the handoff preserved it, and fall back to a hashed email or phone number from the intake form once the window Google sets has passed.
Where the data enters
Jane App offers an API for approved integrations, which is the usual path for pulling a booking event out and into Google Ads' offline conversion import. What that API exposes can change, so we confirm current access with your clinic's Jane account before building, rather than assuming it matches an older setup we built elsewhere.
What never gets sent
We send Google Ads a booking happened and, if you choose, its value. We do not send a diagnosis, a treatment type, or anything that identifies why the patient came in. That distinction matters under HIPAA in the US and PHIPA in Canada.
What we check before a clinic trusts this.
First appointment attended, not just booked
A booked slot that no shows should not count as a conversion. Where your clinic tracks attendance in Jane App, we trigger on the patient actually showing up for the first visit, since a full calendar of missed appointments tells you nothing useful about your ads.
Privacy built in, not bolted on
We design the data we send before we build anything, so a compliance question does not come up after the fact. If a request would need health information to work, we tell you plainly and look for another way.
New patients separated from returning ones
A returning patient rebooking is not a new customer your ad brought in. We only count first time bookings against the click, so a loyal patient base does not inflate what your Google Ads is actually doing, since referral traffic from existing patients is a real and separate channel worth tracking on its own.
Re-tested after Jane App updates
Jane App's booking pages and integration access change on their own timetable, not ours. The safeguard is simple: a fresh batch of bookings runs through after any such change, before your clinic's reporting is allowed to lean on it.
How we build it.
01
Audit the booking hand off
We start by checking whether your booking link is actually preserving the click identifier as a visitor moves from your site to Jane App, and how your clinic currently tells new patients apart from returning ones.
02
Build and test the feed
Because nothing about a diagnosis or treatment type is allowed near this build, we test it the same way we built it: real bookings from your own schedule, run through blind, checked only for whether a plain first-visit conversion comes out the other side.
03
Hand off a plain record
Your clinic keeps a copy showing exactly what reaches Google Ads and what never does, something to pull out the moment a privacy question comes up.
Jane App and Google Ads conversions, answered.
We only send that a booking happened and, if you choose, its value. Nothing about the reason for the visit, a diagnosis, or a treatment type is ever included in what we send, regardless of how the clinic's own intake form is worded.
The actual visit, where your clinic tracks attendance. A booked slot that no shows tells Google Ads nothing useful about which keyword works.
Yes, though we set it up per clinic location if you run more than one, since booking pages and staff schedules often differ location to location, and a shared front desk booking flow needs its own separate check.
Jane App does not ask permission before changing its API or booking pages, so we do not assume anything stays the same. Bookings get run through again after every such change, and the numbers get confirmed before your clinic leans on them.
Track new patients from Jane App without touching their health data.
Tell us how patients book with your clinic today, how your booking button links to Jane App, and whether you run more than one location. We will scope the exact build, in plain language, free, within one business day.