Weekly feature adoption report from Amplitude to Notion
Every Monday morning, an AI product analyst reads last week's Amplitude usage, writes a narrative per launched feature, and files it in your Notion product review database.
Amplitude
NotionProductAI ReportsResearch & MonitoringEvery Monday at 9am (operator-configurable timezone), generate a written feature-adoption report for our recently launched features and drop it into a Notion database as a new page. Trigger: cron. Integrations: Amplitude and Notion.
Let the operator configure: (1) a list of feature event names to track (or a single event category), (2) the ordered funnel steps that represent activation for those features (2 to 4 events), (3) the target Notion database ID where the report page should be created, and (4) the Amplitude user property to segment by, such as plan tier or platform. Provide sensible defaults but treat these as first-class inputs.
For date ranges, compute three windows in Amplitude Dashboard format (YYYYMMDD with no separators): last week (the seven days ending yesterday), the week before that, and the week before that. The two prior weeks are the trajectory baseline.
For EACH configured feature event, call Amplitude Get Event Segmentation Data for last week, broken down by the configured user property (plan tier or platform). Then call Amplitude Get Event Segmentation Data for each of the two prior weeks so you can compare totals and detect trajectory (growing, flat, declining). Also call Amplitude Get Funnel Analysis Data once per feature using the operator-supplied funnel step sequence over last week to compute activation conversion, and again for the prior week to see if the funnel is improving or getting worse.
Synthesize a short adoption narrative for each feature (roughly 4 to 6 sentences): who is using it (top segments by the configured property), who isn't (segments with near-zero usage or a sharp drop-off in the funnel), whether the activation funnel is converting (cite the last-week conversion rate and the delta vs the prior week), the two-week trajectory, and ONE concrete follow-up action a PM could take this week (for example: reach out to the underperforming segment, tighten the empty state on the drop-off step, or promote the feature to power users who haven't tried it).
Then call Notion Create a Page under the operator-configured Product Reviews database. Title the page with the ISO week (for example 'Feature adoption — 2026-W28'). In the page body, include one section per feature with: the narrative, a small table of last-week totals broken down by segment, the funnel conversion rate with the week-over-week delta, and the follow-up action. Add a short executive summary at the top listing which features are trending up, which are flat, and which need attention.
Notes for the agent: Amplitude Dashboard date parameters are strict YYYYMMDD with no dashes. If a feature event has zero volume across all three weeks, still include a one-line entry in the report noting no signal was captured — do not silently omit it. If the funnel returns fewer than the expected step counts, flag the gap explicitly in that feature's narrative rather than fabricating a conversion number.
Additional information
What does this prompt do?
- Every Monday morning, checks last week's usage in Amplitude for the features you're tracking.
- Compares each feature against the two prior weeks so you can see whether adoption is climbing, flat, or slipping.
- Breaks usage down by your chosen dimension (plan tier, platform, or any user property) so you can spot which segments are engaging.
- Runs your activation funnel for each feature and reports whether users are actually converting through it.
- Writes a short narrative per feature with a concrete follow-up action and saves the whole thing as a new page in your Notion product review database, titled with the ISO week.
What do I need to use this?
- An Amplitude account with the feature events you want to track already firing.
- The list of feature event names and the funnel steps that represent activation for each one.
- A Notion workspace with a database where the weekly reports should be filed (for example, a 'Product Reviews' database).
- The user property in Amplitude you want to segment by, such as plan tier or platform.
How can I customize it?
- Change the day and time the report runs, or add a second run mid-week for hotter launches.
- Add or remove feature events, and adjust the funnel steps as your activation definition evolves.
- Swap the segmentation dimension between plan tier, platform, country, or any custom user property you already track.
- Point the workflow at a different Notion database or change the page title format if you prefer a different naming convention.
Frequently asked questions
Do I need to write any queries or dashboards ahead of time?
Can it track more than one feature at once?
What if a feature has no usage yet?
Can I use a different segmentation, like country or device instead of plan tier?
Where does the report actually land?
Related templates
Stop letting feature launches go quiet after week one.
Automate the Monday morning 'how is X doing?' question so every launched feature gets a written check-in in Notion.