Microsoft Clarity

Server-side custom event delivery to Microsoft Clarity via the Clarity Data Export API. Complements Clarity’s session replay and heatmap features with server-side event context.

Why route Microsoft Clarity through Datafly Signal

• Clarity sees what the browser cannot tell it. Session replay and heatmaps observe the page. Server-side events add the facts that only your backend knows, such as confirmed revenue, fulfilment status, or a refund that followed the session.
• Consent is enforced before anything loads. Clarity is gated by the same consent state as every other destination, so a withdrawal applies across your whole stack at once rather than tool by tool.
• One integration, not another tag. The Clarity credentials live in your pipeline configuration, so rotating them is a config change rather than a site release.
• Your event stream stays in one place. The same events that feed your warehouse and your ad platforms feed Clarity, so the session context matches what the rest of your reporting shows.

Prerequisites

• A Microsoft Clarity project. Free tier is fine for basic analytics but Data Export API access may require a paid tier — confirm with your Clarity account representative.
• The Project ID of the Clarity project. Find it in the Clarity dashboard under Settings > Setup > Install tracking code.
• A Data Export API token. Generate under Settings > Data Export in the Clarity dashboard.

Configuration fields

Next steps

• Clarity is primarily a session-replay and heatmap tool; server-side events are used to enrich sessions with context Clarity cannot observe directly (e.g. post-transaction revenue).
• For server-side delivery of the full event stream, prefer a dedicated analytics destination like Amplitude, Mixpanel, or Matomo.