diff --git a/.gitea/workflows/deploy-landing.yml b/.gitea/workflows/deploy-landing.yml index d22f74f..0f34dd2 100644 --- a/.gitea/workflows/deploy-landing.yml +++ b/.gitea/workflows/deploy-landing.yml @@ -44,6 +44,11 @@ jobs: tags: | ${{ env.REGISTRY }}/${{ env.IMAGE }}:latest ${{ env.REGISTRY }}/${{ env.IMAGE }}:${{ github.sha }} + # PostHog — token public inliné dans le bundle client Astro à la + # compile. Le secret est partagé avec apps/web (même projet PostHog). + build-args: | + PUBLIC_POSTHOG_PROJECT_TOKEN=${{ secrets.POSTHOG_PROJECT_TOKEN }} + PUBLIC_POSTHOG_HOST=https://eu.i.posthog.com - name: Install kubectl run: | diff --git a/Dockerfile.landing b/Dockerfile.landing index c031ec2..d42d6e5 100644 --- a/Dockerfile.landing +++ b/Dockerfile.landing @@ -42,7 +42,17 @@ FROM deps AS build COPY packages/shared ./packages/shared COPY packages/ui ./packages/ui COPY apps/landing ./apps/landing -RUN cd apps/landing && pnpm exec astro build + +# PostHog — vars PUBLIC_* inlinées par Astro dans le bundle client à la +# compile (cf. src/components/posthog.astro). Token public (phc_*), safe à +# bake. Si vide → posthog.init('') → no-op silencieux côté navigateur. +ARG PUBLIC_POSTHOG_PROJECT_TOKEN= +ARG PUBLIC_POSTHOG_HOST=https://eu.i.posthog.com + +RUN cd apps/landing && \ + PUBLIC_POSTHOG_PROJECT_TOKEN=$PUBLIC_POSTHOG_PROJECT_TOKEN \ + PUBLIC_POSTHOG_HOST=$PUBLIC_POSTHOG_HOST \ + pnpm exec astro build # Prune devDeps. Les workspace symlinks restent intacts. Le stage runner # copie ensuite le repo entier — pnpm a besoin de la structure complète diff --git a/apps/landing/.claude/skills/integration-astro-ssr/.posthog-wizard b/apps/landing/.claude/skills/integration-astro-ssr/.posthog-wizard new file mode 100644 index 0000000..e69de29 diff --git a/apps/landing/.claude/skills/integration-astro-ssr/SKILL.md b/apps/landing/.claude/skills/integration-astro-ssr/SKILL.md new file mode 100644 index 0000000..a6a40ea --- /dev/null +++ b/apps/landing/.claude/skills/integration-astro-ssr/SKILL.md @@ -0,0 +1,57 @@ +--- +name: integration-astro-ssr +description: PostHog integration for server-rendered Astro applications with API routes +metadata: + author: PostHog + version: 1.13.1 +--- + +# PostHog integration for Astro (SSR) + +This skill helps you add PostHog analytics to Astro (SSR) applications. + +## Workflow + +Follow these steps in order to complete the integration: + +1. `basic-integration-1.0-begin.md` - PostHog Setup - Begin ← **Start here** +2. `basic-integration-1.1-edit.md` - PostHog Setup - Edit +3. `basic-integration-1.2-revise.md` - PostHog Setup - Revise +4. `basic-integration-1.3-conclude.md` - PostHog Setup - Conclusion + +## Reference files + +- `references/EXAMPLE.md` - Astro (SSR) example project code +- `references/astro.md` - Astro - docs +- `references/identify-users.md` - Identify users - docs +- `references/basic-integration-1.0-begin.md` - PostHog setup - begin +- `references/basic-integration-1.1-edit.md` - PostHog setup - edit +- `references/basic-integration-1.2-revise.md` - PostHog setup - revise +- `references/basic-integration-1.3-conclude.md` - PostHog setup - conclusion + +The example project shows the target implementation pattern. Consult the documentation for API details. + +## Key principles + +- **Environment variables**: Always use environment variables for PostHog keys. Never hardcode them. +- **Minimal changes**: Add PostHog code alongside existing integrations. Don't replace or restructure existing code. +- **Match the example**: Your implementation should follow the example project's patterns as closely as possible. + +## Framework guidelines + +- Always use the is:inline directive on PostHog script tags to prevent Astro from processing them and causing TypeScript errors +- Use PUBLIC_ prefix for client-side environment variables in Astro (e.g., PUBLIC_POSTHOG_PROJECT_TOKEN) +- Create a posthog.astro component in src/components/ for reusable initialization across pages +- Import the PostHog component in a Layout and wrap all pages with that layout +- Use posthog-node in API routes under src/pages/api/ for server-side event tracking +- Store the posthog-node client instance in a singleton pattern (src/lib/posthog-server.ts) to avoid creating multiple clients +- Pass the client session ID to server via X-PostHog-Session-Id header for unified session tracking +- When a reverse proxy is configured, both /static/* AND /array/* must route to the assets origin (us-assets.i.posthog.com or eu-assets.i.posthog.com). + +## Identifying users + +Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` headers to maintain correlation. + +## Error tracking + +Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries. diff --git a/apps/landing/.claude/skills/integration-astro-ssr/references/EXAMPLE.md b/apps/landing/.claude/skills/integration-astro-ssr/references/EXAMPLE.md new file mode 100644 index 0000000..f5758b8 --- /dev/null +++ b/apps/landing/.claude/skills/integration-astro-ssr/references/EXAMPLE.md @@ -0,0 +1,998 @@ +# PostHog Astro (SSR) Example Project + +Repository: https://github.com/PostHog/context-mill +Path: basics/astro-ssr + +--- + +## README.md + +# PostHog Astro SSR Example + +This is an [Astro](https://astro.build/) server-side rendered (SSR) example demonstrating PostHog integration with both client-side and server-side event tracking. + +It uses: + +- **Client-side**: PostHog web snippet for browser analytics +- **Server-side**: `posthog-node` for API route event tracking + +This shows how to: + +- Initialize PostHog on both client and server +- Track events from API routes using `posthog-node` +- Pass session IDs from client to server for unified sessions +- Identify users on both client and server +- Capture errors via `posthog.captureException()` +- Reset PostHog state on logout + +## Features + +- **Server-side rendering**: Full SSR with `output: 'server'` +- **API routes**: Server-side endpoints for auth and event tracking +- **Dual tracking**: Events captured on both client and server +- **Session continuity**: Session ID passed to server via headers +- **Product analytics**: Track login and burrito consideration events +- **Session replay**: Enabled via PostHog snippet configuration +- **Error tracking**: Manual error capture sent to PostHog +- **Simple auth flow**: Demo login using localStorage + server API + +## Getting started + +### 1. Install dependencies + +```bash +npm install +# or +pnpm install +``` + +### 2. Configure environment variables + +Create a `.env` file in the project root: + +```bash +# Client-side (PUBLIC_ prefix exposes to browser) +PUBLIC_POSTHOG_PROJECT_TOKEN=your_posthog_project_token +PUBLIC_POSTHOG_HOST=https://us.i.posthog.com + +# Server-side (no PUBLIC_ prefix, server-only) +POSTHOG_PROJECT_TOKEN=your_posthog_project_token +POSTHOG_HOST=https://us.i.posthog.com +``` + +Get your PostHog project token from your project settings in PostHog. + +### 3. Run the development server + +```bash +npm run dev +# or +pnpm dev +``` + +Open `http://localhost:4321` in your browser. + +## Project structure + +```text +src/ + components/ + posthog.astro # PostHog snippet for client-side tracking + Header.astro # Navigation + logout, calls posthog.reset() + layouts/ + PostHogLayout.astro # Root layout that includes PostHog + Header + lib/ + auth.ts # Client-side auth utilities + posthog-server.ts # Server-side PostHog client singleton + pages/ + index.astro # Login form, calls /api/auth/login + burrito.astro # Burrito demo, calls /api/events/burrito + profile.astro # Profile + error tracking demo + api/ + auth/ + login.ts # Server-side login endpoint with PostHog tracking + events/ + burrito.ts # Server-side event capture endpoint + styles/ + global.css # Global styles +``` + +## Key integration points + +### Server-side PostHog client (`src/lib/posthog-server.ts`) + +A singleton pattern ensures only one PostHog client is created: + +```typescript +import { PostHog } from "posthog-node"; + +let posthogClient: PostHog | null = null; + +export function getPostHogServer(): PostHog { + if (!posthogClient) { + posthogClient = new PostHog(import.meta.env.POSTHOG_PROJECT_TOKEN, { + host: import.meta.env.POSTHOG_HOST, + flushAt: 1, + flushInterval: 0, + }); + } + return posthogClient; +} +``` + +### API route with server-side tracking (`src/pages/api/auth/login.ts`) + +```typescript +import { getPostHogServer } from "../../../lib/posthog-server"; + +export const POST: APIRoute = async ({ request }) => { + const body = await request.json(); + const { username } = body; + + // Get session ID from client + const sessionId = request.headers.get("X-PostHog-Session-Id"); + + const posthog = getPostHogServer(); + + // Capture server-side event + posthog.capture({ + distinctId: username, + event: "server_login", + properties: { + $session_id: sessionId || undefined, + source: "api", + }, + }); + + return new Response(JSON.stringify({ success: true })); +}; +``` + +### Passing session ID to server (`src/pages/index.astro`) + +```javascript +// Get the session ID from PostHog to pass to the server +const sessionId = window.posthog?.get_session_id?.() || null; + +const response = await fetch("/api/auth/login", { + method: "POST", + headers: { + "Content-Type": "application/json", + "X-PostHog-Session-Id": sessionId || "", + }, + body: JSON.stringify({ username, password }), +}); +``` + +### Client-side identification (`src/pages/index.astro`) + +After server login succeeds, also identify on client: + +```javascript +window.posthog?.identify(username); +window.posthog?.capture("user_logged_in"); +``` + +### Logout and session reset (`src/components/Header.astro`) + +On logout, both the local auth state and PostHog state are cleared: + +```javascript +window.posthog?.capture("user_logged_out"); +localStorage.removeItem("currentUser"); +window.posthog?.reset(); +``` + +## Scripts + +```bash +# Run dev server +npm run dev + +# Build for production +npm run build + +# Preview production build +npm run preview +``` + +## Learn more + +- [PostHog documentation](https://posthog.com/docs) +- [PostHog Astro guide](https://posthog.com/docs/libraries/astro) +- [PostHog Node.js SDK](https://posthog.com/docs/libraries/node) +- [Astro SSR documentation](https://docs.astro.build/en/guides/server-side-rendering/) + +--- + +## .env.example + +```example +# Client-side environment variables (PUBLIC_ prefix) +PUBLIC_POSTHOG_PROJECT_TOKEN=your_posthog_project_token_here +PUBLIC_POSTHOG_HOST=https://us.i.posthog.com + +# Server-side environment variables (no PUBLIC_ prefix) +POSTHOG_PROJECT_TOKEN=your_posthog_project_token_here +POSTHOG_HOST=https://us.i.posthog.com + +``` + +--- + +## astro.config.mjs + +```mjs +import { defineConfig } from "astro/config"; +import node from "@astrojs/node"; + +export default defineConfig({ + output: "server", + adapter: node({ + mode: "standalone", + }), + image: { + service: { entrypoint: "astro/assets/services/noop" }, + }, +}); + +``` + +--- + +## src/components/Header.astro + +```astro +--- +// Header component with navigation and logout functionality +--- +
+
+ +
+ + Not logged in + +
+
+
+ + + + + +``` + +--- + +## src/components/posthog.astro + +```astro +--- +// PostHog analytics snippet for client-side tracking +// Uses is:inline to prevent Astro from processing the script +--- + + +``` + +--- + +## src/layouts/PostHogLayout.astro + +```astro +--- +import PostHog from '../components/posthog.astro'; +import Header from '../components/Header.astro'; +import '../styles/global.css'; + +interface Props { + title: string; +} + +const { title } = Astro.props; +--- + + + + + + + + {title} + + + +
+
+ +
+ + + +``` + +--- + +## src/lib/auth.ts + +```ts +// Client-side auth utilities for localStorage-based authentication + +export interface User { + username: string; + burritoConsiderations: number; +} + +export function getCurrentUser(): User | null { + if (typeof window === "undefined") return null; + + const username = localStorage.getItem("currentUser"); + if (!username) return null; + + const considerations = parseInt( + localStorage.getItem("burritoConsiderations") || "0", + 10, + ); + + return { + username, + burritoConsiderations: considerations, + }; +} + +export function login(username: string, password: string): boolean { + if (!username || !password) return false; + + localStorage.setItem("currentUser", username); + // Initialize burrito considerations if not set + if (!localStorage.getItem("burritoConsiderations")) { + localStorage.setItem("burritoConsiderations", "0"); + } + + return true; +} + +export function logout(): void { + localStorage.removeItem("currentUser"); + localStorage.removeItem("burritoConsiderations"); +} + +export function incrementBurritoConsiderations(): number { + const current = parseInt( + localStorage.getItem("burritoConsiderations") || "0", + 10, + ); + const newCount = current + 1; + localStorage.setItem("burritoConsiderations", newCount.toString()); + return newCount; +} + +``` + +--- + +## src/lib/posthog-server.ts + +```ts +import { PostHog } from "posthog-node"; + +let posthogClient: PostHog | null = null; + +/** + * Get the PostHog server-side client. + * Uses a singleton pattern to avoid creating multiple clients. + */ +export function getPostHogServer(): PostHog { + if (!posthogClient) { + posthogClient = new PostHog(import.meta.env.POSTHOG_PROJECT_TOKEN || "", { + host: import.meta.env.POSTHOG_HOST || "https://us.i.posthog.com", + // Flush immediately for demo purposes + // In production, you might want to batch events + flushAt: 1, + flushInterval: 0, + }); + } + return posthogClient; +} + +/** + * Shutdown the PostHog client gracefully. + * Call this when your server is shutting down. + */ +export async function shutdownPostHog(): Promise { + if (posthogClient) { + await posthogClient.shutdown(); + posthogClient = null; + } +} + +``` + +--- + +## src/pages/api/auth/login.ts + +```ts +import type { APIRoute } from "astro"; +import { getPostHogServer } from "../../../lib/posthog-server"; + +// In-memory user store for demo purposes +const users = new Map(); + +export const POST: APIRoute = async ({ request }) => { + try { + const body = await request.json(); + const { username, password } = body; + + if (!username || !password) { + return new Response( + JSON.stringify({ error: "Username and password are required" }), + { status: 400, headers: { "Content-Type": "application/json" } }, + ); + } + + // Check if this is a new user + const isNewUser = !users.has(username); + + if (isNewUser) { + users.set(username, { + username, + createdAt: new Date().toISOString(), + }); + } + + // Get the PostHog server client + const posthog = getPostHogServer(); + + // Get session ID from client if available (passed via header) + const sessionId = request.headers.get("X-PostHog-Session-Id"); + + // Capture server-side login event + posthog.capture({ + distinctId: username, + event: "server_login", + properties: { + $session_id: sessionId || undefined, + isNewUser, + source: "api", + timestamp: new Date().toISOString(), + }, + }); + + // Also identify the user server-side + posthog.identify({ + distinctId: username, + properties: { + username, + createdAt: isNewUser ? new Date().toISOString() : undefined, + }, + }); + + return new Response( + JSON.stringify({ + success: true, + username, + isNewUser, + }), + { status: 200, headers: { "Content-Type": "application/json" } }, + ); + } catch (error) { + console.error("Login error:", error); + return new Response(JSON.stringify({ error: "Internal server error" }), { + status: 500, + headers: { "Content-Type": "application/json" }, + }); + } +}; + +``` + +--- + +## src/pages/api/events/burrito.ts + +```ts +import type { APIRoute } from "astro"; +import { getPostHogServer } from "../../../lib/posthog-server"; + +export const POST: APIRoute = async ({ request }) => { + try { + const body = await request.json(); + const { username, totalConsiderations } = body; + + if (!username) { + return new Response(JSON.stringify({ error: "Username is required" }), { + status: 400, + headers: { "Content-Type": "application/json" }, + }); + } + + // Get the PostHog server client + const posthog = getPostHogServer(); + + // Get session ID from client if available (passed via header) + const sessionId = request.headers.get("X-PostHog-Session-Id"); + + // Capture server-side burrito consideration event + posthog.capture({ + distinctId: username, + event: "burrito_considered", + properties: { + $session_id: sessionId || undefined, + total_considerations: totalConsiderations, + source: "api", + timestamp: new Date().toISOString(), + }, + }); + + return new Response( + JSON.stringify({ + success: true, + totalConsiderations, + }), + { status: 200, headers: { "Content-Type": "application/json" } }, + ); + } catch (error) { + console.error("Burrito event error:", error); + return new Response(JSON.stringify({ error: "Internal server error" }), { + status: 500, + headers: { "Content-Type": "application/json" }, + }); + } +}; + +``` + +--- + +## src/pages/burrito.astro + +```astro +--- +import PostHogLayout from '../layouts/PostHogLayout.astro'; +--- + +
+

