TrackStack Docs
TrackStack Docs
DashboardPricingTrackStack DocsQuickstartExamplesSDK SetupB2B SaaS EventsEvent Payload ContractPlatform Event MappingRouting PolicySupported Platforms
IntegrationsSSO & Event Capture
API Playground
GitHub
Integrations

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, Configure for destinations.

Source integrations

  • PostHog — Native. TrackStack proxies PostHog via first-party /_ph. Use posthog in 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.

PlatformIDStatus
Meta (Facebook)meta✅
Google Ads / GA4google✅
LinkedInlinkedin✅
Redditreddit✅
TikToktiktok✅
X (Twitter)x✅
Microsoft AdsmicrosoftUET
Quoraquora✅

Auth and SSO

SDK identity helpers standardize identify() after your users sign in — including SAML/OIDC enterprise SSO. See the dedicated guide:

  • SSO & identify after login — dashboard Clerk SSO, customer app SSO, env vars, and capture patterns
ProviderComponentPackage path
ClerkTrackStackClerkIdentify@trackstack/sdk/react-clerk
Auth0TrackStackAuth0Identify@trackstack/sdk/react-auth0
NextAuth / Auth.jsTrackStackNextAuthIdentify@trackstack/sdk/react-nextauth
Better AuthTrackStackBetterAuthIdentify@trackstack/sdk/react-better-auth
Supabase AuthTrackStackSupabaseIdentify@trackstack/sdk/react-supabase
Firebase AuthTrackStackFirebaseIdentify@trackstack/sdk/react-firebase

See SDK setup for wiring. These helpers do not require platform-level destination config.

Payments

SystemTrackStack surfaceStatusSystem docs
StripeEdge webhook endpoint POST /stripeIn 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

Integration areaPersistent storageNotes
Source integrations (PostHog, etc.)D1 apikey.metadata.integrationsPer-key config; secrets redacted on read
Edge API key and auth runtimeD1 apikey, users, sessions, accounts, verificationsKey validation and edge auth/session lifecycle
Edge delivery reliabilityD1 dedup, rate_limitDedup and delivery controls
Clerk webhook ingestionSupabase clerk.events, clerk.users, clerk.organizations, clerk.organization_memberships, clerk.sessionsPOST /api/webhooks/clerk stores raw events and entity projections
App profile + subscription stateSupabase public.app_users, public.app_subscriptionsIncludes Stripe reference fields
Auth0 / NextAuth / Better Auth / Supabase Auth / Firebase AuthNo required first-party table in TrackStack by defaultSDK identify helpers only; persist to your app DB as needed

Supported Platforms

Conversion destination coverage, common mappings, and override patterns.

SSO & Event Capture

Dashboard SSO, customer app identify after SSO, and the full send-and-catch configuration checklist.

On this page

Source integrationsDestination platforms (CAPI)Auth and SSOPaymentsFrameworksDB structure and persistence footprint