On this page

The latest healthcare tracking pixel lawsuits in 2026 include LifeStance Health's $3,027,874.44 settlement, which won final approval on October 20, 2026 (settlement site, final approval order); Wellstar Health System's $4,250,000 settlement, with claims due November 10, 2026 (settlement site); the Third Circuit's August 28, 2026 decision affirming dismissal of a Meta Pixel case against Tower Health (opinion); and the FTC's July 29, 2026 complaint against Hims & Hers over health information shared with Meta and Snap (FTC case page). Curve Compliance helps healthcare marketers keep measuring ads without browser pixels on those pages: it replaces browser ad pixels with one script, sends conversions server-side to Meta, Google, TikTok, Microsoft and LinkedIn, detects PHI-like patterns before data reaches an ad platform, and signs a BAA on every plan.

Book a call. Worried a pixel on your scheduling, portal or condition pages could put your practice in the next class action? Curve's team does the setup, and most customers are live in about a week. Book a call with Curve.

Healthcare pixel lawsuit activity continued through 2026. New class actions are still being filed, such as the August 5, 2026 complaint against University of Colorado Health over the Meta/Facebook tracking pixel on its "Find a Doctor" tool (court docket). Settlements keep coming: Duke University Health System's $3,743,600 settlement won final approval on August 27, 2026, and paid valid claims on October 29, 2026 (settlement site), and Atrium Health agreed to pay up to $1,800,000 (settlement FAQ). Rulings on threshold questions go both ways. The Third Circuit found the Tower Health patients had standing but upheld the dismissal of their complaint (opinion), while the California Court of Appeal revived part of a class certification bid against Adventist Health in an opinion filed July 24, 2026 (opinion). The FTC's earlier orders against GoodRx, BetterHelp and Cerebral still shape the rules for health apps. This article, updated November 2, 2026, covers the latest developments, the legal theories behind them, and the concrete steps healthcare operators should take right now.

Latest healthcare pixel lawsuits and settlements in 2026

Updated November 2, 2026. Ordered by each case's most recent event, newest first. Every row links to the official settlement website, court record or FTC page, and each amount is written the way that source states it.

CaseWhat happenedAmount (as stated)DateSource
Duke University Health System (M.D.N.C.)Settlement over a tracking pixel on Duke Health's website. Final judgment entered. Payments for valid claims were issued October 29, 2026.$3,743,600Payments issued October 29, 2026; final approval August 27, 2026Settlement site
LifeStance Health (D. Ariz.)Settlement over pixels on its public website that allegedly sent patient information to Meta and Google. Claims closed September 29, 2026. The court held the final approval hearing on October 16, 2026.$3,027,874.44Final approval granted; order and judgment filed October 20, 2026Settlement site, final approval order
Fairchild Medical Center (Siskiyou County, Calif.)Settlement for about 1,000 California citizens over the Meta Pixel and related technologies. Claims due November 2, 2026.$25.00 expected cash payment per claimantFinal approval granted; order filed October 15, 2026Settlement site, final approval order
Atrium Health (Mecklenburg County, N.C.)Settlement over pixels on its website and, from 2015 to 2019, its patient portal, with alleged disclosure to Meta and Google. Claims closed September 28, 2026.Up to $1,800,000Final approval granted; order and judgment filed October 5, 2026Settlement FAQ, final approval order
Cone Health (M.D.N.C.)Settlement over tracking of users on its website, including the MyChart patient portal. Claims closed October 5, 2026.$1,765,000.00Final approval hearing November 5, 2026Settlement site
University of Colorado Health (D. Colo.)New class action over the Meta/Facebook tracking pixel on its "Find a Doctor" tool. UCHealth moved to dismiss on September 21, 2026.None (complaint)Filed August 5, 2026Court docket
Santoro v. Tower Health (3d Cir.)Opinion of the court: the patients had standing, but the court affirmed the dismissal of their Meta Pixel complaint and the denial of their late request to amend it. The district court had found the complaint did not adequately specify the health information shared; the patients did not challenge that finding on appeal, so the Third Circuit took no position on it.None (ruling)Decided August 28, 2026Opinion
Wellstar Health System (N.D. Ga.)Settlement over tracking pixels, cookies and other tools on its website and patient portal, with alleged disclosure to Meta and Google. Claims due November 10, 2026.$4,250,000Notices began August 24, 2026; final approval hearing December 1, 2026Settlement site
Doe v. Adventist Health System/West (Cal. Ct. App.)Reversed the denial of class certification for patients who submitted an online health risk assessment form and for part of a patient portal subclass. The case involves the Meta Pixel and Google Analytics.None (ruling)Filed July 24, 2026; certified for publication August 24, 2026Opinion
Sutter Health (Sacramento County, Calif.)Settlement of California Invasion of Privacy Act claims over tracking on webpages including the MyHealthOnline portal login page. Payments began August 21, 2026.$21.5 millionFinal approval March 6, 2026Settlement site
Boone Health (Cole County, Mo.)Settlement for patient portal users over third-party website technologies. Claims due November 9, 2026.$20.00 cash payment per approved claimPreliminary approval August 10, 2026; final approval hearing December 1, 2026Settlement site
FTC, Utah and California v. Hims & Hers (N.D. Cal.)FTC complaint alleging the telehealth company shared health information with Meta, Snap and others through customer lists and tracking technologies. Case pending.None statedComplaint July 29, 2026FTC case page
Kaiser Permanente (N.D. Cal.)Settlement over third-party technology on Kaiser Permanente websites and mobile apps. Final order entered.$46 million, with the possibility of up to $47.5 millionFinal order filed July 22, 2026Settlement site, final order

