A few words on Acquisitions and Renaming
What Google Renaming 'Looker Studio' Back to 'Data Studio' Actually Tells Us About the $2.6B Acquisition
On April 10, 2026, Google quietly announced that Looker Studio is being renamed back to Data Studio. Most people shrugged. A few marketers updated their bookmarks. But if you were inside Looker when Google acquired it for $2.6 billion in 2019, this “minor product update” reads like a quiet admission. A postmortem dressed up in press release language.
I was there. I helped build Looker to 700 people. Not for your dashboards - here’s why this rename matters for anyone who builds products with a real brand, then sells them to a large acquirer.
Cursor team - take note.
What the Looker Brand Actually Stood For
Looker wasn’t just a BI tool. It was a philosophy.
The core idea was governance: one semantic layer, defined in LookML, that sat between your raw data and every analyst in the company. You didn’t write ad-hoc SQL and hope everyone agreed on the numbers. You defined your metrics once ( revenue, churn, activation) and every team pulled from the same source of truth. No more “why does my dashboard say 10,000 users and yours says 11,400?”
That idea resonated deeply with a specific community: senior data engineers, analytics leads, data-forward CTOs. People who had lived through the chaos of five teams using five definitions of the same metric. Looker was their answer, and they were evangelical about it.
The brand carried that signal. When someone said “we use Looker,” it communicated something precise about how that company thought about data. It was a badge. It meant your data was governed, trusted, and not a mess.
The Acquisition: Two Products, One Name, Zero Clarity
When Google announced the acquisition in June 2019, it already had its own analytics product: Google Data Studio. Free tier. Drag-and-drop dashboards. Deeply connected to Google Ads, Google Analytics, Google Sheets. Beloved by marketers, freelancers, small business owners, and anyone who needed a quick visualization without writing a line of code.
That’s a great product. Nothing wrong with it.
But it is NOT Looker. The users are different, the problems they’re solving are different, and the underlying philosophy about how data should work is different.
In October 2022, Google decided to consolidate. Data Studio became Looker Studio. The logic, from a product portfolio perspective, was understandable: unify the analytics family under one brand, signal that these tools belong together in the Google Data Cloud ecosystem.
The execution was a branding disaster.
The Damage: When Novices and Practitioners Stop Speaking the Same Language
Data Studio had millions of users. Marketers. Small business owners. Agency folks running Google Ads reports. When the product was renamed Looker Studio, all of those users suddenly became “Looker users.” And when they talked to someone in the data world — a data engineer, a potential employer, a vendor — they’d say: “Oh yeah, I use Looker.”
That broke something real.
Because to a senior data practitioner, “I use Looker” means something specific. It means LookML. It means a governed semantic model. It means your company has invested in the infrastructure to get data right. It’s a signal of sophistication that carries weight in hiring, in fundraising, in vendor conversations.
Now that signal was noise. Real Looker practitioners started having to clarify: “No, I mean actual Looker. Not Looker Studio. The BI platform.” VCs and angels evaluating startups would hear “we use Looker for our data” and have no idea whether that meant a drag-and-drop Google Ads dashboard or a full governed analytics stack. Hiring managers reviewing resumes faced the same confusion.
The Looker brand, built on precision, became imprecise.
Google essentially took a term of art and turned it into a generic.
What Large Acquirers Always Get Wrong About Brand
Google isn’t the only company that’s made this mistake.
When a large company acquires a product with a cult following (especially a technical one), the internal pressure to integrate it into the existing brand portfolio is enormous. Product managers want coherence, marketing wants a unified story, and leadership needs to justify the price tag. Every incentive points the same direction: put the acquired brand on as many things as possible.
But a brand that means something specific to a specific community derives its value from that specificity. Stretch it and you don’t get a bigger brand, you get a weaker one. The precision that made it valuable gets averaged away.
Looker’s brand was built on trust, rigor, and a particular worldview about how data should be managed. Grafting it onto a free drag-and-drop dashboard tool didn’t elevate Data Studio. It diluted Looker.
No one inside a large acquirer has a strong incentive to protect what the acquired brand actually meant. The founders are gone or sidelined. The original community has no seat at the table. The people making the naming decision are optimizing for a slide in a product portfolio deck, not for the subtle but real meaning that “Looker” held in the minds of 50,000 data practitioners.
The Rename-Back: A Quiet Admission
Google’s official language around the April 2026 rename is all forward momentum. “Expanded mission.” “AI era.” “Data Cloud ecosystem.” Data Studio as “the on-ramp for creating and sharing ad-hoc reports.” Two tiers: Data Studio and Data Studio Pro.
After 3.5 years, Google is separating the two products again.
Looker is the enterprise BI platform and Data Studio is the lightweight visualization tool, which is exactly where things stood before the 2022 rebrand.
That’s a correction. It might not feel like one from the outside, but anyone who lived through the confusion knows what it is.
Looker gets its name back. Uncontested. No more drag-and-drop users calling themselves Looker users in job interviews and investor meetings. For the data community, that means the signal is clean again, saying “we use Looker” means something again.
What This Means If You’re Building Something
If you’re a founder with a product that has real brand equity with a specific community, protect that signal like it’s infrastructure. Because it is.
When acquisition conversations start, brand architecture questions feel secondary to valuation, earnouts, and employment agreements. They’re not. The way your product name gets used post-close will shape how your community perceives what happened, whether your team stays bought-in, and whether the thing you built retains the meaning that made it worth buying in the first place.
Get commitments on naming, in writing if you can. Understand the acquirer’s portfolio logic well enough to predict what their integration team will do in 18 months. Because that rationalization exercise is coming, and when it does, the brand question will feel like a footnote (right up until the moment it isn’t).
Small product renames are rarely just product renames. This one took four years to undo.
I'm building something new in the personal AI space and posting about it on X, follow me at @sgmlabs. Details dropping soon.