Skip to main content
Guide

Best HIPAA-Compliant Server-Side Tracking Tools (2026)

Compare server-side tracking tools for healthcare: which sign a BAA, on which plan, who does the setup and what reaches Meta and Google Ads.

9 min read

The best HIPAA-compliant server-side tracking tools sign a business associate agreement (BAA) for the plan you use and keep protected health information (PHI) out of what Meta, Google Ads and other ad platforms receive, and Curve Compliance, Freshpaint, Tealium, Stape (Custom plan), Cloudflare Zaraz (Enterprise), RudderStack (Enterprise) and Twilio Segment (Business Tier) each say on their own pages that they sign or offer one. They differ most on who builds the setup and on what each ad platform ends up receiving. Curve Compliance, which signs a BAA on every plan and whose team does the setup, checked each vendor's own page on October 26, 2026.

Book a call. Comparing tools because your ads still need conversions? Curve Compliance replaces browser ad pixels with one script, sends conversions server-side to Meta, Google Ads, TikTok, Microsoft Advertising and LinkedIn, and strips PHI before data reaches an ad platform. Curve's team does the setup, typically live in about a week. Book a call with Curve.

Which server-side tracking tools sign a BAA?

Each row comes from the vendor's own page, opened October 26, 2026. Curve Compliance has its own section below. Where the answer names a plan, the vendor offers its BAA only on that plan or to those customers.

ToolSigns a BAA?Plan or conditionWhat the tool isSource
FreshpaintYesNo plan named on its FAQA healthcare marketing data platform where, in its words, “Nothing is shared unless you explicitly allow it”Freshpaint FAQ
TealiumYesHIPAA customers in the healthcare and pharma verticalsTag management and customer data platform, sold as EDF for Healthcare or the Tealium for Healthcare BundleTealium for Healthcare
StapeSpecific plansAny Custom planHosting for server-side Google Tag Manager containersStape plans page
Cloudflare ZarazSpecific plansEnterprise-level customers; Zaraz is on the in-scope listLoads third-party tools, including advertising pixels and scripts, from Cloudflare's edgeCloudflare Trust Hub; Zaraz docs
RudderStackSpecific plansEnterprise plan; its plans page lists HIPAA among Enterprise featuresCustomer data infrastructure that builds on your data warehouseRudderStack Security; RudderStack plans page
Twilio SegmentSpecific plansBusiness Tier plan, in a workspace showing the HIPAA badgeCollects events and forwards them to destinationsTwilio Docs
JENTISNot statedIts HIPAA page does not mention a BAAServer-side tracking and tag managementJENTIS HIPAA page

Each linked name opens its BAA Directory entry, with the vendor's own words. A BAA covers the company that signs it, so none of these agreements reaches Meta or Google Ads, which the directory lists as not signing one (Meta; Google Ads). See which ad platforms sign a BAA.

What server-side tracking changes, and what it doesn't

HHS defines a tracking technology as “a script or code on a website or mobile app used to gather information about users or their actions as they interact with a website or mobile app” (HHS). Server-side tracking moves the send from the patient's browser to a server. That gives you a place to remove data before it leaves. It does not change what the receiving platform allows.

Meta's Business Tools Terms list “Meta Pixel, Conversions API” among the tools they govern, and advertisers agree not to share data that “includes or is based on, directly or otherwise, health information.” They add: “The names you choose and criteria you establish for your events, conversions, and any custom audiences you create must not reflect, imply or be based on any category of information described in this Section 1.h.” Those terms took effect November 3, 2025 (Meta). A server-side event to Meta faces the same rule as a pixel event.

HHS's tracking bulletin says “it is insufficient for a tracking technology vendor to agree to remove PHI from the information it receives or de-identify the PHI before the vendor saves the information.” It describes another route: a BAA with a vendor that will “de-identify online tracking information that includes PHI and then subsequently disclose only de-identified information to tracking technology vendors that are unwilling to enter into a BAA” (HHS). That is the job a server-side tool has to do. The same HHS page notes that a federal court vacated part of the bulletin on June 20, 2024: the part saying HIPAA applies when a tool connects a visitor's IP address with a visit to an unauthenticated public page about specific health conditions or healthcare providers. See why server-side tracking alone is not HIPAA compliance.