A settlement is not a finding of wrongdoing: the defendants in these settlements deny the claims on their settlement sites, and a scheduled hearing is not a final approval. For California's new limit on private CIPA pen register suits over website tracking, signed September 30, 2026 (SB 690 bill text), see California SB 690 and CIPA for health websites.

TL;DR

  • Meta pixel lawsuit healthcare settlement activity continued in 2026. Settlement funds approved or noticed this year include Kaiser's $46 million (settlement site), Sutter Health's $21.5 million (settlement site), Wellstar's $4,250,000 (settlement site) and Duke's $3,743,600 (settlement site).
  • Plaintiffs can survive standing challenges. On August 28, 2026 the Third Circuit held that patients who alleged Tower Health shared their health information with Meta had standing, yet it affirmed the dismissal of their complaint, which the district court had found did not adequately specify what information was shared; the patients did not challenge that finding on appeal (opinion). Results vary by court.
  • As Curve Compliance's pixel lawsuit tracker shows, hospital pixel litigation now extends beyond large health systems to mid-size specialty practices, fertility clinics, behavioral health providers, and substance-abuse treatment centers. 2026 examples include behavioral health provider LifeStance (settlement site) and Fairchild Medical Center, whose settlement class is about 1,000 people (settlement site).
  • The HHS OCR online tracking bulletin issued in December 2022 (revised in March 2024) is still HHS's main guidance, but on June 20, 2024 a federal court in AHA v. Becerra vacated the part that treated an IP address plus a visit to a public page about a health condition as enough to trigger HIPAA (court order). Our annotated HHS tracking bulletin shows what still applies.
  • State laws have opened additional causes of action beyond HIPAA-derivative claims, particularly the Washington My Health My Data Act (MHMDA), enacted in 2023, which makes a violation an unfair or deceptive act under the state Consumer Protection Act (RCW 19.373.090). California cases also use the state wiretap law, CIPA (Sutter Health settlement).
  • HHS says regulated entities "are not permitted to use tracking technologies in a manner that would result in impermissible disclosures" of PHI to tracking vendors (HHS bulletin). Server-side tracking through a vendor that signs a BAA and removes PHI before anything is sent to an ad platform is one way to keep measuring ads within that guidance.

What Is Different in 2026

The most significant shift in hospital pixel litigation this year is geographic and organizational breadth. Earlier cases targeted the largest health systems, such as Kaiser Permanente (settlement site) and Advocate Aurora Health (court docket). 2026 settlements also reach regional and specialty providers: Wellstar in Georgia (site), Cone Health (site) and Atrium Health (site) in North Carolina, Boone Health in Missouri (site), Fairchild Medical Center in California (site) and behavioral health provider LifeStance (site). Pixels are easy to find: a browser's developer tools, or a free scan such as Curve's compliance scanner, list the pixels and trackers a page loads. For a detailed breakdown of the Advocate Aurora matter, see our analysis: Advocate Aurora $12.2M Pixel Settlement: Anatomy of a Healthcare Data Lawsuit.

