I’ve been thinking about cost reduction proposals for Mixpanel pricing, so I’d like to share them with you.

Background: Understanding Mixpanel's pricing structure to consider cost reduction proposals

Pricing - Mixpanel | Product Analytics

Prerequisite Knowledge: Changed to MTU billing system in 2019

In 2019, Mixpanel changed from billing based on the total number of events and the number of registered user profiles to a Monthly Tracked User (MTU) billing system.

In 2019, we realized our pricing wasn’t good for our customers. Here’s what we did. - Mixpanel

Therefore, it is no longer necessary to perform regular data deletion like the following for Mixpanel pricing cost reduction:

データを定期的に削除する (Regularly delete data) "Cacoo のようなフリーミアム型のサービスの場合、登録したものの残念ながら使わなくなってしまうユーザが一定の割合で存在します。Mixpanel の課金はイベントの総数と登録されているユーザのプロフィール数に基づくので、離脱したユーザの情報を保持しつづけると利用しているプランの上限を超えてしまう事もありえます。Mixpanel の画面上でそういったユーザの検索は出来ますが、削除は一つずつ手動で行わないといけないため、件数が多くなると現実的ではなくなります。(In the case of freemium services like Cacoo, there's a certain percentage of users who register but unfortunately stop using the service. Since Mixpanel's billing is based on the total number of events and the number of registered user profiles, retaining information of users who have left could exceed the limits of your current plan. While you can search for such users on the Mixpanel interface, deletion must be done manually one by one, making it impractical when the numbers become large.)"

引用元 (Source): エンジニア目線でみるグロースハックツール Mixpanel をのりこなす 6 つのポイント | 株式会社ヌーラボ(Nulab inc.)

What you can do to reduce Mixpanel pricing costs

Turn OFF Mixpanel tracking in non-production environments

By turning OFF Mixpanel tracking in staging and development environments other than production, you can reduce MTU, so I think it would be good to implement it so that you can toggle ON/OFF with environment variables.

That’s all from the Gemba.