---
title: "Run Togo alongside PostHog, Mixpanel or Amplitude"
description: "Keep the analytics tool you have, send the same events to Togo, and remove nothing until you are ready."
canonical: "https://www.togohq.ai/docs/alongside"
applies_to: "@togohq/sdk-browser 1.x, @togohq/sdk-node 1.x"
updated: "2026-11-03T00:00:00Z"
---

# Run Togo alongside PostHog, Mixpanel or Amplitude

Keep the analytics tool you have, send the same events to Togo, and remove nothing until you are ready.

You do not have to switch to try Togo. Install the Togo SDK next to the one you have, call both,
and compare. Nothing about your current setup changes.

## Keep your event names

Send events to Togo under the names you already use — `Sign Up`, `checkout_completed`,
`Button Clicked`. Togo stores each name exactly as sent and gives it a stable `snake_case` key
(`Sign Up` → `sign_up`) that reports and the AI analyst use. There is no mapping file to
write: [Events and the event registry](/docs/concepts/events) explains how names become keys, and
[Event governance](/docs/concepts/governance) how to define each one as you go.

## Call both SDKs from your code

Add the Togo call beside the existing one, wherever you track:

```ts
import posthog from 'posthog-js';
import { analytics } from './analytics'; // your Togo client

export function trackSignUp(plan: string) {
  posthog.capture('Sign Up', { plan });
  analytics.track('Sign Up', { plan });
}
```

If your code already goes through one tracking helper, that helper is the only place to change.
Do the same for identity: call Togo's `identify()` and `reset()` where you call the other tool's.

## Do not forward their events

Do not pipe the other tool's events into Togo — no webhook from its pipeline, no forwarding
plugin. Their automatic events use names Togo reserves (PostHog's `$pageview`, for example, starts
with `$`) and are refused with
[`event_name_reserved`](/docs/reference/event-diagnostics#event_name_reserved). Calling Togo directly
also gets you the SDK's page context, sessions and clock correction, which a forwarded copy
loses.

## Let your agent do it

If you install with your agent ([Install Togo with your AI agent](/docs/install)), it reads the
existing PostHog, Mixpanel or Amplitude calls in your code and adds the Togo calls beside them,
defining each event as it goes.

## When to remove the old tool

When the numbers you rely on agree. Togo's live data is a few hours behind
([When your data shows up](/docs/concepts/data-freshness)), so compare whole days, not the last
hour. Removing the old SDK is then a deletion — the Togo calls are already there.