Class certification is the next battleground, and 2026 brought a notable appellate ruling. In Doe v. Adventist Health System/West, the California Court of Appeal reversed the denial of class certification for patients who submitted an online health risk assessment form and for part of a patient portal subclass, while upholding the denial for the portal subclass's medical-information (CMIA) claims (opinion filed July 24, 2026, certified for publication August 24, 2026). The trial court had reasoned that checking what each user's data contained required an individual inquiry; the appeals court disagreed in part. A certified class raises a defendant's potential exposure, which is one reason these cases settle.

The FTC also polices health apps outside HIPAA. GoodRx was its first enforcement action under the Health Breach Notification Rule and Premom its second (GoodRx, Premom). A 2023 FTC order requires BetterHelp to pay $7.8 million and bars it from sharing health data for advertising (FTC), and the Cerebral complaint also charged violations of the Opioid Addiction Recovery Fraud Prevention Act and the Restore Online Shoppers' Confidence Act (FTC). Together they show that sharing health information with advertising platforms without consent can bring penalties, refunds and bans. On July 29, 2026 the FTC, joined by Utah and California, sued telehealth provider Hims & Hers, alleging it shared health information with Meta, Snap and other third parties, including through tracking technologies (FTC case page).

The private cases in the 2026 table rely mainly on three legal frameworks.

Electronic Communications Privacy Act and State Wiretap Statutes

Plaintiffs allege that a pixel "intercepts" communications between a patient and the healthcare provider's server. In two-party-consent states (California, Pennsylvania, Illinois, and others), this theory carries extra weight because the patient never consented to Meta or Google receiving the content of their browsing session on a patient portal. Recent examples: the August 2026 UCHealth complaint asserts a single claim under the federal Electronic Communications Privacy Act (court docket), and Sutter Health's $21.5 million settlement resolved claims under the California Invasion of Privacy Act (settlement site). California narrowed one CIPA claim in September 2026; see California SB 690 and CIPA for health websites.

State Consumer Protection and Health Data Statutes

Most duties under the Washington MHMDA began March 31, 2024 (June 30, 2024 for small businesses), and the Act makes a violation of its "consumer health data" rules an unfair or deceptive act under the state Consumer Protection Act (RCW 19.373), which lets a person "injured in his or her business or property" bring a civil action (RCW 19.86.090). Connecticut and Nevada passed consumer health data laws in 2023, but Connecticut gives its Attorney General "exclusive authority to enforce" them (Conn. Gen. Stat. 42-525) and Nevada's provisions "Do not create a private right of action" (NRS 603A.550). Of the three, only Washington's gives consumers a private right of action, so it is the main new statutory hook outside wiretap law (HIPAA itself has no private right of action).

Common-Law Privacy and Breach of Fiduciary Duty

Courts treat the confidential relationship between patient and provider as central. In Santoro, the Third Circuit held that a provider's secret disclosure of a patient's confidential medical information is "analogous to the kind of harm caused by an intrusion upon seclusion," which was enough for standing, though it did not decide whether the claims could succeed (opinion). The argument is straightforward: patients reasonably expect that their healthcare provider will not transmit the details of their medical inquiries to advertising companies, and that expectation creates a fiduciary-like duty the provider breaches by deploying unconsented tracking.

For a comprehensive timeline of how these theories have played out in specific cases, see our Healthcare Pixel Lawsuit Tracker 2024-2026: Every Settlement, Amount, and Lesson Learned.

Settlement Patterns and Dollar Amounts

Among the 2026 settlements cited on this page, the totals run from $1,765,000 at Cone Health (settlement site) and up to $1,800,000 at Atrium Health (settlement FAQ) to $46 million at Kaiser, which can rise to $47.5 million (settlement site). Individual payments are far smaller than the headline numbers. Kaiser's notice estimated $20 to $40 per person, Sutter Health's settlement FAQ says the pro rata payment came to $68.81 per claimant, "lower than the estimated $90.00 payment" (settlement FAQ), Boone Health's settlement pays $20.00 per approved claim (settlement site) and Fairchild Medical Center's payment "is expected to be $25.00" (settlement site). Advocate Aurora Health's $12,225,000 settlement, approved July 10, 2024, is an earlier benchmark (court docket).

