metabase · github-automation-metabase · Jul 15, 2026 · Jul 15, 2026
diff --git a/_data/shared_chrome.json b/_data/shared_chrome.json
@@ -1,7 +1,7 @@
 {
   "$schema": "https://www.metabase.com/shared/chrome.schema.json",
   "version": 1,
-  "generated_at": "2026-07-14T13:30:52+00:00",
+  "generated_at": "2026-07-14T21:52:03+00:00",
   "origin": "https://www.metabase.com",
   "stylesheets": [
     {

diff --git a/_docs/latest/configuring-metabase/config-template.md b/_docs/latest/configuring-metabase/config-template.md
@@ -320,7 +320,6 @@ config:
     sql-tools-parser-backend: sqlglot
     ssh-heartbeat-interval-sec: 180
     start-of-week: sunday
-    static-viz-mode: graalvm
     subscription-allowed-domains: null
     surveys-enabled: true
     sync-leaf-fields-limit: 1000

diff --git a/_docs/latest/configuring-metabase/environment-variables.md b/_docs/latest/configuring-metabase/environment-variables.md
@@ -2225,15 +2225,6 @@ Controls how often the heartbeats are sent when an SSH tunnel is established (in
 
 This will affect things like grouping by week or filtering in GUI queries. It won't affect most SQL queries, although it is used to set the WEEK_START session variable in Snowflake.
 
-### `MB_STATIC_VIZ_MODE`
-
-- Type: keyword
-- Default: `graalvm`
-
-How static visualizations (subscription/alert charts and pulse table cell colors) are rendered:
-  `graalvm` runs the JavaScript in-process on a pooled GraalVM context (default), or `node` runs it in a
-  pool of external Node.js child processes (requires a `node` binary on the host's PATH).
-
 ### `MB_SUBSCRIPTION_ALLOWED_DOMAINS`
 
 > Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.

diff --git a/_docs/latest/embedding/introduction.md b/_docs/latest/embedding/introduction.md
@@ -109,8 +109,6 @@ If you're using an AI agent to help you embed Metabase in your app, check out [A
 
 [Usage Analytics](../usage-and-performance-tools/usage-analytics) tracks embed usage, including embedding context, authentication methods, hostname, and other metadata. Check out the [Embedding usage dashboard](../usage-and-performance-tools/usage-analytics-reference#embedding-usage).
 
-For information about the anonymous usage data Metabase collects from embedded components, see [Embedding telemetry](../installation-and-operation/information-collection#embedding-telemetry).
-
 ## Embedding limitations
 
 - Currently, you can't embed [documents](../documents/introduction) (though you can create [public documents](./public-links)).

diff --git a/_docs/latest/installation-and-operation/information-collection.md b/_docs/latest/installation-and-operation/information-collection.md
@@ -38,6 +38,25 @@ This anonymous data helps us figure out things like:
 - Where people get stuck
 - How performance for key workflows (like querying or loading) changes over time
 
+## Embedding telemetry
+
+When anonymous tracking is enabled, Metabase collects usage data from embedded iframes and components. This usage data is anonymous, and just concerns embedding feature usage. It doesn't collect query content, result data, or user identifiers.
+
+### Data collected by modular embeds
+
+[Modular embedding components](../embedding/modular-embedding) collect usage events when the components are rendered in your app. Each event includes:
+
+- Which components were used (for example, a dashboard or question)
+- The component's configuration options (for example, whether downloads or drill-through are enabled)
+- The authentication method (like SSO or guest)
+- Whether a custom locale is configured
+
+Within a session, an in-memory identifier groups related events, but this identifier is regenerated on every page load and is never written to cookies or localStorage, so there's no persistent cross-session identifier.  
+
+### Data collected by iframe embeds
+
+For iframe embeds, like public links, or when embedding the full Metabase app, Metabase records query execution counts grouped by embedding type.
+
 ## Opting out of anonymous usage data collection for self-hosted Metabases
 
 If you're self-hosting Metabase, you can opt out of providing us with your anonymous usage data:

diff --git a/_docs/v0.62/configuring-metabase/config-template.md b/_docs/v0.62/configuring-metabase/config-template.md
@@ -318,7 +318,6 @@ config:
     sql-tools-parser-backend: sqlglot
     ssh-heartbeat-interval-sec: 180
     start-of-week: sunday
-    static-viz-mode: graalvm
     subscription-allowed-domains: null
     surveys-enabled: true
     sync-leaf-fields-limit: 1000

diff --git a/_docs/v0.62/configuring-metabase/environment-variables.md b/_docs/v0.62/configuring-metabase/environment-variables.md
@@ -2223,15 +2223,6 @@ Controls how often the heartbeats are sent when an SSH tunnel is established (in
 
 This will affect things like grouping by week or filtering in GUI queries. It won't affect most SQL queries, although it is used to set the WEEK_START session variable in Snowflake.
 
-### `MB_STATIC_VIZ_MODE`
-
-- Type: keyword
-- Default: `graalvm`
-
-How static visualizations (subscription/alert charts and pulse table cell colors) are rendered:
-  `graalvm` runs the JavaScript in-process on a pooled GraalVM context (default), or `node` runs it in a
-  pool of external Node.js child processes (requires a `node` binary on the host's PATH).
-
 ### `MB_SUBSCRIPTION_ALLOWED_DOMAINS`
 
 > Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.

diff --git a/_docs/v0.62/embedding/introduction.md b/_docs/v0.62/embedding/introduction.md
@@ -105,8 +105,6 @@ If you're using an AI agent to help you embed Metabase in your app, check out [A
 
 [Usage Analytics](../usage-and-performance-tools/usage-analytics) tracks embed usage, including embedding context, authentication methods, hostname, and other metadata. Check out the [Embedding usage dashboard](../usage-and-performance-tools/usage-analytics-reference#embedding-usage).
 
-For information about the anonymous usage data Metabase collects from embedded components, see [Embedding telemetry](../installation-and-operation/information-collection#embedding-telemetry).
-
 ## Embedding limitations
 
 - Currently, you can't embed [documents](../documents/introduction) (though you can create [public documents](./public-links)).

diff --git a/_docs/v0.62/installation-and-operation/information-collection.md b/_docs/v0.62/installation-and-operation/information-collection.md
@@ -36,6 +36,25 @@ This anonymous data helps us figure out things like:
 - Where people get stuck
 - How performance for key workflows (like querying or loading) changes over time
 
+## Embedding telemetry
+
+When anonymous tracking is enabled, Metabase collects usage data from embedded iframes and components. This usage data is anonymous, and just concerns embedding feature usage. It doesn't collect query content, result data, or user identifiers.
+
+### Data collected by modular embeds
+
+[Modular embedding components](../embedding/modular-embedding) collect usage events when the components are rendered in your app. Each event includes:
+
+- Which components were used (for example, a dashboard or question)
+- The component's configuration options (for example, whether downloads or drill-through are enabled)
+- The authentication method (like SSO or guest)
+- Whether a custom locale is configured
+
+Within a session, an in-memory identifier groups related events, but this identifier is regenerated on every page load and is never written to cookies or localStorage, so there's no persistent cross-session identifier.  
+
+### Data collected by iframe embeds
+
+For iframe embeds, like public links, or when embedding the full Metabase app, Metabase records query execution counts grouped by embedding type.
+
 ## Opting out of anonymous usage data collection for self-hosted Metabases
 
 If you're self-hosting Metabase, you can opt out of providing us with your anonymous usage data: