diff --git a/pages/docs/session-replay/heatmaps.mdx b/pages/docs/session-replay/heatmaps.mdx
index cf6526e138..4975e1bd7d 100644
--- a/pages/docs/session-replay/heatmaps.mdx
+++ b/pages/docs/session-replay/heatmaps.mdx
@@ -23,7 +23,9 @@ Heatmaps only capture data during sessions with recorded replays. If a page has
 
 ### Implementation
 
-Ensure you have Session Replay set up(see [developer guide on implementing Session Replay](/docs/session-replay/implement-session-replay/session-replay-web)), with the `record_heatmap_data` set to `true`. 
+Ensure you have Session Replay set up(see [developer guide on implementing Session Replay](/docs/session-replay/implement-session-replay/session-replay-web)), with the `record_heatmap_data` set to `true`.
+
+Clicks recorded using `record_heatmap_data` will only capture clicks while an a session recording is in progress. These clicks are sent as `$mp_click` and will not be counted against your plan data allowance.
 
 **Example Usage**
 
@@ -36,6 +38,8 @@ mixpanel.init('YOUR_PROJECT_TOKEN', {
 
 If you currently use [Autocapture](/docs/tracking-methods/autocapture) to track clicks, you can leverage these clicks to populate the Heatmaps without the `record_heatmap_data` init option.
 
+Clicks captured by Autocapture are billable events that are counted against your plan data allowance.
+
 **Example Usage**
 
 ```javascript Javascript
@@ -52,6 +56,10 @@ mixpanel.init('YOUR_PROJECT_TOKEN', {
 });
 ```
 
+<Callout type="info">
+  Clicks generated by `record_heatmap_data` are exempt from your plan data allowance. Clicks generated by [Autocapture](/docs/tracking-methods/autocapture) are billable events.
+</Callout>
+
 ### Using Heatmaps
 
 1. From the Home page, find the Heatmaps section
diff --git a/pages/docs/session-replay/implement-session-replay/session-replay-web.mdx b/pages/docs/session-replay/implement-session-replay/session-replay-web.mdx
index c47223befb..b38813bfd4 100644
--- a/pages/docs/session-replay/implement-session-replay/session-replay-web.mdx
+++ b/pages/docs/session-replay/implement-session-replay/session-replay-web.mdx
@@ -169,6 +169,8 @@ Enable Heatmap data collection by setting `record_heatmap_data` to `true` during
 
 Ensure Session Replay is enabled, as Heatmaps only collect data during sessions with recorded replays. If a page has limited replay coverage, the resulting Heatmap may provide limited or less meaningful insights.
 
+Clicks recorded using `record_heatmap_data` will only capture clicks while an a session recording is in progress. These clicks are sent as `$mp_click` and will not be counted against your plan data allowance.
+
 **Example Usage**
 
 ```javascript Javascript
@@ -180,6 +182,8 @@ mixpanel.init('YOUR_PROJECT_TOKEN', {
 
 If you use [Autocapture](/docs/tracking-methods/autocapture) to track clicks, you can leverage these clicks to populate the Heatmaps without setting the `record_heatmap_data` option during library initialization.
 
+Clicks captured by Autocapture are billable events that are counted against your plan data allowance.
+
 **Example Usage**
 
 ```javascript Javascript
@@ -196,6 +200,10 @@ mixpanel.init('YOUR_PROJECT_TOKEN', {
 });
 ```
 
+<Callout type="info">
+  Clicks generated by `record_heatmap_data` are exempt from your plan data allowance. Clicks generated by [Autocapture](/docs/tracking-methods/autocapture) are billable events.
+</Callout>
+
 ## Debugging
 
 <Callout type="info">