Defendants settle while denying wrongdoing. Atrium Health's settlement FAQ says the parties "agreed to a Settlement to avoid the costs and risks of a trial" (settlement FAQ), and Cone Health's site says it settled "to avoid the costs and risks associated with continuing the litigation" (settlement site). Defendants also win some rulings. On August 28, 2026 the Third Circuit affirmed dismissal of the Tower Health case, which the district court had dismissed because the patients "did not adequately specify the nature of the personal health information the tracking pixels shared" (opinion). Rulings that keep class claims alive, like the Adventist appeal, push the other way (opinion).

For ongoing tracking of amounts and outcomes, we maintain a dedicated resource: Healthcare Pixel Lawsuit Tracker: Settlement Amounts and Compliance Lessons.

What Triggers a Lawsuit in 2026

Anyone can check which healthcare websites still load Meta Pixel, Google Analytics (client-side), TikTok Pixel, or similar JavaScript on pages that collect or display health information, using a browser's developer tools or a free scan such as Curve's compliance scanner. The 2026 cases point to specific places: a "Find a Doctor" search tool (UCHealth complaint), an online health risk assessment form (Adventist opinion), an online booking tool (LifeStance settlement), a portal login page (Sutter Health settlement) and patient portals (Wellstar, Cone Health). The trigger conditions are remarkably specific.

Common Trigger Conditions

  • A pixel fires on a page whose URL contains a condition name, provider specialty, or appointment type (e.g., /oncology/schedule-appointment).
  • A pixel fires on a patient portal login page or any authenticated session page.
  • Form-field data (name, date of birth, insurance ID, reason for visit) is captured by a pixel's automatic event listeners.
  • A scheduling confirmation page transmits appointment details via pixel event parameters.

Any one of these conditions, documented in a browser's network inspector, can be the basis of a complaint, but the details matter. In Santoro, the Third Circuit did not require proof that Meta misused the data: the alleged disclosure itself was enough for standing. The case still ended in dismissal: the district court found the complaint did not adequately specify what health information the pixel shared, and the Third Circuit affirmed because the patients did not ask in time to amend it and did not challenge that finding on appeal (opinion).

The Regulatory Backdrop

HHS OCR's December 2022 bulletin on online tracking technologies (revised March 18, 2024) is still HHS's main federal guidance, with one exception. On June 20, 2024, in American Hospital Association v. Becerra, a federal court in Texas declared unlawful and vacated the part that treated an IP address plus a visit to a public, unauthenticated page about a health condition or provider as enough to trigger HIPAA (court order). HHS's page now opens with a notice of that order and says "HHS is evaluating its next steps in light of that order" (HHS bulletin). The rest of the bulletin stands. It says "Regulated entities are not permitted to use tracking technologies in a manner that would result in impermissible disclosures" of PHI to tracking vendors, and that tracking on login-protected pages such as patient portals "generally" has access to PHI. Unless the vendor has signed a BAA and the disclosure fits a permitted use, the covered entity is in violation. Our annotated HHS tracking bulletin after AHA v. Becerra goes passage by passage.

Meta's Business Tools Terms, which govern the pixel, say advertisers will not share data that "includes or is based on, directly or otherwise, health information" (Meta Business Tools Terms). Google says it "does not offer Business Associate Agreements" for Google Analytics (Google Analytics Help). So a client-side pixel from these vendors that sends PHI from those pages is a disclosure to a vendor with no BAA, whether or not Meta or Google actually "uses" the data for advertising purposes. The bulletin adds that "it is insufficient for a tracking technology vendor to agree to remove PHI from the information it receives" (HHS bulletin). For Meta specifically, see Is the Meta Pixel HIPAA compliant? For a full comparison of how these platforms handle compliance, see Meta vs Google: Comparing HIPAA Compliance Capabilities for Home Healthcare Services.

The FTC's Health Breach Notification Rule adds another layer. It applies to vendors of personal health records and PHR related entities that are not HIPAA covered entities or acting as their business associates (16 CFR 318.1), and the health services it covers include websites and mobile apps that track health conditions, treatment or medications (16 CFR 318.2). A breach includes an unauthorized disclosure, and after one they must notify affected individuals, the FTC and, if 500 or more residents of a state are affected, prominent media outlets (16 CFR 318.3). Violations are treated as violations of a rule under section 18 of the FTC Act (16 CFR 318.7), with civil penalties of up to $53,088 per violation for knowing violations, the amount the FTC set in January 2025 (Federal Register, January 17, 2025). That figure is unchanged for 2026: the FTC's September 15, 2026 notice says its "civil penalty amounts will remain unchanged during 2026" (Federal Register, September 15, 2026).