Burrito consideration zone

+

Take a moment to truly consider the potential of burritos.

+ +
+ + + +
+ +
+

Consideration stats

+

Total considerations: 0

+
+ +

+ Events are tracked both client-side and server-side for demonstration. +

+
+ + + + +``` + +--- + +## src/pages/index.astro + +```astro +--- +import PostHogLayout from '../layouts/PostHogLayout.astro'; +--- + +
+ + +
+

Welcome to Burrito Consideration App

+

Please sign in to begin your burrito journey

+ +
+
+ + +
+ +
+ + +
+ + + + +
+ +

+ Note: This is a demo app with server-side tracking. Use any username and password to sign in. +

+
+
+ + + + +``` + +--- + +## src/pages/profile.astro + +```astro +--- +import PostHogLayout from '../layouts/PostHogLayout.astro'; +--- + +
+

User Profile

+ +
+

Your Information

+

Username:

+

Burrito Considerations: 0

+
+ +
+

Your Burrito Journey

+

+
+ +
+

Error Tracking Demo

+

Click the button below to trigger a test error and send it to PostHog:

+ + +
+
+ + + + +``` + +--- + diff --git a/apps/landing/.claude/skills/integration-astro-ssr/references/astro.md b/apps/landing/.claude/skills/integration-astro-ssr/references/astro.md new file mode 100644 index 0000000..4b37196 --- /dev/null +++ b/apps/landing/.claude/skills/integration-astro-ssr/references/astro.md @@ -0,0 +1,165 @@ +# Astro - Docs + +PostHog makes it easy to get data about traffic and usage of your [Astro](https://astro.build/) app. Integrating PostHog into your site enables analytics about user behavior, custom events capture, session recordings, feature flags, and more. + +This guide walks you through integrating PostHog into your Astro app using the [JavaScript Web SDK](/docs/libraries/js.md). + +## Beta: integration via LLM + +Install PostHog for Astro in seconds with our wizard by running this prompt with [LLM coding agents](/blog/envoy-wizard-llm-agent.md) like Cursor and Bolt, or by running it in your terminal. + +`npx @posthog/wizard@latest` + +[Learn more](/wizard.md) + +Or, to integrate manually, continue with the rest of this guide. + +## Installation + +In your `src/components` folder, create a `posthog.astro` file: + +Terminal + +PostHog AI + +```bash +cd ./src/components +# or 'cd ./src && mkdir components && cd ./components' if your components folder doesnt exist +touch posthog.astro +``` + +In this file, add your `Web snippet` which you can find in [your project settings](https://us.posthog.com/settings/project#snippet). Be sure to include the `is:inline` directive [to prevent Astro from processing it](https://docs.astro.build/en/guides/client-side-scripts/#opting-out-of-processing), or you will get Typescript and build errors that property 'posthog' does not exist on type 'Window & typeof globalThis'. + +posthog.astro + +PostHog AI + +```javascript + +``` + +**Using with Astro's view transitions (ClientRouter)** + +If you've opted in to Astro's `` component for client-side navigation, you'll need to add an initialization guard to prevent PostHog from running multiple times during page transitions. + +Update your `posthog.astro` file to wrap the snippet with a check: + +posthog.astro + +PostHog AI + +```javascript +--- +// src/components/posthog.astro +--- + +``` + +Without this guard, `ClientRouter`'s soft navigation can re-execute the inline script during page transitions, causing a stack overflow error. The `capture_pageview: 'history_change'` option ensures pageviews are tracked automatically as users navigate. + +The next step is to a create a [Layout](https://docs.astro.build/en/core-concepts/layouts/) where we will use `posthog.astro`. Create a new file `PostHogLayout.astro` in your `src/layouts` folder: + +Terminal + +PostHog AI + +```bash +cd .. && cd .. # move back to your base directory if you're still in src/components/posthog.astro +cd ./src/layouts +# or 'cd ./src && mkdir layouts && cd ./layouts' if your layouts folder doesn't exist yet +touch PostHogLayout.astro +``` + +Add the following code to `PostHogLayout.astro`: + +PostHogLayout.astro + +PostHog AI + +```javascript +--- +import PostHog from '../components/posthog.astro' +--- + + + +``` + +Lastly, update `index.astro` to wrap your existing app components with the new Layout: + +index.astro + +PostHog AI + +```javascript +--- +import PostHogLayout from '../layouts/PostHogLayout.astro'; +--- + + + +``` + +## Identifying users + +> **Identifying users is required.** Call `posthog.identify('your-user-id')` after login to link events to a known user. This is what connects frontend event captures, [session replays](/docs/session-replay.md), [LLM traces](/docs/ai-engineering.md), and [error tracking](/docs/error-tracking.md) to the same person — and lets backend events link back too. +> +> See our guide on [identifying users](/docs/getting-started/identify-users.md) for how to set this up. + +Set up a reverse proxy (recommended) + +We recommend [setting up a reverse proxy](/docs/advanced/proxy.md), so that events are less likely to be intercepted by tracking blockers. + +We have our [own managed reverse proxy service](/docs/advanced/proxy/managed-reverse-proxy.md), which is free for all PostHog Cloud users, routes through our infrastructure, and makes setting up your proxy easy. + +If you don't want to use our managed service then there are several other options for creating a reverse proxy, including using [Cloudflare](/docs/advanced/proxy/cloudflare.md), [AWS Cloudfront](/docs/advanced/proxy/cloudfront.md), and [Vercel](/docs/advanced/proxy/vercel.md). + +Grouping products in one project (recommended) + +If you have multiple customer-facing products (e.g. a marketing website + mobile app + web app), it's best to install PostHog on them all and [group them in one project](/docs/settings/projects.md). + +This makes it possible to track users across their entire journey (e.g. from visiting your marketing website to signing up for your product), or how they use your product across multiple platforms. + +Add IPs to Firewall/WAF allowlists (recommended) + +For certain features like [heatmaps](/docs/toolbar/heatmaps.md), your Web Application Firewall (WAF) may be blocking PostHog’s requests to your site. Add these IP addresses to your WAF allowlist or rules to let PostHog access your site. + +**EU**: `3.75.65.221`, `18.197.246.42`, `3.120.223.253` + +**US**: `44.205.89.55`, `52.4.194.122`, `44.208.188.173` + +These are public, stable IPs used by PostHog services (e.g., Celery tasks for snapshots). + +## Next steps + +For any technical questions for how to integrate specific PostHog features into Astro (such as analytics, feature flags, A/B testing, surveys, etc.), have a look at our [JavaScript Web SDK docs](/docs/libraries/js/features.md). + +Alternatively, the following tutorials can help you get started: + +- [How to set up Astro analytics, feature flags, and more](/tutorials/astro-analytics.md) +- [How to set up A/B tests in Astro](/tutorials/astro-ab-tests.md) +- [How to set up surveys in Astro](/tutorials/astro-surveys.md) + +### Community questions + +Ask a question + +### Was this page useful? + +HelpfulCould be better \ No newline at end of file diff --git a/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.0-begin.md b/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.0-begin.md new file mode 100644 index 0000000..51bb534 --- /dev/null +++ b/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.0-begin.md @@ -0,0 +1,46 @@ +--- +title: PostHog Setup - Begin +description: Start the event tracking setup process by analyzing the project and creating an event tracking plan +--- + +We're making an event tracking plan for this project. + +Before proceeding, find any existing `posthog.capture()` code. Make note of event name formatting. + +From the project's file list, select between 10 and 15 files that might have interesting business value for event tracking, especially conversion and churn events. Also look for additional files related to login that could be used for identifying users, along with error handling. Read the files. If a file is already well-covered by PostHog events, replace it with another option. Do not spawn subagents. + +Look for opportunities to track client-side events. + +**IMPORTANT: Server-side events are REQUIRED** if the project includes any instrumentable server-side code. If the project has API routes (e.g., `app/api/**/route.ts`) or Server Actions, you MUST include server-side events for critical business operations like: + + - Payment/checkout completion + - Webhook handlers + - Authentication endpoints + +Do not skip server-side events - they capture actions that cannot be tracked client-side. + +Create a new file with a JSON array at the root of the project: .posthog-events.json. It should include one object for each event we want to add: event name, event description, and the file path we want to place the event in. If events already exist, don't duplicate them; supplement them. + +Track actions only, not pageviews. These can be captured automatically. Exceptions can be made for "viewed"-type events that correspond to the top of a conversion funnel. + +As you review files, make an internal note of opportunities to identify users and catch errors. We'll need them for the next step. + +## Status + +Before beginning a phase of the setup, you will send a status message with the exact prefix '[STATUS]', as in: + +[STATUS] Checking project structure. + +Status to report in this phase: + +- Checking project structure +- Verifying PostHog dependencies +- Generating events based on project + +## Abort statuses + +If and only if the instructions have `[ABORT]` states specified, and you clearly match the conditions for an abort, emit the abort message. Do NOT attempt to exit or halt yourself — the wizard's middleware catches `[ABORT]` and terminates the run for you. + +--- + +**Upon completion, continue with:** [basic-integration-1.1-edit.md](basic-integration-1.1-edit.md) \ No newline at end of file diff --git a/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.1-edit.md b/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.1-edit.md new file mode 100644 index 0000000..ca9d70e --- /dev/null +++ b/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.1-edit.md @@ -0,0 +1,37 @@ +--- +title: PostHog Setup - Edit +description: Implement PostHog event tracking in the identified files, following best practices and the example project +--- + +For each of the files and events noted in .posthog-events.json, make edits to capture events using PostHog. Make sure to set up any helper files needed. Carefully examine the included example project code: your implementation should match it as closely as possible. Do not spawn subagents. + +Use environment variables for PostHog keys. Do not hardcode PostHog keys. + +If a file already has existing integration code for other tools or services, don't overwrite or remove that code. Place PostHog code below it. + +For each event, add useful properties, and use your access to the PostHog source code to ensure correctness. You also have access to documentation about creating new events with PostHog. Consider this documentation carefully and follow it closely before adding events. Your integration should be based on documented best practices. Carefully consider how the user project's framework version may impact the correct PostHog integration approach. + +Remember that you can find the source code for any dependency in the node_modules directory. This may be necessary to properly populate property names. There are also example project code files available via the PostHog MCP; use these for reference. + +Where possible, add calls for PostHog's identify() function on the client side upon events like logins and signups. Use the contents of login and signup forms to identify users on submit. If there is server-side code, pass the client-side session and distinct ID to the server-side code to identify the user. On the server side, make sure events have a matching distinct ID where relevant. + +It's essential to do this in both client code and server code, so that user behavior from both domains is easy to correlate. + +You should also add PostHog exception capture error tracking to these files where relevant. + +Remember: Do not alter the fundamental architecture of existing files. Make your additions minimal and targeted. + +Remember the documentation and example project resources you were provided at the beginning. Read them now. + +## Status + +Status to report in this phase: + +- Inserting PostHog capture code +- A status message for each file whose edits you are planning, including a high level summary of changes +- A status message for each file you have edited + + +--- + +**Upon completion, continue with:** [basic-integration-1.2-revise.md](basic-integration-1.2-revise.md) \ No newline at end of file diff --git a/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.2-revise.md b/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.2-revise.md new file mode 100644 index 0000000..5ac72f0 --- /dev/null +++ b/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.2-revise.md @@ -0,0 +1,22 @@ +--- +title: PostHog Setup - Revise +description: Review and fix any errors in the PostHog integration implementation +--- + +Check the project for errors. Read the package.json file for any type checking or build scripts that may provide input about what to fix. Remember that you can find the source code for any dependency in the node_modules directory. Do not spawn subagents. + +Ensure that any components created were actually used. + +Once all other tasks are complete, run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Do not run formatting or linting across the entire project's codebase. + +## Status + +Status to report in this phase: + +- Finding and correcting errors +- Report details of any errors you fix +- Linting, building and prettying + +--- + +**Upon completion, continue with:** [basic-integration-1.3-conclude.md](basic-integration-1.3-conclude.md) \ No newline at end of file diff --git a/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.3-conclude.md b/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.3-conclude.md new file mode 100644 index 0000000..b48af6a --- /dev/null +++ b/apps/landing/.claude/skills/integration-astro-ssr/references/basic-integration-1.3-conclude.md @@ -0,0 +1,38 @@ +--- +title: PostHog Setup - Conclusion +description: Review and fix any errors in the PostHog integration implementation +--- + +Use the PostHog MCP to create a new dashboard named "Analytics basics" based on the events created here. Make sure to use the exact same event names as implemented in the code. Populate it with up to five insights, with special emphasis on things like conversion funnels, churn events, and other business critical insights. + +Search for a file called `.posthog-events.json` and read it for available events. Do not spawn subagents. + +Create the file posthog-setup-report.md. It should include a summary of the integration edits, a table with the event names, event descriptions, and files where events were added, along with a list of links for the dashboard and insights created. Follow this format: + + +# PostHog post-wizard report + +The wizard has completed a deep integration of your project. [Detailed summary of changes] + +[table of events/descriptions/files] + +## Next steps + +We've built some insights and a dashboard for you to keep an eye on user behavior, based on the events we just instrumented: + +[links] + +### Agent skill + +We've left an agent skill folder in your project. You can use this context for further agent development when using Claude Code. This will help ensure the model provides the most up-to-date approaches for integrating PostHog. + + + +Upon completion, remove .posthog-events.json. + +## Status + +Status to report in this phase: + +- Configured dashboard: [insert PostHog dashboard URL] +- Created setup report: [insert full local file path] \ No newline at end of file diff --git a/apps/landing/.claude/skills/integration-astro-ssr/references/identify-users.md b/apps/landing/.claude/skills/integration-astro-ssr/references/identify-users.md new file mode 100644 index 0000000..564ead2 --- /dev/null +++ b/apps/landing/.claude/skills/integration-astro-ssr/references/identify-users.md @@ -0,0 +1,271 @@ +# Identify users - Docs + +Linking events to specific users enables you to build a full picture of how they're using your product across different sessions, devices, and platforms. + +This is straightforward to do when [capturing backend events](/docs/product-analytics/capture-events?tab=Node.js.md), as you associate events to a specific user using a `distinct_id`, which is a required argument. + +However, in the frontend of a [web](/docs/libraries/js/features.md#capturing-events) or [mobile app](/docs/libraries/ios.md#capturing-events), a `distinct_id` is not a required argument — PostHog's SDKs will generate an anonymous `distinct_id` for you automatically and you can capture events anonymously, provided you use the appropriate [configuration](/docs/libraries/js/features.md#capturing-anonymous-events). + +To link events to specific users, call `identify`: + +PostHog AI + +### Web + +```javascript +posthog.identify( + 'distinct_id', // Replace 'distinct_id' with your user's unique identifier + { email: 'max@hedgehogmail.com', name: 'Max Hedgehog' } // optional: set additional person properties +); +``` + +### Android + +```kotlin +PostHog.identify( + distinctId = distinctID, // Replace 'distinctID' with your user's unique identifier + // optional: set additional person properties + userProperties = mapOf( + "name" to "Max Hedgehog", + "email" to "max@hedgehogmail.com" + ) +) +``` + +### iOS + +```swift +PostHogSDK.shared.identify("distinct_id", // Replace "distinct_id" with your user's unique identifier + userProperties: ["name": "Max Hedgehog", "email": "max@hedgehogmail.com"]) // optional: set additional person properties +``` + +### React Native + +```jsx +posthog.identify('distinct_id', { // Replace "distinct_id" with your user's unique identifier + email: 'max@hedgehogmail.com', // optional: set additional person properties + name: 'Max Hedgehog' +}) +``` + +### Dart + +```dart +await Posthog().identify( + userId: 'distinct_id', // Replace "distinct_id" with your user's unique identifier + userProperties: { + email: "max@hedgehogmail.com", // optional: set additional person properties + name: "Max Hedgehog" +}); +``` + +Events captured after calling `identify` are identified events and this creates a person profile if one doesn't exist already. + +Due to the cost of processing them, anonymous events can be up to 4x cheaper than identified events, so it's recommended you only capture identified events when needed. + +## How identify works + +When a user starts browsing your website or app, PostHog automatically assigns them an **anonymous ID**, which is stored locally. + +Provided you've [configured persistence](/docs/libraries/js/persistence.md) to use cookies or `localStorage`, this enables us to track anonymous users – even across different sessions. + +By calling `identify` with a `distinct_id` of your choice (usually the user's ID in your database, or their email), you link the anonymous ID and distinct ID together. + +Thus, all past and future events made with that anonymous ID are now associated with the distinct ID. + +This enables you to do things like associate events with a user from before they log in for the first time, or associate their events across different devices or platforms. + +Using identify in the backend + +Although you can call `identify` using our backend SDKs, it is used most in frontends. This is because there is no concept of anonymous sessions in the backend SDKs, so calling `identify` only updates person profiles. + +## Best practices when using `identify` + +### 1\. Call `identify` as soon as you're able to + +In your frontend, you should call `identify` as soon as you're able to. + +Typically, this is every time your **app loads** for the first time, and directly after your **users log in**. + +This ensures that events sent during your users' sessions are correctly associated with them. + +You only need to call `identify` once per session, and you should avoid calling it multiple times unnecessarily. + +If you call `identify` multiple times with the same data without reloading the page in between, PostHog will ignore the subsequent calls. + +### 2\. Use unique strings for distinct IDs + +If two users have the same distinct ID, their data is merged and they are considered one user in PostHog. Two common ways this can happen are: + +- Your logic for generating IDs does not generate sufficiently strong IDs and you can end up with a clash where 2 users have the same ID. +- There's a bug, typo, or mistake in your code leading to most or all users being identified with generic IDs like `null`, `true`, or `distinctId`. + +PostHog also has built-in protections to stop the most common distinct ID mistakes. + +### 3\. Reset after logout + +If a user logs out on your frontend, you should call `reset()` to unlink any future events made on that device with that user. + +This is important if your users are sharing a computer, as otherwise all of those users are grouped together into a single user due to shared cookies between sessions. + +**We strongly recommend you call `reset` on logout even if you don't expect users to share a computer.** + +You can do that like so: + +PostHog AI + +### Web + +```javascript +posthog.reset() +``` + +### iOS + +```swift +PostHogSDK.shared.reset() +``` + +### Android + +```kotlin +PostHog.reset() +``` + +### React Native + +```jsx +posthog.reset() +``` + +### Dart + +```dart +Posthog().reset() +``` + +If you *also* want to reset the `device_id` so that the device will be considered a new device in future events, you can pass `true` as an argument: + +Web + +PostHog AI + +```javascript +posthog.reset(true) +``` + +### 4\. Person profiles and properties + +You'll notice that one of the parameters in the `identify` method is a `properties` object. + +This enables you to set [person properties](/docs/product-analytics/person-properties.md). + +Whenever possible, we recommend passing in all person properties you have available each time you call identify, as this ensures their person profile on PostHog is up to date. + +Person properties can also be set being adding a `$set` property to a event `capture` call. + +See our [person properties docs](/docs/product-analytics/person-properties.md) for more details on how to work with them and best practices. + +### 5\. Use deep links between platforms + +We recommend you call `identify` [as soon as you're able](#1-call-identify-as-soon-as-youre-able), typically when a user signs up or logs in. + +This doesn't work if one or both platforms are unauthenticated. Some examples of such cases are: + +- Onboarding and signup flows before authentication. +- Unauthenticated web pages redirecting to authenticated mobile apps. +- Authenticated web apps prompting an app download. + +In these cases, you can use a [deep link](https://developer.android.com/training/app-links/deep-linking) on Android and [universal links](https://developer.apple.com/documentation/xcode/supporting-universal-links-in-your-app) on iOS to identify users. + +1. Use `posthog.get_distinct_id()` to get the current distinct ID. Even if you cannot call identify because the user is unauthenticated, this will return an anonymous distinct ID generated by PostHog. +2. Add the distinct ID to the deep link as query parameters, along with other properties like UTM parameters. +3. When the user is redirected to the app, parse the deep link and handle the following cases: + +- The mobile app is already authenticated. In this case, call [`posthog.alias()`](/docs/libraries/js/features.md#alias) with the distinct ID from the web. This associates the two distinct IDs as a single person. +- The mobile app is unauthenticated. In this case, call [`posthog.identify()`](/docs/libraries/js/features.md#identifying-users) with the distinct ID from the web so pre-login mobile events stay connected to the web session. When the user later logs in on mobile, call `identify()` again with your canonical user ID. + +As long as you associate the distinct IDs with `posthog.identify()` or `posthog.alias()`, you can track events generated across platforms. + +Here's an example implementation for handling deep links from web to mobile: + +PostHog AI + +### iOS + +```swift +import PostHog +class DeepLinkIdentityManager { + static let shared = DeepLinkIdentityManager() + // MARK: - Deep Link Received + func handleDeepLink(_ url: URL, isAuthenticatedOnMobile: Bool) { + guard let webDistinctId = URLComponents(url: url, resolvingAgainstBaseURL: true)? + .queryItems?.first(where: { $0.name == "ph_distinct_id" })?.value else { + return + } + if isAuthenticatedOnMobile { + // The mobile app already knows the current user. + // Alias the incoming web distinct ID to that user. + PostHogSDK.shared.alias(webDistinctId) + } else { + // Reuse the web distinct ID until login on mobile. + PostHogSDK.shared.identify(webDistinctId) + } + } + // MARK: - Login/Signup + func handleLogin(canonicalUserId: String) { + // Switch from the web distinct ID (or a mobile anon ID) + // to your canonical user ID. + PostHogSDK.shared.identify(canonicalUserId) + // Set user properties, track signup event, etc. + } + func handleLogout() { + PostHogSDK.shared.reset() + } +} +``` + +### Android + +```kotlin +import android.net.Uri +import com.posthog.PostHog +object DeepLinkIdentityManager { + // Deep Link Received + fun handleDeepLink(uri: Uri, isAuthenticatedOnMobile: Boolean) { + val webDistinctId = uri.getQueryParameter("ph_distinct_id") ?: return + if (isAuthenticatedOnMobile) { + // The mobile app already knows the current user. + // Alias the incoming web distinct ID to that user. + PostHog.alias(webDistinctId) + } else { + // Reuse the web distinct ID until login on mobile. + PostHog.identify(webDistinctId) + } + } + // Login/Signup + fun handleLogin(canonicalUserId: String) { + // Switch from the web distinct ID (or a mobile anon ID) + // to your canonical user ID. + PostHog.identify(canonicalUserId) + // Set user properties, track signup event, etc. + } + fun handleLogout() { + PostHog.reset() + } +} +``` + +## Further reading + +- [Identifying users docs](/docs/product-analytics/identify.md) +- [How person processing works](/docs/how-posthog-works/ingestion-pipeline.md#2-person-processing) +- [An introductory guide to identifying users in PostHog](/tutorials/identifying-users-guide.md) + +### Community questions + +Ask a question + +### Was this page useful? + +HelpfulCould be better \ No newline at end of file diff --git a/apps/landing/.env.development b/apps/landing/.env.development index e48ae1a..1bd5164 100644 --- a/apps/landing/.env.development +++ b/apps/landing/.env.development @@ -1 +1,3 @@ API_URL=http://localhost:3333 +PUBLIC_POSTHOG_PROJECT_TOKEN=phc_yPtTBc6cXyTS8mQVYbYze5fDoRWHD3Cy5iRdn9AR56x8 +PUBLIC_POSTHOG_HOST=https://eu.i.posthog.com diff --git a/apps/landing/.env.example b/apps/landing/.env.example index bce9521..d6dfbe2 100644 --- a/apps/landing/.env.example +++ b/apps/landing/.env.example @@ -2,3 +2,8 @@ # En dev local : http://localhost:3333 # En prod (K3s ConfigMap) : https://app.rubis.pro API_URL=http://localhost:3333 + +# PostHog — token public exposé au client (préfixe PUBLIC_ obligatoire en +# Astro pour qu'il soit inliné dans le bundle browser). +PUBLIC_POSTHOG_PROJECT_TOKEN= +PUBLIC_POSTHOG_HOST=https://eu.i.posthog.com diff --git a/apps/landing/posthog-setup-report.md b/apps/landing/posthog-setup-report.md new file mode 100644 index 0000000..7b900fb --- /dev/null +++ b/apps/landing/posthog-setup-report.md @@ -0,0 +1,50 @@ + +# PostHog post-wizard report + +The wizard has completed a deep integration of PostHog analytics into the Rubis landing page (`apps/landing`, Astro 6 SSR). + +## What was done + +- **`src/components/posthog.astro`** — PostHog client-side snippet component, initialised from env vars, injected into all pages via the shared layout. +- **`src/lib/posthog-server.ts`** — Server-side PostHog singleton (posthog-node), ready for use in any future API routes. +- **`src/layouts/Layout.astro`** — Added `` component to `` so all pages (home, blog, legal, changelog) are covered. +- **`src/pages/index.astro`** — ` diff --git a/apps/landing/src/layouts/Layout.astro b/apps/landing/src/layouts/Layout.astro index 9869cd3..96d5423 100644 --- a/apps/landing/src/layouts/Layout.astro +++ b/apps/landing/src/layouts/Layout.astro @@ -13,6 +13,7 @@ import "../styles/app.css"; import { SiteHeader } from "../components/SiteHeader"; import { SiteFooter } from "../components/SiteFooter"; +import PostHog from "../components/posthog.astro"; /** * URLs hashées (au build) des deux woff2 latin que la quasi-totalité du @@ -148,6 +149,8 @@ const jsonLdArray = jsonLd ? (Array.isArray(jsonLd) ? jsonLd : [jsonLd]) : []; +