How to Install Amplitude and Track Your First Event in 30 Minutes
Amplitude builds funnels, retention and path analyses from tracked events. Its Starter plan is free up to 50,000 events per month, and Growth pricing begins near $61/month, so a small product can run real analysis without a sales call.
What does Amplitude need from your app?
An SDK or an HTTP event endpoint, a user identifier, and an event naming scheme. Only one of those is a technical task. The naming scheme is the one that determines whether your data is usable in six months.
Events in Amplitude are facts: Signed Up, Completed Checkout, Invited Teammate. Properties are the detail: plan, source, amount. Confusing the two is the classic first-month error.
How do you install the SDK?
- Create the project and copy the API key from Settings → Projects.
- Install the SDK —
npm install @amplitude/analytics-browserfor web. - Initialize once per page load with
amplitude.init(API_KEY, { defaultTracking: true }). - Call
amplitude.setUserId(user.id)after login. - Fire one test event and confirm it in the Amplitude Live Events view.
defaultTracking: true covers page views, sessions and file downloads automatically. Leave it on unless you have a specific reason: it gives you baseline data while your custom events are still being defined.
Do not initialize the SDK twice. In single-page apps, re-initialising on route change creates duplicate sessions and doubles your event volume against the free tier.
How should you name the first events?
Pick a convention and write it into the repo. The two that survive: Title Case with an object-verb order (Checkout Completed), or snake_case (checkout_completed). Either works. Mixing them does not.
Rules worth enforcing from day one:
- Past tense for things that happened; no “Click Button” events.
- No user IDs, dates or dynamic values in event names.
- Properties as camelCase keys with consistent types —
plan: "team", never sometimes a number. - One event per user intent, not per UI control.
Start with five to eight events: signup, activation, first core action, invite, upgrade, churn. A five-event taxonomy beats a forty-event mess every time.
What do you check before trusting the numbers?
Three things, all in the first hour:
- Live view shows the event with your user ID attached.
- User properties populate on the profile you just touched.
- Event volume matches your server-side count for a one-hour window.
That third check catches ad-blocker losses. Browser SDKs lose 10–30% of events to blockers on consumer traffic, less on B2B. If the gap is large and your funnel decisions are revenue-critical, add server-side tracking via the HTTP API.
Is the free tier enough to start?
For a pre-launch or early product, yes — 50,000 events per month is roughly 1,500 daily active users with a dozen events each. Past that, Growth near $61/month is the next step, and pricing negotiates upward with volume.
The constraint that bites first is not events but seats. Analysts and PMs both want access, and the free tier’s limits on saved charts and cohorts are tighter than the event cap suggests. Check Amplitude‘s current plan matrix before you plan a team rollout.
How does Amplitude compare with the alternatives?
Against PostHog: PostHog wins on price and on having replay and flags in the same product; Amplitude wins on analysis depth, especially retention and pathfinding.
Against Pendo: Pendo bolts guides onto analytics; Amplitude does not do guides at all. If you need both, that is two bills.
Against Hotjar: different jobs. Hotjar tells you how a page felt; Amplitude tells you whether a cohort came back.
Key Takeaways
- Amplitude’s Starter plan is free to 50,000 events per month; Growth starts near $61/month.
- Initialise the SDK once, set the user ID on login, and keep
defaultTrackingon for baseline data. - Use one naming convention (Title Case or snake_case) and past-tense event names.
- Verify with Live Events and compare against server-side counts to spot ad-blocker loss.
- Start with five to eight events, not forty.
