Integrations
Analytics, auth, payments, and frameworks TrackStack works with.
TrackStack integrates with your existing stack. One event contract flows to ad platforms, analytics, and optional webhooks.
Source integrations (e.g. PostHog) feed events into TrackStack. Destination platforms (Meta, Google, etc.) receive routed conversions. Configure both in the dashboard: Integrations for sources, Platforms for destinations.
Source integrations
- PostHog — Native. TrackStack proxies PostHog via first-party
/_ph. Useposthogin SDK config. Configure in Settings → Integrations. - GA4 — Receives events via Google CAPI adapter (destination platform).
- Amplitude / Mixpanel — Use PostHog destinations or capture alongside TrackStack.
Destination platforms (CAPI)
TrackStack routes to Meta, Google, LinkedIn, Reddit, TikTok, X, Microsoft Ads, and Quora. See Supported platforms for IDs, mapping targets, and override patterns.
| Platform | ID | Status |
|---|---|---|
| Meta (Facebook) | meta | ✅ |
| Google Ads / GA4 | google | ✅ |
linkedin | ✅ | |
reddit | ✅ | |
| TikTok | tiktok | ✅ |
| X (Twitter) | x | ✅ |
| Microsoft Ads | microsoft | UET |
| Quora | quora | ✅ |
Auth and sign-on providers (SDK identity helpers)
| Provider | Component | Package path | Provider docs |
|---|---|---|---|
| Clerk | TrackStackClerkIdentify | @trackstack/sdk/react-clerk | Clerk docs |
| Auth0 | TrackStackAuth0Identify | @trackstack/sdk/react-auth0 | Auth0 docs |
| NextAuth / Auth.js | TrackStackNextAuthIdentify | @trackstack/sdk/react-nextauth | Auth.js docs |
| Better Auth | TrackStackBetterAuthIdentify | @trackstack/sdk/react-better-auth | Better Auth docs |
| Supabase Auth | TrackStackSupabaseIdentify | @trackstack/sdk/react-supabase | Supabase Auth docs |
| Firebase Auth | TrackStackFirebaseIdentify | @trackstack/sdk/react-firebase | Firebase Auth docs |
See SDK setup for wiring. These helpers standardize identify() from your existing session provider; they do not require a platform-level destination config.
Payments
| System | TrackStack surface | Status | System docs |
|---|---|---|---|
| Stripe | Edge webhook endpoint POST /stripe | In progress (signature check is live; event mapping pipeline is scaffolded) | Stripe webhooks |
Frameworks
- Next.js —
withTrackStack(), PostHog proxy, App Router. - React — Provider, hooks, pageview.
- Vite — SPA with
VITE_TRACKSTACK_KEY.
DB structure and persistence footprint
Use this section to understand what is persisted today versus SDK-only integration helpers.
| Integration area | Persistent storage | Notes |
|---|---|---|
| Source integrations (PostHog, etc.) | D1 apikey.metadata.integrations | Per-key config; secrets redacted on read |
| Edge API key and auth runtime | D1 apikey, users, sessions, accounts, verifications | Key validation and edge auth/session lifecycle |
| Edge delivery reliability | D1 dedup, rate_limit | Dedup and delivery controls |
| Clerk webhook ingestion | Supabase clerk.events, clerk.users, clerk.organizations, clerk.organization_memberships, clerk.sessions | POST /api/webhooks/clerk stores raw events and entity projections |
| App profile + subscription state | Supabase public.app_users, public.app_subscriptions | Includes Stripe reference fields (stripe_customer_id, stripe_subscription_id) |
| Auth0 / NextAuth / Better Auth / Supabase Auth / Firebase Auth | No required first-party table in TrackStack by default | SDK identify helpers only; persist to your app DB as needed |
Full integration list: INTEGRATIONS.md