↻ Integrations
Works with what you already run.
Trevo reads your funnel from the analytics tool you already trust, and writes experiments into the repo through the GitHub App. Nothing here asks you to move your data or replace a tool.
Where your data comes in
Read-only connectors. Trevo pulls the catalog it needs to ground a proposal — events, funnels, flags, experiment history — and never writes back.
Analytics
PostHogPull events, funnels & experiments.
AmplitudePull your event taxonomy, plus flags & experiments.
MixpanelPull events & saved funnels.
Web analytics
Google Analytics 4Read key events and audiences from a GA4 property.
CDP
SegmentPull your tracking plan and forward live events.
Feature flags
LaunchDarklyRead live flags, experiments & segments.
Experimentation
StatsigRead gates, experiments & metric lineage.
GrowthBookRead features, experiments & metric lineage.
Billing
StripeBilling health: MRR, subscriptions, refunds, disputes.
Advertising
Meta AdsJoin campaign spend to activated users.
Google AdsJoin campaign spend to activated users.
Where experiments go out
One GitHub App, scoped to the repositories you pick. It reads your default branch and opens pull requests on trevo/* branches — never on main, and never a deploy.
Runtimes the SDK supports
Next.jsMiddleware + server components
ReactuseExperiment hook
React NativeSame client, native storage
NodeServer-side assignment
PythonSync, deterministic client
Ruby / RailsController-friendly client
BrowserZero-flicker, no DOM injection
VercelEdge-cached config
Missing the one you use?
Trevo works without any connector — the SDK sends its own events. A connector only saves you re-instrumenting what another tool already measures.