| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| SaaS metrics and analytics | Planning and analysis | 4% | 5 of 78 | 12% | 16 | accepted challenger | ▼−10Since September 2026: 14% → 5%, −10 points. Inside the 10-point floor: within noise. Read over the models both editions asked. |
| Financial reporting and dashboards | Planning and analysis | 0% | 23 of 105 | 20% | 15 | accepted challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 10-point floor: within noise. Read over the models both editions asked. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| SaaS metrics | 14% | 5% | ▼−10Since September 2026: 14% → 5%, −10 points. Inside the 10-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 3 → 5 of 78 |
| Financial reporting | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 10-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 37 → 23 of 105 |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 10 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 2 | 0 | 0 | 2 |
| GPT-5.4 mini | 0 | 1 | 1 | 0 | 2 |
| Gemini 3.5 Flash | 0 | 2 | 1 | 0 | 3 |
| Perplexity Sonar | 0 | 0 | 0 | 1 | 1 |
| Grok 4.1 Fast | 1 | 2 | 1 | 1 | 5 |
| Mistral Small | 0 | 1 | 0 | 1 | 2 |
| DeepSeek V4 Flash | 0 | 1 | 1 | 1 | 3 |
| Llama 4 Maverick | 0 | 1 | 0 | 1 | 2 |
| Qwen 3.7 Flash | 1 | 2 | 0 | 0 | 3 |
| Kimi K2 | 1 | 0 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 1 | 1 | 0 | 2 |
| MiniMax M2.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 1 | 0 | 0 | 1 |
| Muse Glimmer 30B | 0 | 2 | 1 | 0 | 3 |
Verbatim evidence the judge attached to positive labels.
“Choose Looker Studio if you want free dashboards, use Google products, and need simple reporting” Kimi K2 · Financial reporting · comparative prompt · first choice
“If you have \$0 budget, this is your best option.” Qwen 3.7 Flash · SaaS metrics · budget prompt · first choice
“Best truly free, unlimited option” Grok 4.1 Fast · SaaS metrics · budget prompt · first choice
“Pull those numbers into Looker Studio ... and layer on GA4 traffic, signups, and other sources.” GLM 4.7 FlashX · SaaS metrics · budget prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“It's recommended to avoid Looker Studio for external client reporting due to hidden connector costs, lack of true white-labeling, and security considerations.” Llama 4 Maverick · Financial reporting · negative prompt · hard negative
“Looker Studio: avoid it for external client reporting because of hidden connector costs, lack of true white-labeling, and security concerns” Perplexity Sonar · Financial reporting · negative prompt · hard negative
“Bottom line: Avoid for everyday SaaS metrics. Use them only for ad-hoc exploration, not for board reporting.” DeepSeek V4 Flash · SaaS metrics · negative prompt · hard negative
“Often called out for being slow or unreliable with large datasets, frequent loading delays, and breaks.” Grok 4.1 Fast · Financial reporting · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 75 of the 83 answers that named Looker Studio and are not a share of its labels.
197 of the 197 domain citations in answers naming Looker Studio came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Looker Studio's own pages state, read September 28, 2026: lookerstudio.google.com. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Looker Studio's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Looker Studio, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Looker Studio by email, built from the raw record of the edition. It shows: