How Skims Tracks Every Visitor With 10 Pixels, 38 Cookies & a Privacy Lawsuit

Because Skims is one of the few DTC brands that's been legally tested on its tracking practices. A class-action lawsuit over its Meta Pixel deployment gives us a rare window into what happens when tracking goes wrong. Understanding their setup shows you what to do — and what to avoid (see also our full tech stack breakdown):

Skims' detected technology stack suggests approximately 38 cookies on a typical page load. This estimate is based on standard cookies set by each detected platform (Meta Pixel, GA4, TikTok, Pinterest, Snapchat, Bing, Criteo, Klaviyo, Dynamic Yield, Shopify, and OneTrust). The split: we estimate ~22 first-party cookies and ~16 third-party cookies — with some advertising cookies persisting for up to 2 years.

42% of all estimated cookies are advertising trackers. Meta, Google, TikTok, Pinterest, Snapchat, Bing, and Criteo each drop their own cookies to build cross-site behavioral profiles. The longest-lived standard cookie? _ga from Google Analytics and __kla_id from Klaviyo — both set to persist for 2 years.

Notable Cookies (Based on Detected Platforms)

This cookie audit is exactly the kind of analysis LeadMaxxing generates automatically for any ecommerce site — cookie inventory, category breakdown, expiry audit, and compliance gaps — delivered to your inbox in under 60 seconds.

Skims runs 10 distinct tracking pixels and analytics tags, covering every major ad platform plus mobile attribution and display retargeting. Each one fires on page load, sending data about your visit to its respective platform. Here's what we detected via technology profiling and source code analysis:

Loading skims.com triggers requests to 30+ unique external domains. Your browser downloads scripts, pixels, fonts, and data from dozens of different companies before the page finishes loading. Here's the breakdown by category:

Network Waterfall: What Loads and When

Here's the approximate load order when your browser requests skims.com. Notice how many third-party scripts fire in the first 2 seconds — before most users have even scrolled:

Curious how many third-party domains YOUR site contacts? LeadMaxxing's free report runs this same audit on your domain and shows you exactly which vendors are loading, how they impact page speed, and which ones you can cut.

Key External Domains Contacted

Skims uses OneTrust for cookie consent — the same enterprise platform used by Nike, Gymshark, and ASOS. But Skims' consent story is unique: they were sued in a class-action for how their Meta Pixel tracked visitors. Here's how their current consent implementation works:

The Meta Pixel Lawsuit: What Happened

In 2023, Skims was hit with a class-action lawsuit in California's Northern District Court. The complaint alleged that Skims' Meta Pixel acted as "spyware" — tracking users browsing intimate apparel categories and transmitting that data to Meta (Facebook) without meaningful consent. The lawsuit cited violations of California's Invasion of Privacy Act (CIPA), Sections 631(a) and 632, seeking $5M+ in damages. The case was settled in April 2024 and dismissed with prejudice in February 2025. Settlement terms remain undisclosed.

What Happens When You Visit skims.com

Here's the estimated sequence from the moment your browser hits skims.com:

Not sure what fires before consent on your own site? LeadMaxxing's compliance audit maps your pre-consent vs post-consent script loading — so you know exactly what's at risk before a GDPR regulator or plaintiff's lawyer does.

Is Skims' tracking footprint unusual? We compared their estimated setup against averages from Cookiebot's 2024 ecommerce compliance report and HTTP Archive data:

Skims' tracking footprint is above the industry average across every metric — and they've already paid the legal price for it. With an estimated valuation near $4B and advertising across 7 platforms, they need granular attribution data to allocate ad spend. But the CIPA lawsuit shows the risk: one misconfigured consent flow can turn a tracking pixel into a multi-million-dollar liability. Elevar's server-side approach shows Skims is investing in smarter data collection that's more resilient to privacy restrictions.

Skims' story is a cautionary tale and a playbook wrapped into one. They run a sophisticated tracking stack — but they also got sued for it. The lesson isn't "don't track," it's "track smarter." If you're running Meta Pixel on a site that sells sensitive product categories (intimate apparel, health, finance), your consent implementation is the difference between profitable growth and a class-action lawsuit. And if you're not using server-side tracking yet, Skims' adoption of Elevar shows where the industry is headed.

The good news: you don't need Skims' $250K+ tracking stack to get actionable visitor data. Their setup exists because they advertise across 7 platforms simultaneously (see our social media analysis). If you're running 2-3 platforms, you need 2-3 pixels — plus a consent layer and one unified tracking solution to tie it together.

Frequently Asked Questions

How many tracking pixels does Skims use on skims.com?

Skims runs approximately 10 distinct tracking pixels and tags including Meta Pixel, Google Analytics 4, Google Ads, TikTok Pixel, Pinterest Tag, Snapchat Pixel, Microsoft/Bing UET, and Criteo. These were detected via technology profiling and source code analysis of skims.com.

Was Skims sued for its tracking practices?

Yes, Skims was sued in a class-action lawsuit in California's Northern District Court for deploying Meta's tracking pixel without adequate consent, violating California's Invasion of Privacy Act (CIPA). Plaintiffs alleged the Meta Pixel tracked users browsing intimate apparel and transmitted data to Meta without proper disclosure. The case was settled and dismissed with prejudice in February 2025.

What consent management platform does Skims use?

Skims uses OneTrust for cookie consent management, with a privacy banner implementation on their site. The footer includes links to Cookie Policy, Do Not Sell or Share My Personal Information (CCPA requirement), and a Data Request mechanism for consumer rights requests.

Does Skims use Google Tag Manager?

Yes, Skims uses Google Tag Manager with container ID GTM-P3LJS3J as their primary tag orchestration system, detected via source code analysis of skims.com. GTM manages the deployment of GA4, Google Ads conversion tracking, and coordinates pixel firing across platforms.

What email and SMS marketing platform does Skims use?

Skims uses Klaviyo as their primary email and SMS marketing platform, and Attentive for additional SMS messaging capabilities. Both were detected via technology profiling of skims.com and confirmed across multiple third-party analysis sources.

What personalization technology does Skims use on their website?

Skims uses Dynamic Yield for website personalization, Algolia for search functionality, and Black Crow AI for machine learning-based targeting and predictions. These platforms enable personalized product recommendations, intelligent search results, and predictive customer behavior modeling.

Does skims.com comply with GDPR and CCPA privacy regulations?

Skims has CCPA compliance mechanisms including a California Privacy Notice page, Do Not Sell or Share My Personal Information link, and a data request form. They use OneTrust for consent management. However, the 2023 Meta Pixel lawsuit alleged inadequate consent for tracking. The case was settled in 2024 and dismissed with prejudice in February 2025.

How many third-party vendors does Skims load on their website?

Skims loads approximately 30+ third-party vendor domains on skims.com, including advertising platforms (Meta, Google, TikTok, Pinterest, Snapchat, Bing, Criteo), analytics tools (GA4, Elevar, Singular), CRM platforms (Klaviyo, Attentive, Braze), personalization engines (Dynamic Yield, Algolia), and infrastructure services (Shopify, OneTrust, Sentry).