Skip to main content
Ours PrivacyWebsite and marketing platforms

Ours Privacy took the pixels off your site. Now your ads can't tell which clicks became patients.

You signed the BAA, switched to the Ours Privacy tag manager and pulled the old tags. Then Google Ads conversions thinned out and Smart Bidding started guessing. Ours sends conversions server-side, but only for events you've allowed, mapped and published, and Google Ads only gets the ones that carry a click ID. We wire that up, with your privacy officer approving every field that leaves.

Free30 minutesNo obligation

Ours Privacy · what breaks

What goes wrong after a practice moves to Ours Privacy

  1. 01

    Google Ads only counts a fraction of our new patients

    Ours dispatches a Google Ads conversion only when the visitor carries a gclid, gbraid or wbraid and the event name matches an allowed event on that destination. Miss either and the campaigns spending most on implant, Invisalign or med spa consults look like they convert nobody, so bidding pulls budget from them.

  2. 02

    The booking happens somewhere Ours can't see

    Patients book in NexHealth, Healthie or your EHR scheduler, not on your pages. Without a source sending those appointments back, bidding learns from booking-page views instead of booked patients.

  3. 03

    A scheduler webhook quietly erased our click IDs

    Ours' docs warn that mapping a null field onto a visitor property like gclid clears the value captured at landing. One careless template and that patient's later appointments lose their ad credit.

  4. 04

    Calls from our ads land in the 'unknown' pile

    When a patient sees your ad and phones the front desk, Ours can only credit the click if the call event carries the Ours device ID. CallRail passes it through its Custom Cookie Capture plugin, but only if someone turned that on; without it, the campaigns driving your phone bookings get no credit and look like waste.

Ours Privacy · the fix

What changes — Ours Privacy

  • Every matched conversion reaches Google Ads

    Click IDs kept on the visitor, allowed events lined up with conversion actions, and Advanced Upload used where a scheduler or EHR sync delivers bookings days after they happen.

  • Bidding on patients who actually came in

    Completed appointments from your scheduler or EHR go back as the primary conversion, with no-shows kept out of the count.

  • One clean path per platform

    Leftover GA4 and Meta tags removed, Pixel and Conversions API sharing one event_id, and each change published as a version you can roll back.

Ours Privacy · architecture

What Ours Privacy actually lets you hook into

From Ours Privacy's documentation. Where the docs are silent, we test it on your account.

  1. 1

    Web SDK and Ours Tag Manager

    A script tag, npm package or no-code tag manager with click, form and custom-event triggers. Click IDs and UTMs are default visitor properties.

  2. 2

    Event allowlist and data mapping

    Events not on the allowlist are dropped before any destination. Per destination you can map properties to that platform's schema, hash or redact fields, and configuration changes only take effect once a version is published.

  3. 3

    Google Ads destination

    Proxied through Ours' servers. The default sends Website-type conversions; Advanced Upload uses Import Click, needs authentication and accepts events up to 30 days old.

  4. 4

    Meta Conversions API destination

    Server-to-server, with fbclid captured into fbc and the same event_id set on the Pixel hit and the server dispatch for deduplication.

  5. 5

    Sources for offline events

    Webhooks, CallRail and CallTrackingMetrics sources, scheduler connections for platforms such as NexHealth, Healthie and Zocdoc, and the Ingest API. Server events match on visitor ID, then external ID, email and phone.

  6. 6

    GA4, Microsoft and the consent banner

    GA4 from webhook or API events needs the separate Measurement Protocol destination. Microsoft Advertising has an offline conversions destination matched on click ID, email or phone. The CMP adds region-specific policies and Google Consent Mode guidance.

Ours Privacy · diagnose

Where Ours Privacy tracking breaks, in diagnostic order