What Healthcare Operators Should Do Now

The steps below follow the parts of the HHS bulletin that still stand and the facts at issue in the 2026 cases above. This is general information, not legal advice.

Step 1: Audit Every Page for Client-Side Tracking

Run a full crawl of your website and patient portal. Identify every JavaScript tag that sends data to a third-party domain. If any of those tags fire on pages where PHI could be present (scheduling, portal, intake forms, condition-specific pages), they must be removed or replaced with a compliant alternative.

Step 2: Move to Server-Side, BAA-Covered Analytics

Move conversion tracking server-side, through a vendor that signs a BAA and removes PHI before anything is sent to an ad platform. Set up this way, Meta, Google, and Microsoft receive only the fields you choose to send for campaign optimization, after PHI has been removed. Your analytics vendor must sign a Business Associate Agreement and maintain the technical controls required by the HIPAA Security Rule.

Step 3: Document Your Data Flow

If a lawsuit or an OCR inquiry arrives, you will need to show what your tags sent, where, and when. Maintain written documentation of your tracking architecture, including data flow diagrams, BAA copies, and configuration records. This documentation should be reviewed quarterly.

Step 4: Monitor Continuously

Pixels and tags can be reintroduced by marketing teams, CMS updates, or third-party plugins. Automated monitoring that alerts your compliance team when a new client-side tracker appears on a protected page is a practical safeguard against tags creeping back.

Step 5: Review State Law Obligations

If you collect health data from consumers in Washington, check whether the MHMDA applies; it exempts information that is already protected health information under HIPAA (RCW 19.373). If you operate in states with newer health-data privacy laws, such as Connecticut (Conn. Gen. Stat. 42-515 to 42-526) and Nevada (NRS 603A.400 to 603A.550), both passed in 2023, review those statutes for consent requirements, data-sharing restrictions, and private-right-of-action provisions. Compliance with HIPAA alone is not sufficient to avoid state-law claims.

For guidance on how Meta's own platform policies have shifted and what that means for healthcare advertisers, see Meta Health Compliance for 2026: What Changed and How Healthcare Practices Adapt.

The Cost of Inaction vs. the Cost of Compliance

A mid-size health system facing a pixel class action can expect substantial legal defense costs before any settlement is reached. Settlement totals on the official sites cited above range from $1,765,000 (Cone Health) to $46 million (Kaiser), and some smaller cases pay a set amount per claimant instead. Add reputational harm, board-level scrutiny, and potential OCR enforcement, and the total cost of a pixel incident can run into the millions.

By contrast, deploying a HIPAA-compliant analytics platform, conducting a tag audit, and establishing ongoing monitoring is a defined project with a clear scope, while the cost of a class action depends on a court and a class you do not control.

If your organization still relies on client-side pixels without a BAA-covered intermediary, Curve provides HIPAA-compliant tracking and analytics with a signed BAA, PHI-safe server-side conversion delivery to Google, Meta, and Microsoft, session replay, form analytics, and campaign attribution built specifically for healthcare marketers. It is designed to give marketing teams the data they need without creating the liability that fuels pixel lawsuits.

Sources (checked October 16, 2026; settlement sites and court records for the 13 cases in the table rechecked November 2, 2026): settlement websites for LifeStance, Fairchild Medical Center, Boone Health, Cone Health, Atrium Health, Duke, Wellstar, Kaiser and Sutter Health; court records in Miller v. University of Colorado Health, Santoro v. Tower Health, Doe v. Adventist Health System/West, In re Advocate Aurora Health Pixel Litigation, the final approval orders for LifeStance and Fairchild Medical Center, the Kaiser final order and American Hospital Association v. Becerra; FTC pages for Hims & Hers, GoodRx, Premom, BetterHelp and Cerebral; the HHS online tracking bulletin; 16 CFR 318.7 and the Federal Register (January 2025, September 2026); California SB 690; state statutes for Washington and its Consumer Protection Act, Connecticut and Nevada; the Meta Business Tools Terms; and Google Analytics Help.

Frequently Asked Questions

