# Connecting Amplitude

> Measure outcomes from your Amplitude events: connect the project with its API key and secret key, then pick events for an outcome's primary metric and guardrails.

Source: https://productos.ca/documentation/guides/integrations/amplitude (last reviewed 2026-10-08)

> **Preview**
>
> Measuring outcomes from Amplitude is in preview. If Amplitude still shows as coming soon in Settings, Integrations, it isn't turned on for your workspace yet.

Amplitude connects with your project's API key and secret key. ProductOS reads your events, never writes to Amplitude, and uses them to measure [outcomes](https://productos.ca/documentation/pages/golden-thread/outcomes): how an event moved after a release compared with before it.

## What it does

- **Event list.** When you measure an outcome's metric, you pick the event from your project's own list, busiest first, with this week's total. Nothing is typed by hand, so a renamed or misspelled event can't slip in.
- **Daily numbers.** For each measured metric, ProductOS reads the event's count per day (**Events per day**) or the people who did it per day (**Users per day**), from the start of the baseline window to yesterday.
- **Baseline and actual.** The baseline is the mean per day over the days before the release; the actual is the mean per day since it. Means per day let a measurement that is ten days in compare fairly with a 28-day baseline.
- **Daily refresh.** Every morning (07:05 UTC) ProductOS fetches each measured metric again, so a day Amplitude corrects is corrected here too. A week after a metric's measurement window ends, its numbers are final and it stops refreshing.
- **Sync now** on the Amplitude card refreshes every measured metric in the workspace at once.

## Connecting

1. In Amplitude, open **Settings → Organization settings → Projects**, pick the project, and stay on **General**. The **API Key** and **Secret Key** are in the Project Details table; only managers and admins can reveal the secret key.
2. In ProductOS, **Settings → Integrations → Amplitude → Connect**. Paste both keys and pick the **Data region**: US, or EU for projects hosted at analytics.eu.amplitude.com. Then **Connect & test**. The test lists your project's events and shows how many it found.
3. Open an outcome and choose **Measure from Amplitude**, or add a guardrail measured from Amplitude.

Both keys are stored encrypted. Only owners and admins can connect or disconnect Amplitude; any member can measure an outcome once it is connected.

## Windows

| Setting | Default | Choices |
| :--- | :--- | :--- |
| Baseline before the release | 28 days | 7, 14, 28, 56 or 90 |
| Measure after the release | 28 days | 7, 14, 28, 56 or 90 |

The release date is the outcome's **Released** date, else its release's date, else the day you added the metric. Changing the event, what it counts or a window fetches the history again.

## Limits

- Events per day and users per day. Conversion between two events and retention are planned.
- A metric reads the whole project. Filtering by an event property (for example one workspace or one plan) is planned.
- Days follow UTC; Amplitude reports in your project's time zone, so the most recent day can shift slightly and is corrected the next morning.
- ProductOS stays inside Amplitude's rate limits by fetching one metric at a time. A refresh that hits the limit says so on the metric and tries again the next day.

## Disconnecting

**Settings → Integrations → Amplitude → remove**. Measured metrics keep their last numbers and show that Amplitude isn't connected until you connect it again.

## Next

- [Outcomes](https://productos.ca/documentation/pages/golden-thread/outcomes): primary metrics, guardrails and the suggested result
- [Outcomes API reference](https://productos.ca/documentation/api/v1/reference/outcomes): outcome metrics over the REST API