Most PMHNPs who launch a practice website do one very reasonable thing early on: they drop in a Google Analytics tag and, if a consultant set things up, a Meta Pixel so they can eventually run some Facebook or Instagram ads. It feels like basic hygiene. You want to know how many people visit, which pages they read, and whether the money you spend on marketing is doing anything. The problem is that on a health care website, those little snippets of code can quietly hand information about your visitors to third parties in a way that has already cost other providers a great deal of money.
This is not a hypothetical. Between 2023 and 2025, health care organizations paid out more than $100 million to settle lawsuits tied to website tracking tools. Advocate Aurora Health alone agreed to $12.2 million after its sites allegedly disclosed information about more than 2.5 million people to Meta and Google. Two Louisiana systems, LCMC Health and Willis-Knighton, were sued over Meta Pixel code that shared patient data with Facebook. Those are big organizations with legal departments, and they still got caught. A solo or small-group PMHNP practice running the same tools is exposed to the same theory of liability, just with fewer resources to absorb it.
So let’s walk through what actually creates the risk, what the current legal picture looks like after a fair amount of back-and-forth in the courts, and what you can reasonably do about it this month without hiring a privacy consultant.
Why an analytics tag becomes a HIPAA problem
The mechanism is simpler than it sounds. When someone lands on your site, a tracking pixel or analytics tag can transmit data to the company that makes it, typically an IP address, device details, the page URL, and sometimes what the person clicked. On an ordinary retail site, nobody cares. On a psychiatric practice site, the combination gets sensitive fast. An IP address paired with a visit to a page titled something like “Ketamine for Treatment-Resistant Depression” or “Book an ADHD Evaluation” can, in the eyes of regulators and plaintiffs’ attorneys, amount to protected health information, because it can reasonably be linked to an identifiable person and it reveals something about their health.
The wrinkle for behavioral health specifically is that the very topics that make your site useful are also the ones that carry stigma. A visitor reading your page on postpartum mood disorders or substance use has a real privacy interest in not having that browsing quietly forwarded to an advertising network. That is exactly the fact pattern the settlements have been built on.

It matters that neither Google nor Meta will sign a HIPAA business associate agreement covering their standard analytics and advertising products. A business associate agreement is the contract that lets a HIPAA-covered entity share protected information with a vendor. Without one, routing anything that could be PHI through those tools is a disclosure you were never permitted to make. You cannot paper over the gap after the fact.
The legal picture is muddier than the headlines
Here is where it pays to be precise, because the story has moved. In December 2022 the HHS Office for Civil Rights issued a bulletin on the use of online tracking technologies by HIPAA-covered entities, and it took an aggressive position: even on unauthenticated public pages, combining an IP address with a visit to a page about a health condition could be a PHI disclosure. Providers scrambled. Then, on June 20, 2024, a federal court in Texas, ruling in a case brought by the American Hospital Association, vacated that particular piece of the guidance, the part treating those public-page combinations as automatically protected.
It would be easy to read that as “the coast is clear.” It is not. The court struck down one interpretive overreach, but it did not hand providers permission to disclose PHI through third-party tools. The underlying HIPAA rules did not change. OCR has continued to signal that covered entities remain responsible for information disclosed through tracking technologies, including disclosures that happen by accident. And the vacatur does nothing about the more clear-cut exposure: tracking on authenticated pages, like a patient portal or an intake form a logged-in patient completes, where the connection to an identifiable individual is undeniable.
So the honest summary is this. The most extreme version of the federal guidance is gone, but the litigation risk is very much alive, and plaintiffs’ firms have not slowed down. A 2026 study published by the HIPAA Journal scanned 59 health care websites and found 75 distinct tracking tools running on them, including Google Analytics, Meta Pixel, Microsoft Advertising, and session-replay scripts that record a visitor’s every move. Health care sites are still saturated with this stuff, which means the pool of potential defendants has not shrunk.
What this means for a PMHNP in private practice
You are not a hospital system, and that cuts both ways. You have far less data flowing through your site, which lowers your absolute exposure. But you also have no privacy officer, no in-house counsel, and no cushion to absorb a five-figure settlement or the cost of defending a class claim. For a practice built on trust and confidentiality, even a modest tracking incident is the kind of thing that erodes the exact reputation you are trying to build.
There is also a straightforward clinical-values argument here. Patients come to a psychiatric provider precisely because they expect discretion. Silently forwarding their visit to your “Trauma Therapy” page to an ad network is hard to square with that promise, whatever the current state of the case law. Treating this as a values question, not just a compliance question, tends to lead to better decisions.

A practical checklist you can run this month
Find out what is actually on your site. You cannot fix what you cannot see. Free browser extensions and scanners will list the trackers loading on your pages, or your web developer can tell you in a few minutes. Expect to be a little surprised. A theme, a chat widget, an appointment plugin, or an old ad campaign can each drag in a tracker you forgot about or never authorized.
Assume Meta Pixel does not belong on a health care site. Of all the tools in the settlements, the Meta Pixel shows up the most, because it is designed to tie web activity back to specific Facebook and Instagram accounts. Unless you have a genuinely airtight reason and real privacy guidance, the safest move for a small practice is to remove it entirely. The marketing upside rarely justifies the downside for a behavioral health provider.
Rethink standard Google Analytics. Because Google will not sign a business associate agreement for GA4, running it on pages that could reveal health-seeking behavior is a real question mark. Many practices are moving to privacy-focused, HIPAA-conscious analytics platforms that will sign a BAA and that avoid collecting identifiers in the first place. You still get your visitor counts and top-pages report; you just stop shipping raw data to an ad company.
Be strictest wherever a patient is identified. The clearest exposure is on authenticated or transactional pages, your portal login, intake forms, and booking flows. Keep third-party tracking scripts off those pages entirely. If your scheduling or EHR vendor embeds anything there, ask them directly, in writing, whether it phones home to a third party and whether they will sign a business associate agreement.
Put your vendor relationships in writing. Any company whose code touches your site and could see visitor data, your host, your forms tool, your scheduler, your chat widget, is a potential business associate. Get the agreement signed, or replace the tool with one that will sign it. “We assumed they were compliant” is not a defense anyone wants to test in front of a regulator or a plaintiff’s attorney, and it is a surprisingly common way that small practices end up exposed.

The reasonable middle path
None of this means you have to fly blind or abandon marketing. You are allowed to know how your website performs. The shift is toward tools that give you that visibility without treating your patients’ browsing as inventory to be resold. Server-side analytics, BAA-backed platforms, and simply keeping ad pixels off a clinical site get you most of the insight with a fraction of the risk.
The bigger point is that a practice website is a clinical touchpoint, not just a brochure. The same care you bring to a locked filing cabinet or an encrypted email belongs on the pages patients visit before they ever book. Spend an hour this month finding out what is running on your site. It is one of the cheapest risk reductions available to a private practice, and it happens to be the right thing to do for the people you serve.
For more practical, plain-English guidance on running a compliant and effective PMHNP private practice, from your website to your billing to your clinical workflows, visit us at pmhnpwebsite.com.
