diff --git a/docs/product/dashboards/widget-builder/index.mdx b/docs/product/dashboards/widget-builder/index.mdx
index 40f9dc00f55aa..3862672cd0177 100644
--- a/docs/product/dashboards/widget-builder/index.mdx
+++ b/docs/product/dashboards/widget-builder/index.mdx
@@ -15,13 +15,23 @@ Some of these options are standard and displayed for all widgets, but others are
 
 ## Dataset
 
-In the dataset selection step, choose which type of data you would like to use in your widget. This data is classified into four different datasets: [errors](#error), [transactions](#transactions), [issues](#issues), and [releases](#releases).
+In the dataset selection step, choose which type of data you would like to use in your widget. Available datasets include: [errors](#errors), [spans](#spans), [transactions](#transactions), [logs](#logs), [issues](#issues), and [releases](#releases).
 
 ### Errors
 Choosing "Errors" allows you to query and aggregate error events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of errors that occur in your application, which Sentry will use to group into issues, for example:
 
 - Users most affected by errors
 
+### Spans
+
+Choosing "Spans" allows you to query and aggregate individual operations within traces. Spans represent specific operations like database queries, HTTP requests, or UI rendering tasks. Each span has attributes (key-value pairs like `http.method`, `db.query`, or custom attributes) and duration information. Some widget examples include:
+
+- Performance of database queries across different tables
+- Average duration of API calls grouped by endpoint
+- P90 latency of specific operations in your application
+
+You can create span-based widgets directly from [Trace Explorer](/product/explore/trace-explorer/) queries using the "Save As" button.
+
 ### Transactions
 
 Choosing "Transactions" allows you to query and aggregate transaction events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of events that track the performance of operations in your application. Some widget examples include:
@@ -29,6 +39,16 @@ Choosing "Transactions" allows you to query and aggregate transaction events in
 - Tracking performance of an endpoint
 - Throughput by country
 
+### Logs
+
+Choosing "Logs" allows you to query and aggregate structured log data from your applications. Logs are trace-connected and searchable by message content or custom properties. This data is useful for tracking application behavior that doesn't necessarily generate errors. Some widget examples include:
+
+- Count of specific log events (login attempts, checkout flows)
+- Logs filtered by severity level or custom attributes
+- Trends in application state or business events
+
+You can create log-based widgets from [Logs Explorer](/product/explore/logs/) queries.
+
 ### Issues
 
 Choosing "Issues (States, Assignment, Time, etc.)" allows you to query issue properties, such as `is:unresolved` or event properties such as `error.handled:0`, and to sort by issue fields such as `First Seen`. When searching on event properties, the search will return any issue that has one or more events matching the supplied event filters.