chore: improve posthog session identificaion

apps/dashboard/src/lib/utils/services/posthog/index.ts

@@ -2,7 +2,11 @@ import { dev } from '$app/environment';
 import { licenseApi } from '$features/license/api/license.svelte';
 import posthog from 'posthog-js';
 
-const hasNoTracking = () => licenseApi.hasAccess('no-tracking');
+const hasNoTracking = () => {
+  const noTracking = licenseApi.hasAccess('no-tracking');
+  console.log('license_no_tracking', noTracking);
+  return noTracking;
+};
 
 export const capturePosthogEvent = (event: string, properties?: Record<string, unknown>): void => {
   if (dev || hasNoTracking()) return;
@@ -16,10 +20,34 @@ export const identifyPosthogUser = (id: string, properties?: Record<string, unkn
   posthog.identify(id, properties);
 };
 
-export const initPosthog = (): void => {
+export type PosthogBootstrapUser = {
+  id: string;
+  email?: string | null;
+  name?: string | null;
+};
+
+/**
+ * When `user` is supplied, PostHog initializes as the identified user from its
+ * very first event. Without bootstrap the first pageview / autocapture frames /
+ * session-replay attribute to a fresh anonymous UUID and the later `identify`
+ * call only aliases — session replays and initial events stay on the anon person.
+ * The follow-up `setPersonProperties` attaches email/name in the same tick so
+ * autocapture events fire with the user's properties already on the person.
+ */
+export const initPosthog = (user?: PosthogBootstrapUser): void => {
   if (dev || hasNoTracking()) return;
 
   posthog.init('phc_JfdHOZ6v0cVlGELBYx1Tmoen2nxNOrAzvgvrPA6Ksov', {
-    api_host: 'https://eu.posthog.com'
+    api_host: 'https://eu.posthog.com',
+    ...(user && {
+      bootstrap: { distinctID: user.id, isIdentifiedID: true }
+    })
   });
+
+  if (user) {
+    posthog.setPersonProperties({
+      ...(user.email && { email: user.email }),
+      ...(user.name && { name: user.name })
+    });
+  }
 };