Amplitude

Product usage counts and saved charts. Read-only.

Connects with	API key and secret key
Reads	6 operations
Writes	None
Irreversible	None
Personal data	None. Every operation returns an aggregate.
Data stays in	AWS Sydney (ap-southeast-2)

What it reads

• The event types the project has seen, with weekly totals and unique users.
• Event counts over a date window, optionally broken down by a property.
• Active and new users over a window.
• Average session length per day.
• The composition of the active user base by one property: plan, platform, country.
• The results of a chart your team already built and saved.

What it does not read

Raw events and individual user profiles. Every operation returns an aggregate.

What it writes

Nothing. There are no write operations in this connector.

How you connect it

Connect with the project’s API key and secret key. In Amplitude, open Settings, then Projects, then your project. The API key is the one that also appears in your site’s tracking snippet; the secret key is shown beside it.

What StoriBot will ask for

• The data centre the project lives in: US or EU. A key issued for one is not valid in the other.
• The API key.
• The secret key.

Every operation

These are the names the Integrations page shows beside each tick box, in the order it lists them. Generated from the connector registry; do not edit by hand.

All 6 operations

Operation	Kind	What it does
list_events	Read	List the event types the project has seen, each with its weekly totals, unique users and share of daily active users.
event_segmentation	Read	Count one event over a date window, optionally broken down by a property.
active_and_new_users	Read	Count active or newly acquired users over a date window.
average_session_length	Read	Average session length in seconds for each day in a window.
user_composition	Read	Break the active user base down by one property, as a share of the whole, what proportion are on each plan, platform or country.
chart_results	Read	Fetch the results of a chart the customer already built and saved, with the events, segments and date range they chose.