Done for you or do it yourself

The tools split into two groups. A toolkit gives your team or agency the controls, and your team decides what each ad platform receives. A managed service has the vendor's team build and run it. Here is what each vendor says about its side of the work:

  • Stape. Stape hosts server-side Google Tag Manager containers (Directory entry). The tags you configure in that container decide what Meta and Google receive. See how a GTM server-side container is set up for healthcare.
  • Cloudflare Zaraz. Cloudflare says that “While services like Zaraz are in-scope, customers are responsible for ensuring that any third-party scripts configured within Zaraz comply with HIPAA disclosure rules” (Cloudflare).
  • Twilio Segment. Twilio says to confirm the workspace shows the HIPAA badge, then points to its guide on “the shared responsibilities and requirements for building and maintaining HIPAA-compliant workflows in Segment” (Twilio).
  • RudderStack. RudderStack says “We do not store your data” and “We build on your warehouse” (RudderStack).
  • Tealium. Tealium lists a “Marketer-friendly, no-code integration workflow” on its healthcare page (Tealium).
  • Freshpaint. Freshpaint says it “provides hands-on support during implementation” and that “you can configure tracking and routing without writing code” (Freshpaint).
  • JENTIS. JENTIS says you can “De-identify the PHI with the push of a button and forward it to your existing marketing and analytics tools” (JENTIS). Ask JENTIS directly about a BAA.
  • Curve Compliance. Curve's team does the setup for you, typically live in about a week, under a BAA Curve signs on every plan.

Does your tracking vendor's BAA cover Meta or Google Ads?

No. HHS says regulated entities “must ensure that all tracking technology vendors have signed a BAA and that there is an applicable permission prior to a disclosure of PHI” (HHS). Your server-side vendor's BAA covers that vendor. Meta and Google Ads do not sign one, so whatever leaves the server-side tool for them has to be free of PHI. Google's Tag Manager Use Policy adds its own line: you agree not “to upload any data to Google Tag Manager that personally identifies an individual” (Google).

Ask every vendor on your shortlist for the exact fields each ad platform receives, event by event, and how event names are chosen. If you only need to replace the Meta Pixel, see HIPAA-compliant Meta Pixel alternatives. To take the pixel off your site first, see how to remove the Meta pixel. For a full customer data platform, see HIPAA compliant CDPs.

How to choose

  • A BAA on the plan you will buy. Stape names its Custom plan, Cloudflare its Enterprise-level customers, RudderStack its Enterprise plan and Twilio its Business Tier. Get the BAA in place before any PHI flows.
  • A fixed field list per platform. Meta's terms reach event names and criteria, so ask what each event is called and which fields go with it.
  • Who builds and maintains it. A toolkit needs someone on your side to configure every tag and destination and to keep them current. A managed service puts that on the vendor.
  • Outcomes after the click. Bookings, calls and CRM outcomes happen off your website. Check that the tool can credit them to the original ad click.
  • A record of what was sent. You need a log of what went to each platform and what it accepted.
  • A scan before you start. Curve's free website scan lists the pixels and trackers on a page, so you know what the new tool has to replace.

Which rules apply depends on your setup, so talk to your counsel.

How Curve Compliance helps

Curve Compliance is a done-for-you service. Curve replaces browser ad pixels with one script and sends conversions server-side from Curve's servers to Meta, Google Ads, TikTok, Microsoft Advertising and LinkedIn. Each platform receives only a fixed list of fields, events can use neutral names, and contact identifiers are off by default on Meta, Google Ads and TikTok. Curve checks every event for PHI-like patterns and strips PHI before data reaches an ad platform, and Event Logs show what Curve sent to each platform and what the platform accepted.

