Connect Amplitude

Before you start

You'll need workspace admin role in Findry and at least Member role in your Amplitude organization (the role that lets you view and create API keys). The connection is one-time per workspace; every Findry project in that workspace shares it.

Amplitude doesn't use a project ID in its API — your credentials are already scoped to a single project. Unlike PostHog, there's no separate project ID field; you just pick a region and paste both keys.

Findry stores both keys encrypted at rest (AES-256-GCM) using the same column slots as other integrations. Only the adapter layer ever decrypts them — never the UI, never the audit log.

Create credentials

Amplitude requires both an API Key and a Secret Key. They are paired — they come from the same project and must be used together.

1. In Amplitude: Settings → Projects → [your project] → General
2. Scroll to the API Key section. The API Key is already visible — copy it.
3. Click Reveal next to the Secret Key. Copy it now — Amplitude shows the Secret Key only once per session; once you navigate away, you'll need to regenerate it.
4. Note your datacenter region: US projects live on amplitude.com; EU projects live on analytics.eu.amplitude.com. Using the wrong region causes a 401 even with correct keys.

Connect in Findry

1. In Findry: Settings → Integrations → Amplitude tile → Connect
2. Region — choose US Cloud (default) or EU Cloud from the dropdown. This determines which Amplitude base URL the adapter calls.
3. API Key — paste the key you copied from Amplitude.
4. Secret Key — paste the Secret Key you revealed. Both fields are write-only after saving; you can see a redacted prefix but never the full value.
5. Click Save. Findry calls GET /api/2/taxonomy/categories immediately to validate three things at once: the host is reachable, the API Key is recognized, and the Secret Key is accepted. The call returns a 200 with your project's taxonomy data on success.
6. On success, the tile flips to connected and shows the project display name.

What happens next

Connection alone activates several surfaces — you don't need to configure anything else to use them:

• Annotations push defaults ON — when a bet promotes, ships, or its outcome verdict lands, Findry drops a vertical line on every Amplitude chart in the project. Toggle off in the same tile if you'd rather not.
• Cohort picker in the bet predicted-impact form starts populating from your Amplitude project's behavioral cohorts.
• The Add metric mapping form in the integrations tile becomes usable for binding metrics to Amplitude data.
• Amplitude Experiment picker in the Test form becomes available (requires a Management API key — see the Cohorts + experiments guide).

The next two things you'll likely do: (a) define a metric in Settings → Metrics and (b) map it to Amplitude data. That's covered in the next guide: Metrics + mappings.

Troubleshooting

"Amplitude rejected the API key"

The key is unrecognized. Four checks: the API Key was copied correctly (no leading/trailing whitespace), the Secret Key matches the API Key (they come from the same project — mixing keys from different projects causes this), the project hasn't been archived, and the keys haven't been regenerated in Amplitude since you copied them.

"Wrong region / 401 with correct keys"

A US project key submitted to the EU endpoint (or vice versa) returns a 401 with no other indication. Verify your Amplitude project's region in Settings → Projects → [your project] → General — it shows "US" or "EU" explicitly. Switch the Findry region dropdown to match.

"Couldn't reach Amplitude: network timeout"

Your Amplitude project is on a self-hosted or custom domain that isn't publicly reachable. Findry's adapter calls Amplitude from Vercel's infrastructure — it doesn't run inside your VPC. US Cloud and EU Cloud are the only supported regions; custom hosts aren't supported yet.

"429 Too Many Requests"

The validation call was rate-limited. This is unusual for a single GET — it more commonly means your Amplitude plan has restrictive rate limits on the taxonomy endpoint. Wait 60 seconds and retry. If it persists, check whether a batch job is hammering the same endpoint concurrently.

Disconnect cleanly

Settings → Integrations → Amplitude tile → Disconnect. Findry zeros out both encrypted tokens and flips the row to disconnected_at = now().

What survives disconnect (intentional):

• Annotations already pushed to Amplitude — Findry never deletes external state on its own state changes. The annotations stay as historical context on your Amplitude charts.
• Mapping configurations — the rows stay. If you reconnect the same Amplitude project, mappings resume automatically. If you reconnect a different project, outcome runs will report "event not recognized" warnings until you update the mappings.
• Experiment links — Tests linked to Amplitude Experiments retain the link. The nightly sync stops firing until reconnected.

What stops working: outcome metric pulls, annotations push, cohort and experiment pickers, nightly experiment sync. All gracefully return empty / no-op rather than crash.