Connect Amplitude
Connect an Amplitude project so Adduce computes its own trends, retention and funnel drop-offs from your event export every day.
Adduce reads your Amplitude event export, computes its own trends, retention and funnel drop-offs from it, and watches the recordings behind the worst drops.
Before you begin
- Role: project Editor or Lead. A workspace Admin is a lead on every project.
- In Amplitude: a project whose API key and secret key you can read, on a plan whose Export API you can call.
- To hand: the data region your project is hosted in, the project API key, and the secret key.
- Time: five minutes.
What Adduce reads
| Surface | What it becomes |
|---|---|
| The event export | Weekly active users, cohort retention, and per-event trends |
| Week-on-week changes | Evidence naming the event that moved and by how much; a drop is a pain point |
| Funnels you define in Adduce | Evidence naming the step people leave at, and the share who do |
| Session replays behind a drop-off | A short written account of what the person actually did, linking back to the player |
Raw events are never stored. Each sync streams six-hour chunks of the export, folds them into counts, and discards the events. At most ten recordings are summarised per sync.
Permissions the keys need
| Credential | Why |
|---|---|
| Project API key | identifies the Amplitude project |
| Secret key | pairs with the API key to authorise the export and replay reads |
Together the pair grants full read access to that one project — Amplitude has no narrower key. Nothing is written back: Adduce only reads.
Steps
In Amplitude, open Settings → Projects and choose your project. Copy the API Key and the Secret Key from the same page, and note which region the project is hosted in.
In Adduce, open the project, choose Sources, then Add source.
Choose the Amplitude tile.
On Connection details, name the source, pick the Data region, and paste both keys.
Choose Continue. Adduce calls Amplitude with the pair before saving anything, so a key from the other region is refused here rather than at the first sync.
Back on Sources, the new row shows Connected, and it will show a count once the first sync has run.
Once the first sync has read some events, open the source and use Funnels to define the journeys you care about. Each one becomes its own evidence on every later sync. Until that first sync lands there is nothing to pick from, and the panel says so.
First sync and cadence
The first sync reads the last ninety days of the export, in six-hour chunks, and stops three hours short of now — Amplitude takes a couple of hours to make events exportable. A large backfill takes several runs; each chunk is remembered, so an interrupted sync resumes rather than restarting. After the backfill Adduce syncs once a day at 03:00 UTC, and Sync now runs one immediately.
Adding or editing a funnel makes Adduce re-walk the export window for that funnel alone.
Disconnect or replace credentials
Delete the source from its page and type its name to confirm. Deleting removes the evidence it produced, and the funnels defined on it. To rotate keys, delete the source and add it again; the next sync backfills ninety days afresh.
If it did not work
Why were my keys rejected?
Either a key is wrong, or the Data region does not match where the project is hosted. Adduce calls the region you picked and nothing else, so an EU project with the US region selected fails with the same message a bad key gives. Check Settings → Projects in Amplitude for both.
Why has the first sync been running for so long?
A ninety-day export is large and arrives in chunks. The Sync panel on the source page shows each run; as long as runs keep completing, the backfill is progressing.
Why is the Funnels panel empty?
Funnel steps are chosen from the events the export has already delivered, so there is nothing to pick until the first sync lands. The panel says so until then.