SaaS Evaluated Find a tool

Product analytics cost worksheet

Compare Amplitude, Mixpanel and PostHog on one month of events, split before and after signup.

One month of events, before and after signup

The month is 5 million analytics events: 3 million before an account exists, 2 million after. viewed_signup, completed_signup, created_project and invited_teammate are the named steps. The other rows are unnamed product events, sized so the month lands on a volume Mixpanel publishes. Autocapture, replay, flags, experiments and warehouse imports are off. Dollars are list prices before tax, from public pages checked November 19, 2026.

EventAnonymousIdentified
viewed_signup80,0000
completed_signup012,000
created_project07,200
invited_teammate02,400
Other product events2,920,0001,978,400
Total3,000,0002,000,000

viewed_signup goes out with a device id and no account id. completed_signup is that same browser a moment later, with the device id still on the event and a stable account id added. created_project and invited_teammate come after the account exists. When you have an export, replace the unnamed rows with it. One project, so Mixpanel's organization total is this 5 million.

PostHog bills $pageview, $pageleave, $autocapture, $identify, $create_alias and $groupidentify as analytics events. If the SDK sends those, they are already inside the 5 million, and autocapture is off in this example. $exception is a separate product and is left out. If the SDK also emits $identify next to completed_signup, add those events before you compare a bill with this table.

Mixpanel leaves $identify, $create_alias, $merge, $opt_in, session-recording checkpoints and profile updates out of the monthly event count. Simplified ID Merge, the default for organizations created from April 2024, ignores a $identify event, so this example does not send one. Amplitude's Identify call sets user properties, and their docs say it does not send an event. After instrumentation, the usage page should stay at 5 million.

Published rates for that event month

Mixpanel publishes a price at 5 million events. PostHog publishes a rate per event, in bands. Amplitude's pricing page has no dollar amount at this volume, so that row stays blank until checkout.

LineAmountBasis
Amplitude Free$0, up to 2 million eventsFree stops at 2 million events. This month is 5 million.
Amplitude PlusThe amount Stripe shows at checkoutThe page says Plus starts at $0 and runs to 70 million events, or 700,000 monthly tracked users. Growth and Enterprise are custom.
Mixpanel Growth, yearly$438 a monthTheir published 5 million tier. $5,256 for the year. The first million events are inside that price.
Mixpanel Growth, monthly$613 a monthSame 5 million events, billed month to month. Above 20 million events, and Enterprise, are custom.
PostHog, events$152.90All 5 million on the anonymous bands. First million free, next million at $0.00005, last 3 million at $0.0000343.
PostHog, person profiles, if that line has its own free million$198.00The second million of identified events at $0.000198. With the event line, $350.90.
PostHog, person profiles, if identified events have no free allowance of their own$396.00All 2 million identified events at $0.000198. With the event line, $548.90.

The $0.000198 figure is PostHog's identified starting rate of $0.000248 minus the anonymous rate of $0.00005 on the 1-to-2 million band. Their August 1, 2024 pricing post bills events on the anonymous schedule and adds a person-profile line for identified events. The anonymous bands in that post match the product analytics pricing page. The post says the first million events are free whichever type you send, and it does not give the person-profile line a second free million. That is why the person line is either $198 or $396. Enter 3 million anonymous and 2 million identified in the calculator on the pricing page and keep the two lines it prints.

$152.90 is the pay-as-you-go event line. On the free plan, PostHog stops accepting events once the allowance is used, so this month would be cut off. The example adds no platform package, group analytics, recordings or flag requests. PostHog does not charge to store the events or to query them. Pay-as-you-go keeps events for 2 years.

Mixpanel's $438 and $613 include 20,000 session replays on Growth. This month records no replays and leaves Group Analytics and Data Pipelines off. Amplitude Free and Plus include 10,000 replays a month, unused here. Once you buy a Plus volume, further events are charged at the per-event or per-MTU rate you bought, and Plus terms say Amplitude can suspend the account above 200 percent of that volume.

