CRANDALL CONSULTING
Home › Website Tracking Cases › Blaker v. Netscout Systems

Blaker v. Netscout Systems

Published by Crandall Consulting · Informational litigation intelligence · Last substantive update: October 11, 2026

Los Angeles Superior Court
Court
California
Jurisdiction
2026-05-27
Decision Date
Lawsuit
Matter Type

Docket / citation: 25STCV31283 · Filed: 2025-10-27

Risk scores, classifications, statistics, and technical findings are informational guidelines based on observed website behavior and publicly available litigation activity, statutes, court decisions, legal commentary, and other public sources. They are not legal advice, legal opinions, or determinations of liability.

Summary

Loeb & Loeb reports that the Los Angeles Superior Court dismissed Blaker v. NetScout Systems, Inc. with prejudice, rejecting a CIPA § 638.51 claim concerning an X Corp. SDK deployed on NetScout's website. The article attributes the result to statutory interpretation distinguishing telephonic communications from routine website tracking and contrasts it with litigation involving Kochava and Jornaya.

Litigation Status

Dismissed (merits)
Current Status
Defense-favorable (as reported)
Reported Outcome Direction
Statutory interpretation
Ruling Stage
Limited (stage- or fact-specific)
Precedential Weight

Status, direction, and weight describe how tracked public sources characterize this matter as of our last review — they are informational classifications, not legal assessments.

Procedural Posture

Class-action complaint dismissed with prejudice without leave to amend.

Reported Holding

According to the source, the court construed the statute as not reaching standard website tracking software and dismissed the CIPA class action with prejudice.

What the Court Decided

The source reports that the court accepted a distinction between statutory protection of telephonic communications and routine commercial website data collection, finding a structural statutory defect in the plaintiffs' SDK-based claim.

What the Court Did Not Decide

The article does not identify additional issues left undecided. It describes the ruling as nonbinding and does not report a binding appellate resolution of the statute's application to website tracking.

Significance

Generally viewed as defense-favorable. Characterizations of significance describe how the matter has generally been discussed in tracked public sources; individual holdings are often narrow, procedural, or fact-specific, and this page does not state or imply broader holdings than the sources support.

What This Page Does and Does Not Say

This page reports what our tracked public sources say about this matter — including, where identified, the procedural posture (for example, a ruling on a motion to dismiss is not a final merits decision). It does not report legal conclusions beyond those sources, does not predict outcomes, and does not constitute legal advice.

Technologies at Issue

Third parties named or identified in tracked sources: NetScout Systems, Inc., X Corp. (f/k/a Twitter) (SDK supplier), NetScout Systems, third-party SDK vendor (unnamed), X Corp., Kochava, Jornaya, X Corp. (f/k/a Twitter), NetScout, Inc., Cookiebot by Usercentrics, Blaker (plaintiff), X (f/k/a Twitter), Kochava (referenced), Plaintiff: Brian Blaker, Brian Blaker, X Corp. (formerly Twitter).

Statutes Invoked

Claims Asserted

Claims identified in tracked public sources; pleadings may include additional or amended claims.

What This Matter May Mean for Website Operators

California Invasion of Privacy Act (CIPA) is an all-party consent statute with a private right of action. Consent standard and private enforceability are the structural features that most shape where website tracking claims are filed and how they are valued.

For operators using similar technologies, the recurring factual questions in matters like this one are when session recording begins relative to consent and whether input masking covers every field; whether chat transcripts or typing previews transit a vendor's servers before the visitor presses send; whether advertising pixels transmit page URLs or hashed form data before a consent choice; what page URLs and query strings analytics tools share with third parties. Our scanner tests these behaviors empirically.

The reported outcome direction at the statutory interpretation stage reflects how tracked sources characterize the ruling; such rulings are often narrow, posture-specific, and fact-bound rather than broad statements of law.

Detection of a similar technology on a website is an informational risk indicator, not a legal conclusion, and nothing in this section is legal advice.

Related Intelligence

Sources

About This Page

Publisher: Inspection-Ready Institute, Inc. (DBA Crandall Consulting), an independent website compliance and risk consultancy. We are not a law firm and nothing on this page is legal advice.

How this content is produced: Facts are extracted from publicly available sources — court and government materials, recognized legal press, professional analysis, and industry reports — by our litigation intelligence engine, stored with full source provenance, and rendered from the database. Risk guidelines are computed by a deterministic formula, never by an AI model directly. See the full methodology.

Limitations: Counts labeled "Tracked" reflect matters identified in our source set and are not official court statistics. We report what courts decided and did not decide; we do not predict outcomes.

Corrections: If you believe anything on this page is inaccurate, contact us via the contact page and we will review the underlying sources promptly.

Is Your Website Creating Hidden Tracking Risk?

Scan your site for third-party tracking and potential wiretap exposure. Free, no account required.

Scan My Website