Phia Founders Reportedly Knew of Cookie Stuffing for Months; Reversals Begin

Phia’s cookie-stuffing controversy now centers on what its leaders knew and when, rather than solely on whether its shopping extension misattributed purchases. TechCrunch’s August 11 account, citing leaked Slack messages and people familiar with the matter, says co-founders Phoebe Gates and Sophia Kianni knew about the practice as far back as December; the same article carries Phia’s statement that the relevant features were removed on July 7, transaction reviews and reversals had begun, and a head of compliance was being recruited.

The later evidence conflicts with Phia’s initial explanation that incorrect attribution arose from a recent release and came to the company’s attention only after an external inquiry. Phia nevertheless remains in business: its current merchant page solicits commercial relationships and advertises company-reported totals of more than one million downloads, 5,000 direct brand partners and over $12 million in partner sales during seven months. Those marketing figures are not presented as independently audited results, but the live page establishes that the service has not shut down.

The new chronology changes the central business question

Phia’s original response characterized the attribution problem as a recently introduced coding error that was fixed once identified. That framing suggested a narrow implementation failure: unintended behavior appeared in a release, outsiders detected it, and engineers removed it.

The later account describes something materially different. Internal discussions allegedly involved the founders, executives and engineers, while the disputed capability was characterized as a purpose-built feature that could be enabled or disabled. These remain reported allegations based on workplace communications and confidential sources, not findings by a court or regulator.

The distinction matters because a software defect and an intentional attribution mechanism create different governance questions. A defect calls for diagnosis, correction and testing; a deliberately designed feature also raises questions about approval, internal controls, revenue recognition and whether commercial partners received an accurate account of how sales were credited.

Phia has disputed parts of the later characterization while emphasizing remediation. Removing the feature limits future misattribution, but it does not by itself determine how long the behavior operated, which transactions it affected or whether another publisher should have received each commission.

What the extension was accused of doing

Phia, founded by Gates and Kianni, offers an app and browser extension that helps users compare products, prices and discount codes. Part of its business relies on affiliate marketing, in which a shopping service can earn a commission after referring a customer who completes a purchase.

The allegation concerns transactions in which Phia may not have supplied that referral. TechCrunch’s July 10 summary of the tests says the extension opened a background tab during checkout and replaced another affiliate’s identifier with Phia’s even when the shopper arrived independently or through a different publisher; it also says Impact.com suspended Phia and that a later check found the automatic behavior had stopped.

This practice is generally known as cookie stuffing: an affiliate identifier is placed without the affiliate having made a meaningful referral. Under an attribution system that rewards the last recorded affiliate, the substituted identifier can direct both the commission and credit for the sale to the party whose code appears last.

The consequence is broader than a single payment. Another publisher can lose its commission and the performance record attached to the purchase, while the retailer receives a distorted picture of which marketing partner influenced the customer. If those attribution records feed revenue reports, merchant negotiations or investor materials, their reliability can also be affected.

Reversals address the accounting problem, not the full dispute

Transaction reversals are the most consequential part of Phia’s response because disabling code only prevents new occurrences. Correcting earlier transactions requires reconstructing the attribution trail, determining whether Phia contributed to each purchase and identifying any publisher whose referral was displaced.

That exercise can be more complicated than refunding a uniform charge. Individual purchases may have arrived through direct visits, paid advertising, editorial links, other shopping extensions or several touchpoints in sequence. The appropriate correction therefore depends on the retailer’s attribution rules and the event history retained by the merchant and affiliate network.

The cited public material does not provide a transaction-level accounting of the affected period, the number or value of reversals, the method used to identify the rightful recipient, or a completion date. It also does not establish that Impact.com has reinstated Phia. Continued operation of the app and merchant website should therefore not be treated as evidence that every affiliate relationship has been restored.

Phia now faces a credibility test

The immediate technical response appears clear: the disputed attribution behavior stopped. The unresolved issue is whether the company’s first explanation accurately described the origin and duration of the mechanism, given the later account of internal discussions and a feature that could allegedly be switched on and off.

For merchants and affiliate partners, the strongest evidence of remediation will be a completed reconciliation showing which transactions changed attribution and how commissions were reassigned. Documented controls requiring a genuine referral or affirmative shopper action would also clarify how Phia intends to prevent a recurrence.

For investors, the chronology raises a separate concern about the quality of growth and revenue indicators. If some sales were credited through attribution that merchants or networks later reject, headline operating metrics may require adjustment even if Phia’s underlying shopping product remains available.

Phia is therefore neither simply an app accused of misconduct nor a company whose problem ended when code was removed. It is an operating startup reversing transactions while confronting credible allegations that its founders understood the disputed practice months earlier than its initial public explanation indicated.

Also read:

• Peter Thiel’s Founders Fund Backs AI Cow Collar Startup Halter at $2 Billion Valuation
• The Delve Scandal: How Two 21-Year-Old Forbes 30 Under 30 Founders Built a $300M “AI Compliance” Unicorn — And Are Now Accused of Selling Fake Reports
• What India’s $346M Startup Funding Week Means for New Founders