docs: insights gotcha (#8009)

Author: maiieul

packages/docs/src/routes/docs/labs/insights/index.mdx

@@ -5,7 +5,8 @@ contributors:
   - gioboa
   - mrhoodz
   - thejackshelton
-updated_at: '2023-10-11T22:12:12Z'
+  - maiieul
+updated_at: '2025-09-29T22:12:12Z'
 created_at: '2023-06-22T22:13:24Z'
 ---
 
@@ -19,16 +20,12 @@ Insights allow your application to collect real user usage information to optimi
 ## Architecture
 
 The optimization consists of these parts:
-- A `<Insights>` component which collects real user usage data.
+- A `<Insights>` component which collects time based bundle execution data.
+- A `qwikInsights` Vite Plugin to apply the usage data during the build process.
 - A registered application inside the builder.io database.
-- A `qwikInsights` Vite Plugin to load and save real user usage data during the build process.
 
-> NOTE:
-> To try this new feature please drop a message inside the [Qwik Discord server](https://qwik.dev/chat)
 > Currently Insights info is hosted in the Builder database. This information is about the execution of symbols/chunks in the application.
 > The implementation of the service is open-source and you have the choice to use ours or host your own.
-> (Please note, that this may become a paid service in the future.)
-
 
 ## `<Insights>` component
 
@@ -63,9 +60,10 @@ The `<Insights>` component collects this data:
 - The `pathname` part of the URL.
 - Random sessionID which identifies which symbol loads came from the same browser session.
 
-NOTE: The `<Insights>` component does not collect any user-identifiable information.
+> The `<Insights>` component does not collect any user-identifiable information.
+
+The data collected being based on the frequency bundles are being grouped together at the same time, it is **not** advised to share the same API key between your preview and production environments. During preview, developers might use the application in 3G throttling and click around, which can put unrelated bundles together. After that the import graph would be wrong, leading to over-preloading, and Insights would then base its future data collection based on those corrupted bundles. If that happened to you, we recommend creating a new API key for your production environment. In normal usage, you will release a new version of your application and there will be a long enough window for Insights to collect the data. In case you face over-preloading in your app, you can always re-create a new API key. Drop us a message in the [Qwik Discord server](https://qwik.dev/chat) if this becomes a recurrent issue for you.
 
-The information collected is sent to builder.io database for storage.
 
 ## Vite integration