Dj sr heatmaps may #1892
Open
Dj sr heatmaps may #1892
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
djmixpanel
requested review from
ishamehramixpanel
and removed request for
a team
djmixpanel
assigned djmixpanel, carlosdanieltt and dhaval-valotia and unassigned djmixpanel
carlosdanieltt
approved these changes
Jun 6, 2025
| @@ -21,6 +31,10 @@ To function, Heatmaps require Session Replay to be enabled, as they rely on sess | |||
|
|
|||
| Heatmaps only capture data during sessions with recorded replays. If a page has limited replay coverage, the Heatmap may not offer meaningful insights. | |||
|
|
|||
| <Callout type="warning"> | |||
| When clicks occur very close to page navigation events, the heatmap may occasionally show clicks on the wrong page. This happens because the timing between page changes and click events may not align perfectly. If you notice clicks appearing on the wrong page, try using a different [backdrops](#backdrops) to find the correct page state. | |||
There was a problem hiding this comment.
Typo: backdrop should be singular.
There was a problem hiding this comment.
Pull Request Overview
This PR updates the documentation for session replays and heatmaps, providing more detailed information about the retention period and clarifying the features available.
- Extended retention period details and customization options for user/session replays.
- Added detailed descriptions for two types of heatmaps (Click Maps and Traditional Heatmaps) along with additional callouts for clarity.
- Minor copy updates to ensure consistency across the documentation files.
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| pages/docs/tracking-methods/sdks/swift/swift-replay.mdx | Updated retention period text with enterprise customization details. |
| pages/docs/session-replay/implement-session-replay/session-replay-ios.mdx | Updated retention period text to include customization details. |
| pages/docs/session-replay/implement-session-replay/session-replay-android.mdx | Updated retention period text to include customization details. |
| pages/docs/session-replay/heatmaps.mdx | Expanded heatmaps documentation with new sections for Click Maps and Traditional Heatmaps and updated callouts. |
| pages/docs/session-replay.mdx | Updated multiple retention text areas and added a list item on event feed display properties. |
Comments suppressed due to low confidence (2)
pages/docs/session-replay.mdx:43
- Consider updating this callout to include the full retention customization range (between 7 days and 360 days) for consistency with the other sections.
By default, user replays are stored for 30 days after the time of ingestion. Customers on our Enterprise plan can customize this retention period. Once a replay is expired, there is no way to view that replay.
pages/docs/session-replay/heatmaps.mdx:108
- [nitpick] Ensure language consistency by using uniformly styled quotes and apostrophes throughout the documentation to improve readability.
Backdrops are snapshots of your application in various states (such as a modal open, a menu expanded, or different page layouts). Backdrops are pulled from session replays that match the URL you're analyzing, helping you understand how different views or UI states affect user interactions.
dhaval-valotia
approved these changes
Jun 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.