Loading
Keep taking payments in Stripe. Hippo counts the payments you choose as conversions for the campaigns that brought each patient, and cleans each one before sending it to Google Ads and Meta (Facebook). You keep one record of which campaigns bring paying patients and which bring bookings, calls and forms, whoever runs your ads.
No annual contracts.
Transparent pricing.
We set it up for you.
Stripe publishes no statement on whether it signs a BAA, and its terms bar using Stripe Billing, Stripe Invoicing and three other Stripe services in connection with protected health information (as of 10/12/26).
Carve-out
HIPAA's administrative simplification rules do not apply(opens in a new tab) to a financial institution, or a company processing payments for one, with respect to those activities. What your checkout and confirmation page tags send Google and Meta about the purchase is a separate flow, under their rules.
Health information
Under HIPAA, information about a person's payment for health care(opens in a new tab) is health information, and Stripe product names and descriptions are meant for patients to see. "Semaglutide consult" gives the treatment away, so keep clinical detail out of product names, descriptions, metadata, receipts and customer fields.
Enhanced conversions
A success page that greets the patient by name puts that name on the page, and with enhanced conversions on, a Google tag there may detect it and upload it(opens in a new tab).
We take the Google tag and the Meta Pixel off your pages, your confirmation page included, and install Hippo on a subdomain of your domain. We add Hippo's webhook endpoint in your Stripe account with whoever administers it.
A patient who clicked your ad visits your site, and Hippo records the visit and the campaign. When they pay, Stripe notifies Hippo, and Hippo ties the payment to that campaign.
It passes on only the payments you choose to count, each under a name that implies no condition, treatment or service, whatever the product is called in Stripe.
Hippo sends it from its server and keeps a record of the payment by the campaign that produced it. Whoever runs your ads sees the payment conversions arrive in Google Ads and in Meta's Events Manager.
During setup we look for anything already sending your Stripe payments to Google Ads or Meta, such as Meta's own app in your Stripe account, and switch it off, so it and Hippo do not both report the same payment.
Sent
Hippo sends Google Ads and Meta a conversion under a neutral name for the payments you choose to count, from its own server. On your pages, Hippo waits for consent where it is required.
Excluded
Names, emails, phone numbers, dates of birth and IP addresses. For a payment, the card details, billing and shipping addresses, Stripe customer ID, product, plan and price names, descriptions, metadata and URL paths are left out too.
Held
A Stripe event Hippo doesn't recognize stays in Hippo, so a new kind of event can't start sending to Google Ads or Meta on its own.
Kept
Hippo stores what it records in its own storage under the BAA it signs with every customer, with a log of what Hippo sent Google Ads and Meta and what it removed first.
Hippo ties the payments Stripe reports to the campaigns that brought your patients, beside your bookings, calls and forms, in a record you own, whatever Google Ads and Meta do with the conversion.
An independent record of results in an account you own. If you change agencies, it stays with you.
Calls that start from an ad are counted as conversions alongside forms and bookings.
A log of what Hippo sent Google Ads and Meta and what it removed first.
Hippo works with the ad platforms and website tools your practice already uses.
$99/month
Month to month.
Start now, no demo call1,000 visitors/month$199/month
Month to month.
Start now, no demo call2,000 visitors/month$299/month
Month to month.
Start now, no demo call10,000 visitors/monthServer-side conversion tracking under a BAA, at a price a practice can actually pay.
Stripe publishes no statement on whether it signs a BAA. Its terms bar using Stripe Billing, Stripe Invoicing, Stripe Tax, Stripe Revenue Recognition and the Stripe Data Pipeline(opens in a new tab) in connection with protected health information, and they bar giving Stripe protected health information as Third Party Data(opens in a new tab). The BAA you sign with Hippo covers Hippo, and payment processing is a separate carve-out. Whether Stripe falls under that carve-out is a question for your attorney. Hippo cleans the payments you count before it sends Google Ads and Meta a conversion.
The carve-out is narrower than that. HIPAA's administrative simplification rules do not apply to a financial institution, or to a company processing payments for one, with respect to those activities, and under HHS guidance a financial institution processing card payments for health care needs no BAA(opens in a new tab). What the tags on your checkout and confirmation pages send Google and Meta about the purchase is a separate flow. Meta's terms(opens in a new tab) bar data that includes or is based on health information, and Google's data collection policy bars sending personally identifiable information(opens in a new tab) to Google through conversion tracking tags. We take those tags off, and Hippo sends a conversion under a neutral name instead.
Clinical detail. Keep it out of product names, descriptions, metadata, receipts and customer fields. The terms Stripe publishes bar using Stripe Billing and Stripe Invoicing in connection with protected health information. Stripe product names and descriptions are meant for patients to see(opens in a new tab). Stripe creates a receipt for each successful payment and generates invoices automatically for subscriptions, and on card payments a statement descriptor(opens in a new tab) suffix you set can print on the patient's bank statement.
Hippo records the visit and the campaign on your pages. When the patient pays on the Stripe page, Stripe notifies Hippo, and Hippo ties the payment to the campaign that brought the patient and sends Google Ads and Meta a conversion under a neutral name. A pixel on your thank-you page counts only the patients who land on it, and a patient can pay without reaching that page(opens in a new tab).
No. We take the Google tag and the Meta Pixel off your pages, your confirmation page included, and Hippo sends conversions from its own server. A success page that greets the patient by name(opens in a new tab) puts that name where a Google tag with enhanced conversions on may detect it and upload it, and in enhanced conversions Google counts purchases of medical services(opens in a new tab) as health information. Meta's rules cover the product IDs, content names and URL parameters(opens in a new tab) sent with an event.
From Hippo, a conversion for the payments you choose to count, each under a name that implies no condition, treatment or service, as Meta's terms require(opens in a new tab) of event names. The event Stripe sends Hippo for a completed checkout can carry the patient's email, name, phone number and address(opens in a new tab). Before Hippo sends a payment conversion, it removes names, emails, phone numbers, dates of birth and IP addresses, and the conversion carries no card details, no billing or shipping address, no Stripe customer ID, no product, plan or price name and no URL path.
Renewals Stripe reports count in Hippo's record for the campaign that brought the first payment, and Hippo can send them to Google Ads and Meta the same way. Each platform credits a conversion to a campaign only inside its own window: Google's can be set from 1 to 90 days(opens in a new tab), and Meta's follows the ad set's attribution setting(opens in a new tab).
We do. Whoever controls your domain adds a DNS record for your Hippo subdomain. We install Hippo, take the Google tag and the Meta Pixel off your pages, and add Hippo's webhook endpoint in your Stripe account with whoever administers it, since Stripe sends events to a webhook endpoint(opens in a new tab) the business registers. Your agency keeps running the campaigns and sees the payment conversions arrive in Google Ads and in Meta's Events Manager.
During setup we look for anything already sending your Stripe payments to Google Ads or Meta and switch it off, so it and Hippo do not both report the same payment. That includes Meta's own app for Stripe, which sends purchase data(opens in a new tab) from your Stripe account to Meta, and a server container that forwards the webhook from Stripe with the patient's details in it. Sending a payment from a server changes the route and leaves what it carries as it was. In Google Ads, a single transaction may be counted twice(opens in a new tab) by two conversion actions, and Meta's documented deduplication pairs a pixel event with a server event(opens in a new tab).
Only with written pre-approval(opens in a new tab) from Stripe. Stripe lists telemedicine and telehealth services, and online pharmacies, among its restricted businesses(opens in a new tab), which need due diligence by Stripe. Stripe reviews each telemedicine business case by case, and telemedicine businesses do not need LegitScript certification(opens in a new tab) to use Stripe. Hippo has no part in that review. Once Stripe supports your business, Hippo counts the payments you choose by campaign.
No. Meta can restrict certain mid and lower funnel standard events(opens in a new tab) for a data source in its health and wellness category, and under a restriction, custom events stay blocked until you review and confirm them(opens in a new tab). Hippo cannot lift a category Meta assigns or restore an event Meta blocks, and it never renames an event to get past a restriction. You can ask Meta to review(opens in a new tab) the category. Hippo still records your payments by campaign, whatever Meta blocks.
Yes, if you want to know how these laws apply to your business. This page describes Stripe's terms and the law for general information and is not legal advice. Hippo handles the tracking; an attorney can advise you on your obligations. Hippolytics is not affiliated with, endorsed by or sponsored by Stripe.
See which campaigns bring new clients.
Connect campaign spend to intake inquiries.
Measure consultation bookings by campaign.
Understand what drives online bookings.
See which campaigns bring transfers and refills.
Compare acquisition across your campaigns.
See which campaigns drive consultations.
Know your cost per booked patient.
See which promotions get booked.
Connect campaign spend to appointments.
See which campaigns book consultations.
Measure calls and booking inquiries.
See which campaigns bring new patients.
See which campaigns bring walk-ins and online check-ins.
Understand which campaigns drive inquiries.
See which campaigns bring quote requests and calls.
Connect campaigns to appointment inquiries.
See which campaigns bring trials, subscriptions and orders.