Impact.com suspended the Honey browser extension on January 16, 2026, following research by Ben Edelman characterizing the extension's behavior as 'stand-down' tactics — interfering with affiliate tracking by overwriting last-click attribution at the point of conversion. The suspension has reignited a long-simmering debate about browser extensions, affiliate commission integrity, and the structural vulnerabilities of last-click attribution models.
How Honey's Attribution Hijacking Worked — And Why It Mattered
Honey, which was acquired by PayPal in 2019 for $4 billion and claims over 17 million active users, operates by offering shoppers automatic coupon code application at checkout. The controversy centers on how Honey inserts its affiliate tracking code at the final step of the purchase journey, effectively replacing the tracking attribution of the content publisher, influencer, or media buyer who drove the initial intent. In many cases, the customer would have completed the purchase without Honey's coupon — meaning the extension is capturing commission for no incremental value.
What This Means for Your Affiliate Compliance Stack
For affiliate program managers, the Honey suspension is a forcing function for a conversation that many brands have avoided: your compliance stack is your commission integrity. If you are running a program without active monitoring for toolbar and extension interference, you are likely paying commissions to attribution-hijacking tools while undercompensating the publishers who actually drove your sales. This is not a hypothetical risk — it has been standard practice for coupon and browser extension publishers for over a decade.
Auditing Your Program: The Next Steps
The practical response is to audit your top commission-receiving partners against customer journey data. Which 'affiliates' are consistently appearing as the last click on purchases where the customer was already deep in your funnel? If coupon and extension publishers are claiming disproportionate last-click credit relative to their actual traffic contribution, your attribution model has been compromised. The Honey suspension is a forcing function for tightening compliance standards across your entire program — and for accelerating your migration away from pure last-click attribution.