Use Strawberry with Microsoft Clarity to investigate behaviour patterns, compare recordings and heatmaps with the rest of the product context, and prepare evidence-led UX briefs. It keeps the team focused on a testable next question. It turns a pile of session evidence into a practical research artifact rather than another dashboard link.
01
Investigate a conversion problem with the sessions behind it.
A drop in completion can be caused by a confusing page, a broken control, a device-specific issue, or traffic that was never a good fit. Strawberry can organise the Clarity recordings and heatmaps you select alongside analytics, support reports, and release notes into a hypothesis brief with traceable evidence.
02
Turn session evidence into an issue the product team can use.
“Users seem confused” is too vague for a product decision.
Strawberry can convert selected Clarity evidence into a well-scoped issue brief with affected flow, observed behaviour, reproduction conditions, impact signal, and a proposed validation step.
03
Review recurring behaviour at a useful cadence.
Watching recordings every day is not a research program.
A weekly review of a defined journey can detect new friction after releases or campaign changes. It keeps the output comparable from one period to the next.
04
Keep customer impact connected to the observed behaviour.
A recording explains what someone did, not necessarily why it mattered to the business or customer. Strawberry can combine Clarity evidence with support themes, funnel data, and the browser context your team provides. It creates a prioritisation note that keeps the caveats visible.
It can work from the Clarity views open in your authenticated browser, together with the analytics, support, and product context you choose to provide.
No native Clarity configuration capability is asserted here. Treat tracking, privacy, and project changes as separately reviewed decisions.
Yes. Define the journey, review window, and evidence standard, then schedule a routine before the product-growth meeting.
Keep the investigation narrow, minimise exposure to sensitive behaviour, and validate observed patterns before deciding on a product change.
Microsoft Clarity Strawberry