Browsers and a short funnel

This trial was not run, and no vendor account was opened. Use ten clean browsers. Five people complete viewed_signup, completed_signup, created_project and invited_teammate in that order, in one browser, inside 7 days. Three people stop after viewed_signup. Two people view the signup page in one browser, then complete signup as that same account in a second browser. The funnel counts people, with a 7-day window.

StepAmplitudeMixpanel SimplifiedPostHog
Browse before signupSend a device id and leave the user id empty. A shared placeholder such as None sticks unrelated people together.Send $device_id and no $user_id.Stay on the anonymous distinct id. Skip identify, group and $set.
Sign up in that same browserCall setUserId with the account id before the next event, and keep the device id. Events from before signup should sit on that person.Send one event that has both $device_id and $user_id. That pair is the cluster, and $user_id becomes the distinct id.Call identify with the account id. Events after that are identified, and PostHog bills them on the person-profile line.
Sign up again from a second browserSend the same account id. A new device id on its own stays a separate person. Two different account ids do not merge, and the id is case-sensitive.Send the new $device_id with the same $user_id. A second $user_id cannot join the cluster. On this API, $identify is ignored.Call identify with the same id. The earlier anonymous events should show on the person. On the bill, check whether those past events were charged as identified.
Read the funnelThe five same-browser people show up once, on all four steps. The three who only looked stay on step 1. Each cross-device account shows up once from signup on. The first browser's viewed_signup is on that person when the device id was still present as the account id arrived.One profile for that person. Two profiles means $device_id and $user_id were never on the same event.Step 1 is on that person when the anonymous history stayed attached. PostHog's docs say past events are attributed to the person and otherwise left as they were.
Check the usage pageThe count matches the events you sent. Their Identify call is documented as properties, with no extra event.The meter matches the export. A stray $identify is left out of the count and does not merge anything.The event line plus the person-profile line matches the calculator. Another $identify on top of the 12,000 completed_signup events means the SDK sent the signup twice.

Read the Mixpanel project setting before you send the first event. Organizations created from April 2024 start on Simplified ID Merge, and the API cannot be changed once the project has data. Original ID Merge is a different test, because that one does use a $identify event. On Amplitude the account id has to be the same string, including case, in the browser and on any server event, or a second user id becomes a second person.

What to save from checkout and from the quote

Send this same month. Keep the reply with the plan name, the meter and the term.

VendorRequestSave
Amplitude Plus checkout5 million events, one project, no replays.The monthly and annual amounts Stripe shows, whether the meter is events or monthly tracked users, the replay allowance, and the overage rate.
Amplitude Growth or EnterpriseThe same 5 million events, plus the requirement that the anonymous visit lands on the account inside a 7-day funnel.The written quote. Both plans are custom on the pricing page.
PostHog pricing calculator3 million anonymous events and 2 million identified events. No replay, flags, group analytics or platform package.The event line and the person-profile line. Those replace the $350.90 and $548.90 rows above.
Mixpanel, past 20 million eventsTheir own published price at 5 million: $438 a month on yearly billing, $613 month to month.The written price above 20 million, and whether Group Analytics is included. It is separate from the $438.
Pendo or HeapAsk Pendo for a MAU price and Heap for a session price for this month. Put the 5 million events in the note, and have them supply the MAU or session count.Pendo Base, Core and Ultimate are request pricing on a custom MAU volume. Their FAQ puts Pendo Free at 500 MAU. Heap Free is 10,000 sessions a month. Growth estimates after you install the snippet. Pro and Premier are custom session pricing.

No PostHog account was opened. The $350.90 and $548.90 rows are the two readings of the public bands, and they stand until the calculator is run.

Amplitude's marketing comparison puts Plus near $5,388 a year at about 5 million events. That figure is not on the pricing page checked for this worksheet, so the table leaves it out.

Sources