What are the latest healthcare tracking pixel lawsuits in 2026?

The latest include LifeStance Health's $3,027,874.44 settlement, which won final approval on October 20, 2026 (settlement site, final approval order), Wellstar Health System's $4,250,000 settlement, with claims due November 10, 2026 (settlement site), the Third Circuit's August 28, 2026 ruling in Santoro v. Tower Health (opinion) and the FTC's July 29, 2026 complaint against Hims & Hers (FTC case page). The table above lists 13 cases, each with its official source.

Are healthcare pixel lawsuits still being filed in 2026, or has the wave peaked?

Lawsuits are still being filed in 2026. A class action against University of Colorado Health over the Meta/Facebook tracking pixel was filed on August 5, 2026 (court docket), and 2026 settlements reach regional and specialty providers such as Wellstar (settlement site) and LifeStance (settlement site). Washington's My Health My Data Act adds a state claim (RCW 19.373.090). Pixels still running on healthcare pages are easy to find, so the risk has not gone away.

Consent alone does not resolve the issue under HIPAA because Meta's Business Tools Terms say advertisers will not send it data based on health information (Meta Business Tools Terms), HHS says cookie banners "do not constitute a valid HIPAA authorization" (HHS bulletin), and a valid HIPAA authorization must meet specific requirements (including the right to revoke). Even with consent, you may still violate state wiretap laws in two-party-consent jurisdictions. The safer path is server-side tracking through a BAA-covered intermediary that prevents PHI from reaching Meta's servers.

What is the average settlement amount in a healthcare pixel lawsuit?

There is no official average. Settlement totals for large health systems on the official sites cited on this page run from under $2 million, such as Atrium Health's up to $1,800,000 (settlement FAQ), through Duke's $3,743,600 (settlement site), to Kaiser Permanente's $46 million, which can rise to $47.5 million (settlement website). Advocate Aurora Health's $12,225,000 settlement, approved July 10, 2024, is an earlier benchmark (court docket). Smaller cases can pay a set amount per claimant instead, such as $20.00 at Boone Health (settlement site), and per-person payments in large cases are modest too: Kaiser's notice estimated $20 to $40.

Does Google Analytics 4 solve the healthcare pixel compliance problem?

No. GA4 in its default client-side configuration still transmits IP addresses, user identifiers, and page URLs (which may contain health information) to Google's servers. Google says it "does not offer Business Associate Agreements" for Google Analytics (Google Analytics Help). Google says HIPAA-regulated entities "must refrain from exposing to Google any data that may be considered Protected Health Information (PHI)" (Google Analytics Help). On pages where PHI could be present, that means keeping Google tags off or sending data server-side through a BAA-covered vendor that strips PHI before data reaches Google. Confirm current terms with Google, as product configurations change. For telehealth brands, see Can a telehealth company use Google Analytics?

What should I do if my hospital already removed its pixels but had them running for years?

Removing pixels stops ongoing exposure but does not eliminate liability for past data transmissions. Consult with legal counsel about whether a voluntary breach notification or OCR self-disclosure is appropriate. Document when pixels were active, what data was transmitted, and when remediation occurred. This record will be critical if a lawsuit or regulatory inquiry emerges.

How do I know if my current analytics vendor is truly HIPAA compliant?

Request a signed BAA (not just a statement that they "support HIPAA"). Verify that PHI is stripped or de-identified before any data reaches ad platforms. Ask for documentation of their Security Rule controls (encryption at rest and in transit, access controls, audit logging). If the vendor gates BAA availability behind enterprise-tier pricing, confirm you are on a qualifying plan. Curve Compliance signs a BAA on every plan: a vendor that won't sign one is not HIPAA compliant for your use case, regardless of other certifications.

How can a healthcare practice keep ad tracking without sending patient data to Meta or Google?

Move conversion tracking server-side and take client-side pixels off scheduling, portal and condition pages. Curve Compliance replaces those pixels with one script, sends conversions to Meta, Google and Microsoft through their server-side APIs, and gives each platform only a fixed list of fields, with contact identifiers off by default. Curve signs a BAA, and its Event Logs show what each platform received and accepted.

Talk to Curve Compliance

Want to keep ad tracking on your scheduling, portal and condition pages without browser pixels? Curve's team sets up server-side conversion tracking under a BAA, and most customers are live in about a week. Book a call with Curve.