Skip to content

Amplitude

Amplitude turns actions such as creating a workspace and inviting a teammate into reports about how people start and keep using your app.

Visit Amplitude

How can you tell whether someone got through onboarding?

Choose an action that means the app has become useful to that person. For a team app, you might count a saved workspace and then a successfully sent invitation. Those two recorded actions can become steps in a Funnel Analysis chart.

Decide how much time to give the second step. A teammate invitation sent the next day can count in a seven-day funnel. A separate return-usage question would need its own event and timeframe.

How do you check that each event reaches the right project?

Use a separate test project and its own project key. Follow one fictional account in User Activity to see the actions as Amplitude receives them. A saved workspace should show up once, even if the person reloads the screen.

  1. Confirm the destinations before you open the test app
    Verify the actual browser and server project keys, including any event router, against your disposable project. Confirm the app reads and writes only disposable workspace and account data. Use a clean browser profile and a fresh fictional account ID never used in another project. Check the test project’s effective automatic event collection and replay settings, including any remote settings that can override the app, and keep both off. Confirm that invitations, callbacks and any forwarding cannot reach real users or live systems. If you cannot verify every connection and setting, use a paper event log.
  2. Rehearse the success and failure
    Using isolated test routes, create a workspace once, reload it and try one invitation that your test setup will reject. Check the fictional account’s event stream. Expect one workspace saved event and no invitation sent event for the failed attempt. Then complete one simulated invitation and check for one success.
  3. Read the evidence at the right scope
    Compare the event name and timing with the exact app action before looking at a funnel. This tests what the app reported for one fictional account. Customer behavior still needs data from your live app.

What connects anonymous activity with a signed-in account?

Amplitude can recognize a browser by a device ID and link actions to an account after the app supplies a user ID. Use a stable account identifier rather than an email address, and check what happens when two people share a device or a browser clears its storage.

Review automatic collection before turning it on. Keep invitation addresses and workspace content out of event properties. If you later enable replay, masking page text and inputs can still leave sensitive text in HTML attributes, such as a form field’s placeholder. Keep private values out of those attributes and check the result with a fictional replay in the isolated test project before turning on live recording. Heatmaps combine interactions from many web sessions, and Amplitude lists them on Plus and higher plans.

How does Amplitude count usage, and what can you move?

The current public Free plan lists 2 million events per month. Four recorded actions from one person can be four events. Some existing contracts use monthly tracked users instead, a different unit that counts a person who generated at least one event in the month.

Use the project’s Export API to take out underlying event records for a time range. Keep a separate copy of your event definitions and chart settings. For a privacy request, check which projects the deletion covers. The version 2 User Privacy API spans the organization, and an app or data import can still send new events after deletion.