Amplitude
Bring your business data together in Amplitude, and act on it in the apps your team already uses.
13 ways to read, 3 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Amplitude, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Send events
events.sendApproval by rule - Update group properties
group_properties.updateApproval by rule - Count active or new users
active_users.listRead
Example flow
- Amplitude · Count active or new users
active_users.listDone - Amplitude · Send events
events.sendMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Amplitude.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Amplitude
- Amplitude's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Amplitude test account before you go live.
For developers
Technical detail
Amplitude: send events and user or group properties, and read event counts, active users, funnels, retention, revenue, cohorts, annotations and saved charts.
Amplitude API docs- Source actions
- 13
- Destination actions
- 3
- Data types
- 16
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
active users1
- Count active or new usersSourceIncremental
Active or new users per day, week or month, optionally split by a property.
annotations1
- List chart annotationsSourceIncremental
Lists notes your team added to charts, such as releases or campaigns, so reports can explain spikes and dips.
chart results1
- Run a saved chartSource
Returns the current results of a chart your team saved in Amplitude, using the chart's own settings and date range.
cohorts1
- List cohortsSource
Lists your saved cohorts with their size, when they were last computed and, optionally, where they sync to.
event counts1
- Count an event by daySourceIncremental
How many times (or how many users) an event happened each day, optionally split by a property such as country. Use it to check that events you sent arrived.
event types1
- List event typesSource
Lists the event types in your project's tracking plan with their descriptions.
events1
- Send eventsDestinationProvider duplicate protectionApproval before production
Records up to 500 events (for example a purchase or a sign-up) in your Amplitude project in one request.
funnels1
- Run a funnelSource
How many users went through a series of steps (for example sign up, then add to cart, then pay) and how many dropped off at each step.
group properties1
- Update group propertiesDestinationProvider duplicate protectionApproval before production
Sets, sets once or removes properties on an account or other group (Amplitude Accounts add-on).
realtime active users1
- Read live active usersSource
Active users every 5 minutes for today and yesterday, to watch a launch or campaign as it happens.
retention1
- Run a retention reportSource
Of the users who started (for example new users) on each day or week, how many came back in each following period.
revenue ltv1
- Read revenue lifetime valueSource
Revenue per user (or paying user, total revenue or paying users) for users who started each day, from Amplitude's revenue tracking.
user activity1
- Read a user's eventsSource
Lists the events one user performed, newest first, to check what Amplitude recorded for them.
user properties1
- Update user propertiesDestinationProvider duplicate protectionApproval before production
Sets, sets once or removes properties on a user (for example their plan or company) without recording a visible event.
user property definitions1
- List user propertiesSource
Lists the user properties defined in your project's tracking plan.
users1
- Find a userSource
Finds a user by Amplitude ID, User ID or Device ID and returns their Amplitude ID, for reading their activity.
Access and limits
- Authentication
- Amplitude project API key and secret key
- Plans and access
- Sending events, event counts, active users, funnels, retention, revenue, user lookups, taxonomy and annotations work on every plan. Cohorts need a Growth or Enterprise add-on; group properties need the Accounts add-on. The API key and secret key belong to one project and can read all of its data. Only admins and managers can generate a secret key, and Amplitude shows it only once.
- Test environment
- Create a separate test project in Amplitude (Settings → Projects → Create project) and connect its keys first; switch to the production project's keys when the flow is ready.
- Rate limits
- Events: under 1 MB and 2,000 events per request (Nexra sends up to 500), 30 events per second per user or device, 50,000 per second per project; 429 when throttled. Queries: 5 at a time, cost-based limits of 1,000 per 5 minutes and 108,000 per hour, user search and activity 360 per hour; 429 when exceeded. Taxonomy: 7,200 cost per hour.
- Pagination
- User activity pages by offset (up to 1,000 events per page). Other reads return one result; aggregated reads are capped at 10,000 rows and 366 days.
- Provider events
- Amplitude sends cohorts and events onward through its destination integrations and custom monitors, not through a documented webhook subscription API Nexra can use. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Intentionally excluded: the Export API (raw events as zip archives), the User Privacy API (deleting users), cohort upload, and creating, changing or deleting taxonomy entries or annotations.
- Sending events, user properties and group properties is approval-gated like other writes. Events count toward your plan's event volume.
- Duplicate protection: every event carries an insert ID (yours, or derived from the Nexra delivery). Amplitude ignores a repeat with the same insert ID and device for 7 days; include a device ID where you can.
- User and group property updates offer set, set once and remove only, so repeating an update converges. Counters and list operations ($add, $append) are not offered.
- Event types starting with $ are reserved; Nexra refuses them in Send events and uses them only for property updates.
- Aggregated reads use the project's time zone and cover up to 366 days and 10,000 rows (retention up to 92 periods). Event filters, formulas and segments beyond one group-by property are not offered; use a saved chart for those.
- Find a user refuses values that look like email addresses or phone numbers, because the search value travels in the request address.
- Saved chart results follow the chart's own settings and their shape depends on the chart type.
Developer reference
- Create the Amplitude credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Amplitude, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/amplitude and the Connections API.