Curve keeps ad attribution when a patient leaves to book in IntakeQ, Calendly, Acuity, Jane App and other schedulers, takes outcomes from booking systems, CRMs and call tracking through incoming webhooks, and credits each to the original ad click. Curve is SOC 2 Type II and signs a BAA on every plan (Directory entry). Curve's team does the setup, typically live in about a week.

Sources, checked October 26, 2026: Freshpaint FAQ; Tealium for Healthcare; Stape plans and features; Cloudflare Trust Hub, HIPAA; Cloudflare Zaraz docs; RudderStack Security; RudderStack plans page; Twilio Docs, HIPAA Eligible Segment; JENTIS, HIPAA Compliance with JENTIS Server-side Tracking; Google Tag Manager Use Policy; Meta Business Tools Terms; HHS, Use of Online Tracking Technologies.

Frequently Asked Questions

What are the best HIPAA-compliant server-side tracking tools?

The best ones sign a BAA for the plan you use and keep PHI out of what each ad platform receives: Curve Compliance, Freshpaint, Tealium, Stape (Custom plan), Cloudflare Zaraz (Enterprise), RudderStack (Enterprise) and Twilio Segment (Business Tier) say they sign or offer one. Curve Compliance also does the setup for you, typically live in about a week.

Is server-side tracking HIPAA compliant?

Not by itself. It changes where data is sent from, not what it contains: Meta's Business Tools Terms cover the Conversions API as well as the pixel (Meta), and HHS expects a BAA with any tracking vendor that receives PHI (HHS). See why server-side tracking alone is not HIPAA compliance.

Which server-side tracking tools sign a BAA?

Freshpaint says it offers a BAA (Freshpaint), RudderStack says it “can sign a BAA” (RudderStack) and lists HIPAA on its Enterprise plan (RudderStack plans page), Tealium signs BAAs for HIPAA customers in healthcare and pharma (Tealium), Stape on any Custom plan (Stape), Cloudflare for Enterprise-level customers with Zaraz in scope (Cloudflare) and Twilio Segment on a Business Tier plan (Twilio). Curve Compliance signs one on every plan.

Does my tracking vendor's BAA cover Meta or Google Ads?

No. A BAA covers the vendor that signs it, and HHS expects every tracking technology vendor that receives PHI to have signed one (HHS). Meta and Google Ads do not sign one (Meta; Google Ads), so what reaches them has to be free of PHI.

Is Stape HIPAA compliant?

Stape says signing a BAA is “Available on any Custom plan” (Stape; Directory entry). Stape hosts the server-side Google Tag Manager container, and the tags you set up in it decide what Meta and Google receive.

Is Cloudflare Zaraz HIPAA compliant?

Cloudflare says it “enters into a BAA with Enterprise-level customers whose use of our services involves PHI,” and Zaraz is on its in-scope list. It adds that customers are responsible for making sure the third-party scripts they configure in Zaraz comply with HIPAA disclosure rules (Cloudflare).

Is server-side Google Tag Manager HIPAA compliant?

Google publishes no BAA statement for Tag Manager, and its Use Policy bars uploading data that personally identifies an individual (Google; Directory entry). If a server container handles PHI, its host needs to sign a BAA, and its tags need to keep PHI out of what ad platforms receive; see the Google Tag Manager verdict.

Does Curve Compliance sign a BAA?

Yes. Curve Compliance signs a BAA on every plan, and Curve's team does the setup, typically live in about a week (Directory entry).

Talk to Curve Compliance

Book a call. Want server-side tracking without building it yourself? Curve Compliance sends conversions to your ad platforms from its own servers, strips PHI before data reaches an ad platform and signs a BAA on every plan. Curve's team does the setup, typically live in about a week. Book a call with Curve.

Next step

Check your own site

See if your website is at risk. Enter your domain to scan it for tracking scripts that can expose patient data.

Or book a tracking audit

Stay Compliant. Scale Confidently.

Curve's team sets up HIPAA-compliant ad tracking for you, and most customers are live in about a week.

Book a free tracking audit