Conversion tracking for Cedar
Your Google Ads account shows clicks, your Cedar dashboard shows payments, and nothing in between says which ads brought a new patient to your urgent care or cancer center. Cedar steps in after the visit, with a text or email bill on a pay subdomain of your health system or inside MyChart, documents no API, webhooks or ad tags, and a pixel on a page that shows balances is a compliance exposure anyway. So we measure around it: the booking on your own site, matched to the click, then paid first visits from your billing records.
Free30 minutesNo obligation
Cedar · what breaks
What goes wrong with Cedar
- 01
Ads report clicks, Cedar reports payments, nobody reports visits
Google and Meta see a tap. Cedar sees a bill paid weeks later from a text link. The appointment in between is counted by neither, so smart bidding learns from nothing.
- 02
The pay subdomain is Cedar's build, not yours
Patients pay on something like pay.yourhealthsystem.org, but the page is served from Cedar's code. You can't add a tag there, and since it shows balances, you shouldn't want to.
- 03
Pre-visit payments and old balances look identical
Cedar lists pre-visit payments beside post-visit billing. A new patient's copay and a six-month-old claim balance are both 'a payment', and counting them the same inflates return on ad spend.
- 04
Payment plans count once as revenue, then again every month
Cedar's Auto-Pay and Promise-to-Pay plans create a stream of installments. Treat each as a conversion and one new patient looks like twelve.
Cedar · the fix
What changes — Cedar
The booking becomes the conversion
Bookings on your own domain, matched to the click that produced them, feed Google Ads and Meta.
Paid first visits close the loop from your records
Billed first visits from your EHR export, limited to the fields your compliance lead approves.
Installments, refunds and old balances stay out
First payment on a first visit counts once; everything else is excluded from acquisition reporting.
Cedar · architecture
What Cedar actually lets you do
From Cedar's own product pages, its 2020 Epic App Orchard press release and the Stripe customer story. Anything undocumented is listed as a check.
- 1
Text, email and paper outreach to a white-labeled site
Cedar's product page lists automated email and SMS, including abandoned-payment reminders; the Stripe story says those messages send patients to the provider's white-labeled site. The two help centers we checked sit on a pay subdomain of the health system and load from cdn.cedar.com.
- 2
Billing inside MyChart
Cedar's 2020 press release puts Cedar Pay in the Epic App Orchard, embedded in MyChart with single sign-on. Payments made there never touch a page you control.
- 3
Cedar Pre check-in
Cedar's blog describes it: confirm the appointment, verify by date of birth, add contact details and insurance, settle upcoming bills before arrival.
- 4
EHR integrations, method unstated
Cedar's implementation page names Epic, athenahealth and Oracle Health EMRs and 'a variety of integration methods' without listing any; nothing public mentions exports, SFTP or an API. We confirm what your revenue-cycle team can pull.
- 5
No documented API, webhooks, Zapier or ad tags
Nothing public describes an outbound hook, a Google Analytics connection or a Pixel setting on the patient site. The closed loop runs from your systems.
Cedar · diagnose
Where Cedar tracking breaks, in diagnostic order
Start upstream: with Cedar the fault is rarely the payment page. It is that the booking never carried a click ID.
- 01
Check whether a click ID survives to the appointment
One test appointment from a tagged ad URL through your scheduler or call center, then look for the GCLID on the record. On most Cedar health systems it isn't there.
- 02
Find any tag loading on the pay subdomain or MyChart
A Pixel here is a compliance exposure, not a tracking win. Removal comes first.
- 03
Separate pre-visit payments from post-visit balances
One month of Cedar payments, each labeled first visit, follow-up, installment or prior balance.
- 04
Compare first visits with what the ad platforms recorded
Per encounter, over a closed month, by location and service line.
- 05
Check how Cedar Pre completions are counted
A completed check-in must not be double-counted with the original appointment request.
Cedar · prove
The QA evidence — Cedar
Run on real bookings through your live site and real encounters in your EHR.
Source of truth
Your EHR encounter data and billing export — first visits completed and first payments received by date, location and service line, with Cedar plan installments flagged
- One test appointment booked from a tagged ad URL, with the GCLID visible on the scheduling record before Cedar's first message goes out.
- Exactly one booking event per appointment in Google Ads and Meta, with a shared event ID.
- A written field list for offline uploads, signed off by your privacy officer.
- First visits reconciled per encounter against each ad platform over a closed month.
- A no-show first visit reversed; a Cedar plan installment confirmed absent.
- No tag detected on the pay subdomain or in MyChart.
- Repeated 30 days later and whenever your scheduler, EHR export or Cedar outreach settings change.
Cedar · free audit
What we check in the free audit
- Check whether a click ID survives to the appointment
- Find any tag loading on the pay subdomain or MyChart
- Separate pre-visit payments from post-visit balances
- Compare first visits with what the ad platforms recorded
- Check how Cedar Pre completions are counted
Checked against
Your EHR encounter data and billing export — first visits completed and first payments received by date, location and service line, with Cedar plan installments flagged
Free30 minutesNo obligation
Cedar · when not to buy
When you don't need this on Cedar
Cedar is a billing tool, and sometimes what it already tells you is enough.
- If you run ads on one platform and your scheduler already pushes confirmed appointments to it with a click ID attached, the Cedar side adds nothing yet; skip the offline loop.
- If almost every Cedar payment is an existing patient on an Auto-Pay or Promise-to-Pay plan, collections reporting tells you more than ad attribution ever will.
- If your compliance team won't approve any upload of encounter-derived data, stop at the booking event on your own site. That alone fixes most of the bidding.
- If the only problem is a stray pixel someone added to your pay subdomain, pull it. That is a ten-minute change your web team can make without us.
Cedar · what we deliver
The event map around Cedar
Appointment request
Form, scheduler or call on your site, with the Google and Meta click IDs stored against the request.
Appointment confirmed
From your scheduling system, with location and service line (urgent care, oncology consult, imaging) attached.
Cedar Pre check-in completed
Where you run Cedar Pre, a completed pre-registration is the qualified step, from your own check-in records.
First visit completed
The conversion. Sourced from EHR encounter data, never from the Cedar payment page.
First payment received
The money event, one per new patient from your billing export, whatever method Cedar collected it by: card, ACH, Apple Pay or Google Pay.
Installments, refunds and prior balances
Logged for finance, excluded from every ad platform. A no-show first visit is reversed where allowed.
FAQ
Cedar questions, answered
No. The page is served by Cedar on your pay subdomain or inside MyChart, Cedar documents no tag setting for it, and it shows balances that must not reach an ad platform.
Cedar's public material describes no API, webhooks, Zapier or ad-platform integration. Paid-visit data comes from your EHR or billing export, matched to a click ID stored at booking.
The two never meet. The click lands on your site, the booking happens in your scheduler, and Cedar bills weeks later. Without a click ID on the booking, nothing matches.
Only for a new patient's first visit, and only once. A copay before a follow-up or a plan installment is not acquisition and skews bidding if counted.
It can be, so the field list is approved by your privacy officer first and visit details never leave your systems. Without approval, we stop at the booking event on your own domain.
More on Cedar
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Cedar, and what their bookings feed
- AscentStudents finance with Ascent, but Google Ads and Meta stop counting at the Apply button
- ArryvedYour ads send people to order on Arryved. Your ad accounts never hear about it.
- GoodLeapGoodLeap funds the job at the kitchen table. Your ads only ever saw the form fill.
- Acorn FinanceYour homeowner picked a lender on Acorn Finance. Google Ads never found out.
- Square InvoicesSquare says the invoice is paid. Google Ads has no idea which ad brought that client.
- Prosper Healthcare LendingPatients finance surgery through Prosper. Your ads only see the consult form.
- Rectangle HealthPatients pay through Rectangle Health. Your ads never find out.
- TruemedYour HSA/FSA ads bring members in. Truemed can't tell you which ones.
