# Looker: Pricing page changed: feature moved > Pricing page changed: feature moved. Detected 2026-11-03 by Rewindex: what changed on Looker’s pricing page, with the before/after diff. Canonical: https://rewindex.com/change/p13698 Last updated: 2026-11-03T08:45:28Z **Summary:** _summary pending_ - Kind: Pricing · Label: Feature moved between plans (model (Jev)) - Changed: 2026-11-03 08:45 UTC · Detected: 2026-11-03 08:45 UTC - [Source: https://cloud.google.com/looker/pricing](https://cloud.google.com/looker/pricing) - [Company: Looker](https://rewindex.com/company/looker.md) - Versions: before page\_version:466 → after page\_version:13698 - Change 1 of 1 for this page ## What changed **1. Added** ```diff …. Conversational Analytics in Looker Conversational Analytics usage + in Looker (Google Cloud core) and Looker (original) is measured in data tokens, which quantify the… ``` **2. Changed** ```diff …model orchestration driving your insights. This includes translating - the natural language into a Looker query, routing + natural language into governed Looker queries, routing requests to specialized tools, and synthesizing secure semantic context.… ``` **3. Added** ```diff …routing requests to specialized tools, and synthesizing secure + semantic context. Managed at the Looker instance level, usage… ``` **4. Changed** ```diff …sent to the model for processing. This might - include things like: Prompts sent to the Agent + include: Prompts sent to the agent The conversational history of a session Relevant context… ``` **5. Changed** ```diff …the agent The conversational history of a session - Any relevant context (like + Relevant context (such as LookML semantic metadata and agent instructions) Output Data Tokens: These… ``` **6. Added** ```diff …query generated to retrieve data Any other text + or code generated by the model as part of the… ``` **7. Removed** ```diff …response to a question The API call or - SQL query generated to retrieve data Any other text… ``` **8. Changed** ```diff …data tokens are the basis for calculating monthly - usage. + 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… ``` **9. Added** ```diff …applied at the instance level as an aggregated + monthly pool shared across all authenticated users on that… ``` **10. Changed** ```diff …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 + 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,… ``` **11. Removed** ```diff …will not roll over. These tokens are ring-fenced - specifically to Looker and are not fungible across other… ``` **12. Changed** ```diff …add-on instances receive a flat, baseline allocation of - 6M input data tokens and ‹count› + 40,000,000 (40M) input data tokens and 800,000 (800K) output data tokens per month to support development… ``` **13. Changed** ```diff …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 + 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… ``` **14. Changed** ```diff …is billed at the end of each month - based on actual usage during the billing period. + 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)._ ## History of this page | When (UTC) | Change | Label | | --- | --- | --- | | 2026-11-03 08:45 UTC | Pricing page changed: feature moved (this change) | Feature moved between plans | All Looker changes: [timeline](https://rewindex.com/company/looker/changes.md) _Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._ ## Cite this Pricing page changed: feature moved on Looker’s Pricing page, changed 2026-11-03 08:45 UTC (change 1 of 1). - Canonical URL: https://rewindex.com/change/p13698 - Citation: Looker, “Pricing page changed: feature moved” (2026-11-03 08:45 UTC). Archived by Rewindex: https://rewindex.com/change/p13698 (CC BY 4.0). - Markdown link: `[Looker: Pricing page changed: feature moved (2026-11-03)](https://rewindex.com/change/p13698)` --- Canonical: https://rewindex.com/change/p13698 · Markdown: https://rewindex.com/change/p13698.md · JSON: https://rewindex.com/api/v1/changes/p13698 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:32:18.644Z