Test full user journeys.
Follow a visitor past the homepage into search, video, forms, cart, and checkout. Capture what fires after each action.
CIPA / ECPA / VPPA / WESCA / FSCA
got pixels?
Start with a free reject-all audit of the homepage for CIPA, ECPA, FSCA, or WESCA. When the letter or complaint turns on searches, forms, or checkout, Got Pixels runs those user journeys in a real browser and records requests, payloads, and screenshots at each step. No setup or scripts.
How it works
Describe the disputed user path. Composer builds the browser tests, runs the journey, and records what happened at each step. Reuse the workflow when the site changes.
Describe the site, law, consent path, and journey.
Step 1 of 4: Describe the journey
Why Got Pixels
Got Pixels tests the paths that matter in pixel cases, starts from a plain prompt, and needs nothing installed on the site.
Follow a visitor past the homepage into search, video, forms, cart, and checkout. Capture what fires after each action.
Start from journeys that fit the site: add to cart and checkout for ecommerce, articles and video for news.
Run product, cart, and checkout journeys on Shopify storefronts.
Need the issues fixed, not only found? We can remediate what the tests surface, then rerun the same suite to check the fix.
Browse product
Home, collection, product page
Add to cart
Select variant, add to cart, open cart
Checkout
Cart, checkout, contact details
Illustrative template. Edit any journey in Composer before you run it.
Pixel litigation landscape
One browser request can raise different legal questions. Got Pixels preserves the facts counsel needs to assess each theory.
Read the pixel litigation evidence guideCal. Penal Code §§ 631, 632, 638.51
Interception, confidential communications, and pen-register theories
Consent state, in-transit timing, third-party role, request data, addressing signals
CIPA evidence guide18 U.S.C. §§ 2511, 2520
Interception, use, or disclosure of electronic communications
Contents, contemporaneous acquisition, recipient, consent, party and service-provider facts
18 U.S.C. § 2710
Disclosure of video-viewing information tied to a consumer
Video title or URL, watch event, user or device identifier, recipient, consent record
VPPA evidence guide18 Pa.C.S. § 5703
Interception, disclosure, or use of electronic communications
Pennsylvania user context, contents, timing, consent, tracker and website roles
Fla. Stat. §§ 934.03, 934.10
Interception of electronic communications and substantive contents
Searches, health details, form fields, chat text, consent state, third-party requests
MD, WA, IL, MA and other statutes
State interception, health-data, privacy, and consumer-protection theories
Jurisdiction, data sensitivity, authorization, custom events, identifiers, disclosed recipients
Scope, defenses, standing, remedies, and statutory definitions vary by jurisdiction and current case law. Got Pixels captures evidence for counsel to review. It does not determine liability.
Got Pixels pricing
Each run tests a consent choice and user journey, with requests, screenshots, and a report for review. Plans reflect how many runs and seats you need. For a walkthrough, bring your site or legal question to a demo.
Start without a subscription
4 free runs per user.
Try a user journey before choosing a plan. Each audit execution uses one run.
For a team sharing an audit allowance.
or $8,000 annually
For organizations needing custom terms or capacity.
Monthly or annual terms by agreement
Accept All, Reject All, and GPC each count as a run. Paid plans include Composer, screenshots, reports, PDF and Markdown export, sharing, API and MCP access, and scheduled runs. See the app for full terms.
Questions about the software
Direct answers about the software, the browser evidence it preserves, and the legal questions counsel still decides.
Got Pixels is browser journey-testing software for pixel litigation defense. It runs defined user paths under controlled consent states and records requests, payloads, screenshots, recipients, timing, and agent steps for counsel's review.
Run the free reject-all audit on the homepage for the statute the letter cites: CIPA, ECPA, FSCA, or WESCA. If the letter describes a search, form, video, or checkout, test that journey in Got Pixels under the same consent states and keep the requests, payloads, and screenshots for counsel. A test shows what the site does today, not what it did on the date in the letter.
No. Enter a URL or a prompt such as "audit example.com for CIPA risk." Composer builds the test suite, and you can start from a template for ecommerce, news, and other site types.
Yes. A saved workflow can compare no choice, Accept All, Reject All, and GPC where relevant, then run the same journey again after a site or tag change.
No. Got Pixels preserves technical evidence. Counsel evaluates liability under the applicable law, consent record, parties, and defenses.
We run a scenario relevant to your work, then show how to inspect the browser evidence and report. Bring a site or use case if you have one.
Got Pixels
Set the user path once, inspect what fires along the way, and reuse the workflow when the site changes. Start in the app.
Product findings support legal analysis. The software does not determine liability or compliance.
Product demo
Bring a site, consent path, or legal question. We'll show how Got Pixels builds the test, runs the journey, and reports the evidence.