Zentrik + Amplitude

Amplitude is the evidence source. Zentrik turns each saved product question into a fixed aggregate measurement, checks it on a schedule, and keeps one durable Insight current as the result changes.

Use the Insight in an idea or brief when the evidence should change product work. Zentrik does not infer a cause or change an active measurement between runs.

A workspace owner or admin can connect Amplitude. You need the project's API key and secret key, which an Amplitude admin can copy from the project's settings (find your API and secret keys).

1. Open Settings → Integrations → Connections and select Amplitude.
2. Choose the region your Amplitude project stores data in: United States or European Union.
3. Paste the project's API key and Secret key, then save.
4. Select Ask a question to open Imports.

Zentrik checks the keys by reading the project's event list before it saves them. The secret key is encrypted at rest and is never shown again. One Amplitude project connects to a workspace; to use another project, replace the keys.

1. Select New question.
2. Ask about one tracked behavior, such as Are more users completing onboarding each week?, or about an ordered process, such as How well does our onboarding flow convert? Use the name of a behavior or process that your project already records.
3. Choose a daily or weekly check.
4. Select Define measurement. For a single behavior, review the exact Amplitude event, measure, audience, and comparison. For a process, review the ordered steps Zentrik matched from your project's real events.
5. If Zentrik cannot match the question safely, choose the correct event from the project's event list.
6. Select Preview result. Save the question only when the result has enough evidence for your decision.

A single-behavior question reads event totals or unique users for each complete day or week, using Amplitude's event segmentation. A process question becomes an ordered funnel of two to six events, read with Amplitude's funnel analysis: the people who reached the first step in a 30-day window ending 14 days before the check, compared with the 30 days before it. A funnel needs at least 20 people at the first step and 5 at the last before Zentrik reports a result.

• Current Insight shows the newest supported result and evidence window.
• Evidence history keeps the result from each run.
• Use in an idea carries the Insight into product work.
• Pause stops scheduled checks without deleting the question or its history.

If a user rejects the Insight, Zentrik removes it from active product context and later runs do not recreate it.

• Zentrik reads the project's event list: event names, display names and this week's totals. It does not read user properties, cohorts or saved charts.
• Zentrik reads aggregate results through Amplitude's Dashboard REST API: event totals, unique users and funnel step counts.
• Zentrik stores aggregate measurements, evidence windows, versions, and safe run receipts. It does not copy raw events, people, or session replays.
• Day and week periods follow the project's timezone in Amplitude; weeks start on Sunday.
• A model can map the initial question to one event or to an ordered sequence of events from the project's event list. It cannot invent an event, calculate the result, or rewrite an active query.
• Disconnecting removes the saved keys. Saved questions and their Insights stay in Zentrik.