# Billing meters, how they grow and what happens at the limit Every figure below was read from the vendor's live page on 2026-10-17. Prices change more often than anything else in this skill. Before you quote a number to the user, fetch the page named in the entry. If the live value differs, use it, say what changed, and put the new checked-on date in the memo. ## Contents - Rules for every price - Forecast method - GA4 and Analytics 360 - Mixpanel - Amplitude - PostHog - Heap - Pendo - Statsig - Warehouse-native and seat-priced tools - How each meter grows with the business - MTU or event: the break-even method - Startup programmes and month 13 - Worked arithmetic ## Rules for every price - Write every price as "USD X, checked on YYYY-MM-DD, URL". A price without a date is not allowed in the memo. - Price the cheaper of two routes: the smallest published tier at or above the forecast volume, and a lower plan plus that plan's additional data rate. The user reads the rate for their own plan in the vendor's billing settings. Never multiply the entry overage rate across a large volume, and never buy a tier when overage on a lower plan costs less. - Keep billing periods apart. A monthly equivalent of an annual commitment is not a cancellable monthly price. - When a page hides prices behind a calculator, look for the estimator's values in the page data or ask the user to read the result for the given volume. Never interpolate between published points. - Existing accounts can sit on legacy terms. A public page does not reprice a signed contract; ask for the order form. - Separate units: analytics events, identified events, MTUs, sessions, MAUs, replays, flag requests, experiment users, seats and warehouse compute are different meters with different allowances. ## Forecast method Build the forecast from behaviour, not registrations: ```text client events / month = active people x sessions per person x events per session total events = client events + backend events + imports + sync churn identified share = events from logged-in people and backend producers / total events events per identity = total events / distinct identities (anonymous devices count) ``` Produce four cases for every candidate: - Normal: observed usage from a representative month. - Growth: the 12-month plan for active people, plus every release that adds events. - Fault: one realistic instrumentation error, such as a duplicate sender, an SDK initialised twice, or autocapture enabled on every page. - Month 13: the plan the company moves to after a free year or programme, at the growth-case volume. Use [../assets/usage-forecast.yaml](../assets/usage-forecast.yaml) for the inputs. Forecast heavy segments separately: a few enterprise accounts with high events per user can dominate the bill. ## GA4 and Analytics 360 - Standard GA4: Google describes it as free of charge. The cost lives in implementation, BigQuery storage and queries, and maintenance. - Standard BigQuery daily export: limited to 1 million events a day. A property that consistently exceeds it has its daily export paused, immediately for a significant overage, and missed days are not reprocessed. Data streams and events can be excluded to stay under. Source: support.google.com/analytics/answer/9823238. - Streaming export: no volume limit, best effort with no completeness SLO, and charged at USD 0.05 per GB in BigQuery (Google's estimate is about 600,000 events per GB). Source: support.google.com/analytics/answer/9358801. - Analytics 360: contract through Google sales or a partner; no public price. Each event hit copied to a subproperty or roll-up property is charged at half the rate of the initial hit. An event routed to two extra properties therefore costs 1 + 0.5 + 0.5 = 2 hit-equivalents. Source: support.google.com/analytics/answer/9679158. - 360 versus standard limits worth a buying conversation: 100 versus 25 parameters per event, 125 versus 50 event-scoped custom dimensions, 1 billion versus 10 million events per exploration query, up to 50 versus 14 months of event data retention. Source: support.google.com/analytics/answer/11202874. - On 360, the 26, 38 and 50 month options apply to event data only. User-level data and key events stay at 2 or 14 months, and age, gender and interest data at 2 months. A buyer who needs more than 14 months of key-event history in explorations does not get it from 360. Source: support.google.com/analytics/answer/7667196, checked on 2026-10-17. - Large standard and XL 360 properties are limited to 2 months of event data retention; reclassification deletes older event-level data. Source: support.google.com/analytics/answer/7667196. - What grows the bill: total event hits across properties and every routing copy. Draw the property structure before asking for a quote. ## Mixpanel Sources: mixpanel.com/pricing and docs.mixpanel.com/docs/pricing. - Unit: events, counted at ingestion time. Imported history counts in the month it is ingested. Legacy accounts on event-timestamp billing behave differently; check which applies. - Free: up to 1 million events a month, 5 saved reports per seat, 10,000 session replays a month, 1,000 monthly experiment users. Over the event allowance, report viewing is blocked until upgrade or the monthly reset; collection continues and no overage is charged. - Growth: the first 1 million events are free each month. The slider on mixpanel.com/pricing lists 13 tiers, billed monthly then billed yearly (per month), checked on 2026-10-17: - 1M: USD 0, USD 0 - 1.5M: USD 140, USD 100 - 2M: USD 259, USD 185 - 3M: USD 378, USD 270 - 4M: USD 504, USD 360 - 5M: USD 613, USD 438 - 6.5M: USD 785, USD 561 - 8M: USD 952, USD 680 - 10M: USD 1,176, USD 840 - 12.5M: USD 1,466, USD 1,047 - 15M: USD 1,722, USD 1,230 - 17.5M: USD 2,003, USD 1,431 - 20M: USD 2,289, USD 1,635 - Above 20M: contact sales. - Read the whole ladder from the live page and quote the smallest tier at or above the forecast. A 3.2M forecast prices at the 4M tier (USD 504), not 5M; a 7M forecast at 8M (USD 952), not 10M. - The 1M Growth plan: each event over 1 million bills at USD 0.00028. Group Analytics adds 40% and Data Pipelines 20% of that calculated overage. Mixpanel's own example: 1.1M events bills 100,000 events at the rate plus 40% for Group Analytics. A customer does not have to move up a tier. - Which route is cheaper, for the base event charge: the 1.5M tier at USD 140 equals 500,000 x 0.00028, so between 1M and 1.5M events the 1M plan plus overage never costs more than the tier. At 2M the tier (USD 259) beats overage (1M x 0.00028 = USD 280), and the gap widens with volume: at 3M, overage on the 2M events above the included 1M is USD 560 against the USD 378 tier. - With add-ons the 1M-to-1.5M claim no longer holds on its own. Overage at 1.45M with Group Analytics is 450,000 x 0.00028 x 1.4 = USD 176.40, against USD 140 plus the tier's quoted add-on fee. Compare overage plus the 40% or 20% against the tier plus its quoted add-on, never the bare tier. - Higher tiers have their own, lower additional data rates, shown in Organization Settings under Plan Details & Billing. Ask the user to read the rate for their plan; it is not on the public page. - Annual billing needs a pre-committed volume above 1 million monthly events. The 1M plan is monthly only. - Add-on price on a pre-purchased tier: the pricing page says only "extra fee". The 40% and 20% figures on the billing page apply to the calculated overage. Get the tier add-on price, and any minimum, in the quote. - No hard billing cap on Growth: the billing page says a billing limit cannot be set. Owners and billing admins get alert emails at 85%, 100%, 110%, 120%, 200%, 300% and 400% of plan volume. Add a usage report with alerts for anything earlier. - Warehouse connectors: a free add-on on paid event-based plans at update or renewal. Inserted rows bill as events. Mirror updates and deletes bill. Dropping and recreating a mirrored table bills every row as a delete and again as an insert. - Monthly experiment users: Free 1,000, Growth 5,000, with 10,000 to 100,000 purchasable. Free pauses Experiments at the allowance while flags keep serving; Growth bills the overage. Source: docs.mixpanel.com/docs/experiments. - AI telemetry: Agent Intelligence (beta, by request) records every span as one Mixpanel event, and those events count towards event volume. There is no separate meter, so forecast spans per request on the ordinary event line. Source: docs.mixpanel.com/docs/agent-intelligence, checked on 2026-10-17. - MTU option: an Enterprise plan from USD 20,000 a year, sales only, suggested above 100,000 users or 5 million monthly events. Source: docs.mixpanel.com/docs/pricing/legacy-mtu-billing, written for existing MTU customers, so confirm in the contract that it applies to a new one. Its rules: - An MTU is any distinct ID with at least one qualifying event in the calendar month, whether or not it has a user profile, so anonymous visitors count. - A user active in several projects counts once per project. Amplitude counts once overall. - Guardrail: when users average more than 1,000 events each, MTUs equal total events divided by 1,000. - Identify, alias, merge and some messaging and Mirror update events do not qualify. ## Amplitude Sources: amplitude.com/pricing, amplitude.com/plus-plan-terms, amplitude.com/docs/admin/billing-use/mtu-guide, amplitude.com/docs/faq/limits-and-quotas. - Free: 2 million events a month, 10 saved charts per organisation, 1 year of data access, 10,000 session replays with 1 month of replay retention. Group behaviour analysis and experiment results are not included. - Over the Free limit: after the third monthly overage the account is blocked from charts and dashboards; if overages continue without an upgrade, the account is deleted six months after the first block. Hidden events and backfilled events count. - Plus: starts at USD 0 with the first 2 million events free, up to 70 million events or 700,000 MTUs, 2 years of data access. Experiment results are excluded. Group behaviour analysis is listed as available. - Plus estimator, event plans, read from the estimator data (`plus_v4`, amounts in cents) in the live pricing page, checked on 2026-10-17 (monthly billing, then per month billed yearly): - 2M: USD 0, USD 0 - 3M: USD 94, USD 75 - 5M: USD 281, USD 225 - 10M: USD 720, USD 576 - 15M: USD 1,170, USD 936 - 20M: USD 1,575, USD 1,260 - 50M: USD 4,140, USD 3,312 - 60M: USD 5,003, USD 4,002 - 70M: USD 5,865, USD 4,692 - Plus estimator, MTU plans, same source: 10,000 MTUs USD 160, USD 127.50; 25,000 MTUs USD 266, USD 212.50; 50,000 MTUs USD 501, USD 400.25; 100,000 MTUs USD 930, USD 743.75. - The same estimator data carries an `accounts` add-on line for Plus (USD 0 at 2M events, USD 28 a month at 3M), while the plan comparison lists the Accounts (Group) package for Growth and Enterprise only. Get in writing whether Accounts can be bought on Plus before pricing it there. - Re-read the estimator before quoting any of these. They change without notice. - Plus terms (effective 23 July 2026): an MTU purchase carries an event allowance of purchased MTUs x 1,000 events, as an average. Usage above the purchase may be charged at 1.0 times the per-MTU or per-event fee, billed on or around the fourth day after the month ends. Amplitude may suspend or terminate Plus when usage exceeds 200% of the purchased volume. The terms do not define how the per-unit fee is derived; the worked arithmetic below assumes purchase fee divided by purchased volume, so get the rate in writing. - AI telemetry: the plan comparison lists Monthly Agent Sessions (5,000 on Free and Plus, 10,000 on Growth, 20,000 on Enterprise, add-on for more) as their own allowance. Source: amplitude.com/pricing, checked on 2026-10-17. - Growth and Enterprise: the pricing page labels them event-based with custom volume. The MTU guide says all plans support MTU pricing. Ask sales to quote both units on the same workload. - MTU rules from the MTU guide: - A unique user with at least one event in a calendar month, in UTC. Recalculated daily, finalised after month end. - A user active in several projects counts once. - Identify calls, Group Identify calls and user mapping do not add MTUs; nor do `[Experiment] Exposure` and `[Experiment] Assignment` events. - Usage above the allowance adds synthetic MTUs at one per 1,000 events. The Free MTU plan allows 1,000 events per MTU; other contracts vary. - Customers using sampling cannot buy MTU pricing. - Backdated events add an MTU for each month a distinct user appears and are charged to the month they are added. Ask for a written sample calculation before a large backfill. - Accounts (Group) package: account-level analytics, group-level experimentation and account-level bucketing, listed for Growth and Enterprise and priced as a percentage of the platform plan. ## PostHog Sources: posthog.com/pricing (and its .md version), posthog.com/docs/data/anonymous-vs-identified-events, posthog.com/docs/product-analytics/group-analytics, posthog.com/docs/billing/limits-alerts, posthog.com/docs/api/flags. - Every product has its own meter and free tier, which resets monthly. Feature flags and experiments share one meter. Web analytics is included with product analytics. - Free plan retention 1 year; paid plan 7 years. Replay retention up to 30 days on Free and 90 days on pay-as-you-go. - Analytics events, per event: first 1M free; 1M to 2M USD 0.00005; 2M to 15M USD 0.0000343; 15M to 50M USD 0.0000295; 50M to 100M USD 0.0000218; 100M to 250M USD 0.000015; above 250M USD 0.000009. - Identified events add-on (person profiles), per identified event: first 1M free; 1M to 2M USD 0.000198; 2M to 15M USD 0.0000697; 15M to 50M USD 0.000036; 50M to 100M USD 0.0000146; 100M to 250M USD 0.0000037; above 250M USD 0.000001. - Group analytics add-on, per event: first 1M free; 1M to 2M USD 0.000071; 2M to 15M USD 0.00003; 15M to 50M USD 0.0000189; then lower bands. Once subscribed it bills all identified events in the project, including events with no group property. Anonymous events cannot link to groups. - Session replay, per recording: first 5,000 free; 5,001 to 15,000 USD 0.005; 15,001 to 50,000 USD 0.0035; then lower bands. - Flags and experiments, per request: first 1M free; 1M to 2M USD 0.0001; 2M to 10M USD 0.000045; then lower bands. - Identified versus anonymous: web, Android, iOS and Flutter SDKs default to identified-only capture, so events before identify are anonymous. Backend SDKs and the API send identified events by default; set `$process_person_profile` to false for anonymous backend events. After identify, earlier events stay billed as anonymous. Anonymous events cannot use person properties, cohorts, lifecycle insights or group analytics. PostHog says anonymous events can be up to four times cheaper. - AI Observability, per event: first 100,000 free; 100,001 to 150,000 USD 0.00035; then lower bands. Traces can far outnumber user turns, so forecast spans per request, not conversations. Source: posthog.com/pricing.md, checked on 2026-10-17. - Historical imports: events sent with `historical_migration` set to true are not charged standard ingestion fees, but the import needs a paid product analytics plan. The managed Mixpanel, Amplitude and S3 imports set the flag automatically. Ongoing parallel capture still bills. Source: posthog.com/docs/migrate, checked on 2026-10-17. - Billing limits: set per product in the organisation's billing settings. At the limit PostHog stops ingesting and processing, and the excess data is lost. - Free plan over a free allowance: not documented on the billing pages (posthog.com/docs/billing/limits-alerts and posthog.com/docs/billing/common-questions, checked on 2026-10-17). Confirm on the live pricing FAQ or with PostHog before recording a pass, and treat it as data loss until confirmed. The flags `quotaLimited` behaviour below does apply once the organisation is over its flags quota. - Flags at the limit: when the organisation exceeds its Feature flags & Experiments quota, flag evaluation pauses for the whole organisation. `/flags` returns `quotaLimited` with an empty flags object, so flags and experiments fall back to whatever default the code uses. Never cap the flags product without a tested default for every live flag, and record this in the memo whenever flags are in scope. - Alerts: the organisation owner gets emails at 80% and 100% of a billing limit and of the free allotment. There is no 80%-of-budget email for paid volume without a limit. Pick one and name its owner: - A billing limit set with deliberate headroom above the budget, accepting data loss at 100%. Not on the flags product. - An insight alert on a trend of monthly event volume, with a threshold at 80% of the budgeted volume (Free organisations get 5 alerts). Spike detection emails add a daily check, but only for organisations without an assigned account owner, and at most one email in 7 days. Sources: posthog.com/docs/alerts, posthog.com/docs/billing/spike-detection. - What grows the bill: identified share, group subscription across all identified events, and each product switched on. ## Heap Source: heap.io/pricing. - Unit: sessions. A web session ends after 30 minutes of pageview inactivity; a mobile session ends after 5 minutes of inactivity (checked on 2026-10-17). Forecast mobile sessions from observed foreground sessions under the 5-minute rule, never from the web session count. - Free: up to 10,000 sessions a month, 6 months of history. - Growth: self-serve and paid. The price is an estimate shown after the snippet is installed. 12 months of history, unlimited users and reports, CSV export. No account analytics, no Heap Connect, no session replay. - Pro and Premier: custom session pricing. Account analytics from Pro. Heap Connect is a Pro add-on and included in Premier. Session replay is an add-on on Pro and Premier. - Over the limit: Heap says it does not drop or throttle data, but viewing requires an upgrade. - What grows the bill: visits, including marketing pages and campaign spikes, independent of how many events each session sends. ## Pendo Source: support.pendo.io article "Pendo Free". - Free: 500 monthly active users, counted as unique visitor IDs in a 30-day period. Excluded visitors and accounts do not count. - Over the allowance: reports show a random sample of 500 visitors; creating guides, NPS surveys and segments is blocked until upgrade. - No API or third-party integrations on Free. ## Statsig Source: statsig.com/pricing. - Metered events: exposures, log events, metrics ingested from a warehouse, and custom metrics. Each log event includes one dimension; each extra dimension counts as another event. - Flag and config checks are unlimited, except that a check on a gate with Metric Lifts enabled and a partial rollout logs a billable exposure. Gates at 0% or 100% rollout, disabled flags and experiments with no allocation do not bill. Forecast lift exposures for every partial rollout the team measures. - Developer (free): 2 million metered events and 50,000 replays a month. Over the allowance, targeting keeps working and lift computations stop. - Pro: USD 150 a month with 5 million events, then USD 0.05 per 1,000 events, and 100,000 replays. - Warehouse Native: Enterprise only. - Amplitude announced on 5 May 2026 that it will take on Statsig's brand and customers and will maintain the cloud and warehouse platform. Confirm which entity contracts and supports the product before signing. ## Warehouse-native and seat-priced tools - Mitzu (mitzu.io/pricing): unlimited events, no per-event pricing. Analyst USD 149 a month (USD 134 billed yearly) with 3 editors, no viewers, 300 AI insights; Team USD 749 a month (USD 675 billed yearly) with 10 editors and unlimited viewers. 14-day trial. - GrowthBook (growthbook.io/pricing): seat-based. Starter free for up to 3 users; Pro USD 40 per seat per month for up to 30 users. Saved custom SQL reports and private dashboards need Pro; sharing dashboards across the organisation needs Enterprise. Source: docs.growthbook.io/app/product-analytics. - GrowthBook cloud also meters usage, checked on 2026-10-17: managed warehouse events (Starter 1M a month; Pro 2M a month, then USD 30 per million), CDN requests (Starter 1M; Pro 2M a month, then USD 10 per million) and CDN bandwidth (Starter 5GB; Pro 20GB, then USD 1 per GB). Forecast them when the team does not bring its own warehouse or serves flags through the GrowthBook CDN. - Statsig Warehouse Native: Enterprise terms. - Add the warehouse: query compute, refresh schedules, intermediate tables and the hours to maintain models. These grow with query load and people, not traffic. Details in [warehouse-native.md](warehouse-native.md). ## How each meter grows with the business - Events grow with engagement times instrumentation density. One autocapture decision can multiply volume three to five times with no new customer. Imports, Mirror sync churn and duplicate senders add volume that is not usage. - Identified events grow with the logged-in share and every backend producer. - MTUs grow with distinct identities. Anonymous devices, unmerged logins and test users all count, and intensity above the allowance turns into synthetic MTUs. A marketing site on an MTU meter pays for every one-visit reader. - Sessions grow with traffic. Campaign bursts, bots and docs pages raise the bill while product usage stays flat. - MAUs (Pendo) grow with distinct visitors in a 30-day window, including occasional users. - Seats grow with the number of editors. Check whether viewers are free; Mitzu Analyst has none. - Contract hits (GA4 360) grow with events and with every subproperty or roll-up copy. - AI telemetry grows with spans per request, not with users. PostHog AI Observability has its own allowance; Mixpanel Agent Intelligence spans land on the ordinary event meter; Amplitude lists agent sessions as their own allowance. - A CDP in the collection path has its own meter. Segment counts unique `userId`s plus `anonymousId`s never linked to a `userId`, across every source in the workspace, per billing month, so a new source that brings new identities (a marketing site sending anonymous page calls) raises it. Source: twilio.com/docs/segment/guides/usage-and-billing/mtus-and-throughput, checked on 2026-10-17. Forecast it beside the analytics meter. Rules that follow: - MTU or event pricing: compute both bills with the break-even method below for the normal, peak and import months and take the cheaper. Never decide from events per identity alone. - Anonymous surfaces (marketing site, docs): price them separately on each candidate's meter. Keep them off MTU, session and identified-event meters unless a named decision needs pre-signup behaviour inside the product tool. Carry campaign context in through first-touch properties captured at signup. - Session-light, event-heavy product: a session meter can be cheap; session-heavy marketing traffic makes it expensive. - Many viewers, few editors: seat pricing with free viewers beats per-user analytics seats. - Growth case past 80% of a free allowance within six months: price the paid plan now and set a usage alert at 80%. - Hard cap needed for budget: record what the cap does to data. PostHog drops data over a billing limit and pauses flag evaluation over the flags quota; Mixpanel Growth cannot be capped; Heap blocks viewing; Amplitude blocks a Free account after its third monthly overage and may suspend Plus above 200% of purchase. ## MTU or event: the break-even method Use whenever a candidate offers both units (Amplitude on every plan, Mixpanel Enterprise). Price both on the same normal, peak and import months, then take the cheaper. ```text P = purchased MTUs F = monthly fee for P f = F / P (per-MTU fee, confirm in writing) A = events-per-MTU allowance (1,000 on Amplitude Plus and the Free MTU plan; confirm any other contract) m = overage multiplier (1.0 on Plus) synthetic MTUs = max(0, events - P x A) / A billed MTUs = unique identities + synthetic MTUs MTU bill = F + max(0, billed MTUs - P) x f x m event bill = the cheaper of the smallest tier at or above the events and a lower plan plus its overage ``` Rules: - Reject an MTU size if any month's billed MTUs exceed 200% of P; Plus allows suspension above that. Size P up and recompute. - Mixpanel's MTU option uses its own guardrail instead of synthetic MTUs: when users average more than 1,000 events each, billed MTUs equal total events divided by 1,000. Substitute it for the synthetic line and confirm it in the order form. - Reject an MTU quote whose minimum commitment exceeds the event bill. - High events per identity raises the MTU bill through synthetic MTUs, but does not by itself make event pricing cheaper. On the Plus estimator values above, a per-MTU fee of about USD 0.009 to 0.016 carries 1,000 events of allowance, while event plans cost about USD 0.07 to 0.08 per 1,000 events from 10M events upwards. MTU pricing usually wins for intense logged-in use; event pricing wins for low events per identity, such as anonymous one-visit traffic or occasional users. - Show both totals in the memo appendix with the checked-on date. ## Startup programmes and month 13 Checked on 2026-10-17. Eligibility is the vendor's decision; read the live page. - Mixpanel Startup Plan (docs.mixpanel.com/docs/pricing/startup-program): - Eligibility: incorporated less than five years ago, no more than USD 8M raised, no earlier Mixpanel offer redeemed, never on a paid plan. - Includes, for 12 months: 1 billion events per year (an annual pool, not a monthly allowance), 1 million replays, every advanced report, and the Data Pipelines, Group Analytics, Warehouse Connectors and Session Replay packages. - Data must start arriving within 90 days of acceptance, or the startup is removed and cannot rejoin. - It does not renew. After the year the company moves to Free, Growth or Enterprise. - Amplitude Startup Program (amplitude.com/startups): - Eligibility: fewer than 20 employees and under USD 10M raised. - Year one: the full Growth plan for 12 months, up to 200,000 MTUs or 100 million events a month. - Year two: 40% off an annual Plus plan, and a usage-based quote 60 days before the year ends. Plus excludes experiment results and lists the Accounts package only on Growth, so a team using either in year one needs a quote for the plan that keeps them. - PostHog for Startups (posthog.com/pricing, posthog.com/startups): - USD 50,000 in credits for 12 months. - Eligibility: company less than 2 years old, less than USD 5M raised, a PostHog signup from 1 January 2023 onwards, and an account on the company's email domain. - Credits apply after signing up to a paid plan and applying. - From 14 September 2026 credits do not cover PostHog's AI tools (PostHog Desktop, the Slack app, Replay Vision, PostHog AI and Inbox). - Credits cannot be used to claim a BAA under the Boost package. Budget Boost in cash from day one when a BAA is required. Rules: - The memo budgets month 13 on the plan the company will actually move to, with the capabilities it used in year one. - Pilot on a startup plan or a written, time-boxed add-on trial. Never commit to an annual tier in order to pilot. ## Worked arithmetic PostHog, 3 million identified events with group analytics, from the bands above: ```text analytics events: 1,000,000 x 0.00005 + 1,000,000 x 0.0000343 = 50.00 + 34.30 = 84.30 identified add-on: 1,000,000 x 0.000198 + 1,000,000 x 0.0000697 = 198.00 + 69.70 = 267.70 group add-on: 1,000,000 x 0.000071 + 1,000,000 x 0.00003 = 71.00 + 30.00 = 101.00 monthly total (USD, checked on 2026-10-17) = 453.00 without group analytics = 352.00 ``` The same 3 million events with only 1 million identified would drop the identified line to zero, but the group add-on cannot use anonymous events. Decide which analysis needs person history before cutting it. Mixpanel, 1.2 million events on the 1M Growth plan with Group Analytics: ```text overage: 200,000 x 0.00028 = 56.00 group analytics: 56.00 x 40% = 22.40 monthly total (USD, billed monthly) = 78.40 1.5M tier instead = 140.00 monthly, or 100.00 a month billed yearly, plus the tier add-on ``` Mixpanel at 3 million events: the tier is USD 378 billed monthly or USD 270 a month billed yearly, before Group Analytics. Twelve monthly bills are USD 4,536; the yearly price is USD 3,240. Compare like with like. Amplitude Plus, MTU against event pricing, estimator values checked on 2026-10-17 (amplitude.com/pricing), billed monthly: ```text month observed: 48,000 unique users, 62,000,000 events (about 1,292 events per user) MTU route, 50,000 MTUs purchased at USD 501 event allowance: 50,000 x 1,000 = 50,000,000 events synthetic MTUs: (62,000,000 - 50,000,000) / 1,000 = 12,000 billed MTUs: 48,000 + 12,000 = 60,000 (120% of purchase, under 200%) per-MTU fee: 501 / 50,000 = USD 0.01002 (assumed; confirm) overage: 10,000 x 0.01002 x 1.0 = USD 100.20 MTU bill = USD 601.20 event route 70M tier = USD 5,865.00 60M plan plus 2M overage at its per-event fee: 5,003 + 2,000,000 x (5,003 / 60,000,000) = USD 5,169.77 event bill (cheaper route) = USD 5,169.77 ``` Unique users stayed under the purchase and the month still bills 10,000 MTUs of overage, yet MTU pricing is about USD 4,570 a month cheaper. Now drop intensity: the same 48,000 users at 100 events each make 4.8M events, which cost USD 281 on the 5M event tier against USD 501 for 50,000 MTUs (25,000 MTUs at USD 266 would bill 48,000, 192% of purchase, for about USD 511 and sit next to the 200% clause). Low intensity favours events; high intensity usually favours MTUs. Run both bills for every case. Heap, app only versus site plus app: ```text app only: 3,000 logged-in people x 5 sessions = 15,000 sessions site plus app: 15,000 + 40,000 marketing sessions = 55,000 sessions Free allowance = 10,000 sessions ``` App-only capture still exceeds Free, and site capture nearly quadruples the session meter with no new decision behind it. GA4 360 routing: 40 million source hits, 12 million copied to a regional subproperty and 40 million copied to a roll-up give 40 + 6 + 20 = 66 million hit-equivalents, 65% above the source volume. A planning number for the quote conversation, not a price.