Start with what gets filtered out, because on Ours the usual fault is a real conversion stopped on purpose rather than lost by accident.

  1. 01

    Check the allowlist and the published version

    An approved event that was never published, or never added to the Google Ads destination's allowed events, sends nothing.

  2. 02

    Confirm the click ID survives to the appointment

    Book once from an ad-tagged URL and open the visitor; then check no webhook mapping later blanked the gclid.

  3. 03

    Check the Google Ads upload type

    Website type versus Advanced Upload decides how old a conversion can be and whether conversion IDs and labels can be linked manually.

  4. 04

    Test consent on a fresh visit

    A denied ad storage signal suppresses the Google conversion entirely, so compare the banner's regional policy with what your counsel actually requires.

  5. 05

    Look for tags running outside Ours

    Ours tells you to remove existing GA4 scripts for the connected property, and a leftover Meta Pixel in a page template counts twice.

Ours Privacy · prove

The QA evidence — Ours Privacy

Run on a real booking and a real call from an ad-tagged URL on your live site, never on a staging copy.

Source of truth

Your scheduler or EHR appointment records: new-patient appointments booked and completed by date, with appointment ID and referring campaign where recorded

  • One booking from an ad-tagged URL, with the gclid confirmed on the Ours visitor and on the appointment_booked event.
  • The same appointment_id on the booked and completed events, and one conversion per appointment in Google Ads.
  • Exactly one Meta conversion per event in Events Manager, with Pixel and server hits sharing an event_id.
  • A test call stitched to its click through the call-tracking source.
  • A no-show and a reschedule confirmed absent from the bidding conversion.
  • Completed visits reconciled appointment by appointment against Google Ads and Meta over a fully closed window.
  • Repeated 30 days later and after any new published version in Ours.

Ours Privacy · free audit

What we check in the free audit

  • Check the allowlist and the published version
  • Confirm the click ID survives to the appointment
  • Check the Google Ads upload type
  • Test consent on a fresh visit
  • Look for tags running outside Ours

Checked against

Your scheduler or EHR appointment records: new-patient appointments booked and completed by date, with appointment ID and referring campaign where recorded

Get my free conversion tracking audit

Free30 minutesNo obligation

Ours Privacy · when not to buy

When you don't need this on Ours Privacy

Some practices on Ours are a settings check away from clean data.

  • If Google Ads conversions already match your new-patient bookings within a few percent, leave the setup alone.
  • If you don't run Google, Meta or Microsoft ads, there's no bidding to feed and nothing here for us to fix.
  • If you're mid-implementation with Ours and the scheduler connection isn't built yet, finish that first, then have us check it against your appointments.
  • If the only problem is one event missing from the allowlist, adding and publishing it is a five-minute job you can do yourself.

Ours Privacy · what we deliver

The event map on Ours Privacy

  • Ad landing captured

    gclid, fbclid and msclkid stored on the Ours visitor at arrival, with UTM values kept and nothing overwritten by later webhooks.

  • Lead captured

    Booking requests and form submissions logged as lead_captured, a neutral name that never names a condition, and kept apart from real bookings.

  • Ad call answered

    CallRail calls received through the Ours webhook source with ours_device_id attached, so they stitch to the click. On CallTrackingMetrics we confirm what its webhook can carry before counting on it.

  • Appointment booked

    From your scheduler's webhook, with the appointment_id and real booking time, sent to its own conversion action.

  • Appointment completed

    Same appointment_id; the conversion Google and Meta should bid on.

  • Excluded on purpose

    No-shows, reschedules (they reuse the original ID), portal logins, existing-patient follow-ups and anything not on the approved allowlist.

Written guarantee

95%+ tracking accuracy

Measured against Your scheduler or EHR appointment records: new-patient appointments booked and completed by date, with appointment ID and referring campaign where recorded. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Ours Privacy questions, answered

Yes. Events are proxied through Ours' servers, so Google never sees the visitor's browser or IP. It only sends events that carry a gclid, gbraid or wbraid and match an allowed event name.

Free · 30 min

Get patients, not page views, back into your ad accounts

Free30 minutesNo obligation