On this page

What events will you need

Amplitude Academy

Getting Started with Amplitude Analytics

Learn the most fundamental features of Amplitude Analytics, including cohorts.

Get started

Events record the actions users take in your product (signup, purchase, level completed); properties describe the context of each action (channel, plan tier, level number). Every chart, funnel, and cohort in Amplitude reads from this event data, so the events you choose to track determine the questions you can later answer. Track too few and key questions go unanswered; track everything and signal drowns in noise.

Use this guide when you're building a tracking plan from scratch and need a starting list of events. If you already have a draft and want to validate event naming and structure, go to the data planning playbook instead.

How many events should you track

New customers often try to track most, or even all, of the actions a user can take in their product. Resist this urge. Although it feels logical that more data leads to more insights, it usually doesn't work that way. Too much data obscures insights, burying them under an avalanche of events and properties you don't need.

The right number of events depends entirely on the complexity of your product. If your app has a focused feature set, you might only need to track 20 events or so. If your product is feature-rich, 200 might be more appropriate.

To find the right number, think about what kinds of insights you want from Amplitude. What questions do you want Amplitude to help you answer in the next quarter? The next two quarters? Identify those questions, and choose the events that take you there.

What events should you track

Always track any actions that fit into these three categories:

  • Actions that complete a process within your product, such as a tutorial or signup process.
  • Actions that guide a user through the main mechanics of your product.
  • Actions that let a user make an in-app purchase.
After you decide which events to track, plan your events takes a deep dive into this question, so read that next.

Common events and properties to track by industry

This section offers advice, broken down by industry, about which events and properties to track to answer the questions most commonly asked by others in your industry. This isn't a comprehensive list of everything you need. These are suggestions to keep in mind as you create your taxonomy.

Required events and properties:

  • Event: Page View.
    • Properties: url, channel, [Amplitude] Event hour of the day.
  • Your conversion event.
  • [Amplitude] New User.
  • [Amplitude] Any Active Event.

Ecommerce

Required ecommerce events and properties:

  • Event: Page View.
    • Property: utm_source.
  • Event: View Item.
    • Property: product_id.

B2B / SaaS

Required B2B / SaaS events and properties:

  • Group type: Business.
  • User property: role = eng, design, etc.
  • User property: Paying = true/false.
  • Event: Trial Started.
  • Event: Trial Canceled.
  • Event: Account Signed Up.
  • Event: Account Logged In.
  • Your organization's own [key event].

Finance

Required finance events and properties:

  • User property: utm_source.
  • Event: Account Signed Up.
  • Event: Bank Connected (bank name).
  • Event: Automatic Transfer Created.
  • Event: Transfer Submitted (transfer amount).

Media

Required media events and properties:

  • User property: Active Trial = true/false.
  • User property: Device Category = phone, tablet, desktop.
  • Event: Account Signed Up.
  • Event: Trial Started.
  • Event: Trial Canceled.
  • Event: Subscription Purchased.
  • Event: Search Performed.
  • Event: Content Viewed (genre property = comedy, romance, etc).

Healthcare

Required healthcare events and properties:

  • User property: Region.
  • Event: Account Signed Up.
  • Event: Search Performed.
  • Event: Appointment Scheduled.
  • Event: Appointment Rated (rating = 1, 2, 3, 4, 5).

Gaming

Required gaming events and properties:

  • User Property: Region.
  • Event: App Installed.
  • Event: Level Started (level = integer).
  • Event: Level Completed (level = integer).
  • Event: Level Failed (level = integer).
  • Event: Purchase Completed (revenue).

Industry-specific guides

Amplitude also offers industry-specific best practices guides to help you implement and start getting insights quickly. With the goal of driving tangible conversion, retention, and product outcomes, these guides provide you with recommended use cases and business questions, a proposed taxonomy, and an example dashboard that you can use for your own implementation, all tailored to meet the specific needs of your industry.

Amplitude offers guides for companies in the e-commerce, fintech, print media, and streaming media sectors, with more on the way.

Was this helpful?