Guides

Connect Amplitude

VocxAI reads small aggregate summaries from the events and saved charts you choose. It does not download Amplitude's raw event export or store individual user event histories.

What becomes a signal? A sustained, material change such as “Weekly users of CSV export decreased 31%, from 820 to 566.” Normal daily variation is retained only as a short-lived metric snapshot and does not become customer evidence.

1. Find your project credentials

Open the Amplitude project

In Amplitude, choose the production project you want VocxAI to monitor. Open the project's settings and locate its Project ID, API key, and Secret key.

Confirm the data region

Choose United States unless the project uses Amplitude's EU data centre. VocxAI uses the region only to select the correct Amplitude API host.

Treat the secret key like a password. VocxAI encrypts both keys and never displays them again after saving.

2. Choose what is worth monitoring

Start with 5–20 product behaviours that have clear product meaning. Good candidates include:

Activation milestones such as completing setup or inviting a teammate.
Core feature use such as exporting a report or publishing a dashboard.
Failure events such as an import, integration, or payment failure.
Saved funnels for activation or onboarding completion.
Saved retention or session charts used as trusted product KPIs.

Avoid generic events such as page views, button clicks, heartbeats, and events whose meaning is unclear outside the tracking implementation.

3. Connect in VocxAI

Go to Settings → Connectors and click Connect on Amplitude.
Enter the Project ID, API key, secret key, and data region.
Add exact event names, one per line. You can add | adoption, | success, | failure, or | activation after an event name to label the resulting evidence.
Optionally add saved chart IDs. The chart ID is the final identifier in an Amplitude chart URL; add — Friendly name after it to control the signal wording.
Set the comparison window, minimum population, and percentage-change threshold.
Click Connect. VocxAI validates the credentials and starts the first aggregate sync.

4. Tune the thresholds

Setting	Recommended starting point	Purpose
Window	7 days	Compares the latest completed period with the preceding equivalent period.
Minimum users	20	Suppresses large percentages caused by tiny samples.
Change threshold	20%	Requires a meaningful increase or decrease before creating a signal.

VocxAI excludes the current incomplete day, creates at most ten ranked observations in one sync, and applies a 14-day cooldown to the same monitor, segment, and direction. Repeated syncs therefore do not create duplicate signals.

5. Attribute usage to accounts and ARR

If your Amplitude project records a company or workspace identifier as a user property, enter it as the Account/group property. Custom user properties use Amplitude's gp: prefix. Use a value that can be matched to HubSpot: gp:hubspot_company_id (or gp:company_id/gp:account_id) for the HubSpot company record ID, a property ending in domain for the company domain, or gp:company_name for a normalized company name.

VocxAI creates aggregate observations for the returned account groups and matches them to HubSpot by the selected identifier. Saved charts need to include the account property as a breakdown in Amplitude. Do not use an email address or another personal identifier.

Data handling

VocxAI calls Amplitude's aggregate Dashboard APIs for selected event totals, unique users, group breakdowns, and saved-chart results. It stores 90 days of compact metric snapshots for comparisons. It does not call the raw Export API, copy the event warehouse, or retain individual Amplitude users.

Only an observation that crosses the configured population and change thresholds becomes a Product usage signal. Those signals use the same clustering and theme workflow as feedback from other connectors while remaining a separate evidence type.

Managing the connection

Use Edit monitors on the connected Amplitude card to add or remove events and charts or change thresholds. Use Sync now to run the same process as the scheduled background sync. Disconnecting stops future queries; existing product-usage signals remain as historical evidence.