Update posthog and move to anonymized events

We don't identify users anyway, and this way we take that further to not
even store the anonymous person profiles at all. Posthog also helpfully
charges much less for events without profiles attached. The one identify
case that did exist was for the web post-purchase thank you page. This
attempted to link to the checkoutId from before the purchase to measure
conversion but it actually hasn't worked for a long time (since PayPro
was set up I think?) since we never use the checkoutId beforehand.

For now, this is disabled. In future if we want to track checkout
conversion based on website parameters (e.g. by referrer) then we might
need to find a new solution for that, but happy to ignore it for now.

Author: pimterry

package-lock.json

@@ -43,7 +43,7 @@
     "next-mdx-remote": "^4.4.1",
     "next-sitemap": "^4.2.3",
     "next-themes": "^0.2.1",
-    "posthog-js": "^1.57.2",
+    "posthog-js": "^1.188.1",
     "prismjs": "^1.27.0",
     "react": "^18.2.0",
     "react-countup": "^6.5.0",

package.json

@@ -8,12 +8,6 @@ export const CapturePurchaseEvent = () => {
   const posthog = usePostHog();
 
   const sku = params.get('sku');
-  const checkoutId = params.get('checkoutId');
-
-  if (checkoutId) {
-    posthog?.identify(checkoutId);
-  }
-
   const [planName, planCycle] = sku?.split('-') ?? [];
   posthog?.capture('Plan purchased', { planName, planCycle, sku });
 

src/app/(thank-you-pages)/web-purchase-thank-you/capture-purchase-event.tsx

@@ -10,6 +10,7 @@ if (typeof window !== 'undefined') {
     persistence: 'memory', // No cookies/local storage please
     advanced_disable_decide: true, // We don't need dynamic features, skip checking
     disable_session_recording: true, // Disabled server-side, but disable explicitly here too
+    person_profiles: 'identified_only' // Use anonymous events - no user profiles
   });
 }