Every Mediovsky piece tagged Tracking.
SB 690 takes the pen register claim over website and app tracking away from private plaintiffs and reaches back two years. The wiretap section that covers pixels, session replay, and chat tools was not touched.
From iOS 27.2, apps in Germany, France, Italy, Poland, and Romania can show only Apple’s alternative App Tracking Transparency prompt: a full-page sheet, copy the publisher writes, and an Additional Information button. The rule for when to ask stays exactly where it was.
OpenAI’s ad platform now has a pixel, a Conversions API, and a reporting API. Its general reports count click-through conversions, its conversion report adds a one-day view window by default, and the pixel assumes consent until you tell it otherwise.
Google put numbers on first-party data plumbing on September 10: 14% more conversions with tag gateway, 11% from enhanced conversions, 26% higher incremental ROAS from Data Manager. Two of the four rest on two-week windows and one on a comparison of two half-years, so read them as signal you get back, not demand you create.
Your sales team knows which leads were worthless. Your ad account does not, because nothing ever told it. Closing that loop is not a reporting project, it is a change to the optimization target, and the hard parts are a seven-day window, a hashing spec the two platforms disagree on, and the double-counting trap nobody warns you about.
Client-side tracking now loses 20-40% of events, more in Safari-heavy markets. Server-side tagging recovers a real chunk of it, but it’s infrastructure with a bill and a consent trap, not a plugin you switch on.
