Looker: Pricing page changed: feature moved
Summary
Summary pending. The diff below shows exactly what changed.
What changed
Struck in red is what Looker removed; blue is what they added. Muted text is unchanged context.
Before: …. Conversational Analytics in Looker Conversational Analytics usage nothing here is measured in data tokens, which quantify the…
After: …. Conversational Analytics in Looker Conversational Analytics usage in Looker (Google Cloud core) and Looker (original) is measured in data tokens, which quantify the…
Before: …model orchestration driving your insights. This includes translating the natural language into a Looker query, routing to specialized tools, and synthesizing secure semantic context.…
After: …model orchestration driving your insights. This includes translating natural language into governed Looker queries, routing requests to specialized tools, and synthesizing secure semantic context.…
Before: …routing requests to specialized tools, and synthesizing secure nothing here context. Managed at the Looker instance level, usage…
After: …routing requests to specialized tools, and synthesizing secure semantic context. Managed at the Looker instance level, usage…
Before: …sent to the model for processing. This might include things like: Prompts sent to the Agent The conversational history of a session Relevant context…
After: …sent to the model for processing. This might include: Prompts sent to the agent The conversational history of a session Relevant context…
Before: …the agent The conversational history of a session Any relevant context (like metadata and agent instructions) Output Data Tokens: These…
After: …the agent The conversational history of a session Relevant context (such as LookML semantic metadata and agent instructions) Output Data Tokens: These…
Before: …query generated to retrieve data Any other text nothing here generated by the model as part of the…
After: …query generated to retrieve data Any other text or code generated by the model as part of the…
Before: …response to a question The API call or SQL query generated to retrieve data Any other text…
After: …response to a question The API call or removed query generated to retrieve data Any other text…
Before: …data tokens are the basis for calculating monthly usage. Data token allocations are applied at the instance…
After: …data tokens are the basis for calculating monthly usage across Looker's conversational analytics and data agent capabilities, including conversational experiences in Explore and Dashboards, standalone and embedded agents, the Conversational Analytics endpoints in the Looker API , and Looker agents in Gemini Enterprise. Included monthly data token allocations Data token allocations are applied at the instance…
Before: …applied at the instance level as an aggregated nothing here pool shared across all authenticated users on that…
After: …applied at the instance level as an aggregated monthly pool shared across all authenticated users on that…
Before: …shared across all authenticated users on that instance. Each Looker platform subscription comes with a monthly data token quota for usage of Looker's conversational analytics capabilities. Platform Subscription Tier Included Input Data Tokens (monthly) Included Output Data Tokens (monthly) Standard 60M ‹count› Enterprise / Advanced 300M 6M Embed / Elite ‹count› 24M All non-production and add-on instances receive a flat,…
After: …shared across all authenticated users on that instance. Because tokens are pooled at the instance level, all active users can draw from the shared instance inclusion. For Looker (Google Cloud core) and Looker (original) subscriptions, each paid user activated within the platform adds a monthly token allocation to the shared pool. The instance pool size scales dynamically based on the enabled users within the instance. User Type Included Input Data Tokens (Monthly) Included Output Data Tokens (Monthly) Internal Named Users (Viewer, Standard, and Developer users logging into Looker directly with data access) 1,000,000 (1M) Data Tokens per user/month 20,000 (20K) Data Tokens per user/month Embed Users (Signed Embed / Powered by Looker users) 250,000 (250K) Data Tokens per user/month 5,000 (5K) Data Tokens per user/month The total data token inclusion can be calculated by multiplying the per user allocation listed above by the number of users of each type within a Looker instance. Production instance minimum : All production instances receive a minimum of 60,000,000 (60M) input data tokens and 1,200,000 ( ‹count› ) output data tokens. Non-production instances : All non-production and add-on instances receive a flat,…
Before: …will not roll over. These tokens are ring-fenced specifically to Looker and are not fungible across other…
After: …will not roll over. These tokens are ring-fenced removed to Looker and are not fungible across other…
Before: …add-on instances receive a flat, baseline allocation of 6M input data tokens and ‹count› output data tokens per month to support development…
After: …add-on instances receive a flat, baseline allocation of 40,000,000 (40M) input data tokens and 800,000 (800K) output data tokens per month to support development…
Before: …are not fungible across other Data Cloud surfaces. As part of the Conversational Analytics launch, customers currently enjoy promotional access without quota limits or overage fees (within fair usage limits). We are extending this promotional period to allow organizations additional time to baseline usage patterns using Looker’s new observability tooling and system activity dashboards. Conversational Analytics is an evolving capability, and customers can expect continuous feature improvements—including enhanced enterprise governance controls. Google Cloud will provide at least 90 days advance notice via formal MSA communications before billing and quota enforcement begin. After this date, usage that extends beyond the instances included monthly data token allocation will be subject to overage fees. These will be billed at the end of each month to…
After: …are not fungible across other Data Cloud surfaces. Customers currently enjoy promotional access to Conversational Analytics in Looker without allocation limits or billing for additional usage (within fair usage limits) through ‹date› . During this promotional period, organizations can baseline usage patterns using Looker's System Activity dashboards. Starting ‹date› , monthly token allocations and pay-as-you-go billing for additional usage take effect. Usage that extends beyond an instance's included monthly data token allocation is billed at the end of each month to…
Before: …is billed at the end of each month based on actual usage during the billing period. Input data tokens: $3.00 per 1M tokens Output…
After: …is billed at the end of each month to your linked Google Cloud billing account based on actual usage: Input data tokens: $3.00 per 1M tokens Output…
2 noise-only block(s) hidden (dates, counters, testimonials, tokens).
Compared with the previous archived version (#466 to #13698). Text is normalized before comparing: dates, counters and tokens show as ‹date›, ‹count›, ‹tok›, and noise-only edits are hidden. Rewindex shows changed passages with a few words of context, not a copy of the page. View the live page (opens in new tab).
Archive proof
Rewindex commits each page capture it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
158e8693524ac7b9…After captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
5dbf026cbb6e335b…
History of this page
Tuesday, November 3
1 page change
- Feature moved between plansPage change
Pricing pagechangedthis change
Cite this
Pricing page changed: feature moved on Looker’s Pricing page, changed 2026-11-03 08:45 UTC (change 1 of 1).
- Title
- Pricing page changed: feature moved
- Vendor
- Looker
- Date
- URL
- https://rewindex.com/change/p13698