October 7, 2026

3 MMP Pricing Models Compared: Billing Units, Allowances & Terms

Compares Airbridge event pricing with install- and active-user-based MMP plans, including allowances, overages and terms to match a bill to your forecast.

Quick answer: choose the bill you can forecast from your own app activity.

• Airbridge Core fits teams that want to estimate spend from app events, a published monthly data-point allowance, and a per-data-point overage rate.
• Tenjin fits teams that want a free attributed-install allowance, followed by published per-conversion pricing and monthly or annual plans.
• Kochava fits teams that want a free allowance measured in attributed conversions and app events, or paid pricing based on monthly active users or attributed conversions.
• Keep app events, attributed installs, and monthly active users in separate columns. They describe different activity.

Estimate next month’s MMP bill by matching your app’s forecast to the plan’s billing unit. The comparison should also name included usage, extra-use charges, plan limits, and the payment or contract term.

This comparison uses Airbridge, Tenjin, and Kochava pricing and product pages accessed October 1, 2026.

What makes MMP pricing transparent enough to compare?

A useful price comparison names the billable unit, included amount, extra-use charge, plan limits, and payment or contract term. Those details let you price both ordinary and high-volume months against your own app activity.

Airbridge defines one data point as one event the app sends. Tenjin’s pricing page defines a conversion as a mobile app install attributed to a paid user-acquisition campaign. An app event, attributed install, and monthly active user are different counts, so each plan’s allowance needs its matching forecast.

A founder can make a fair comparison by building three forecasts from three separate inputs:

1. App events: Count the events the app sends during a month, such as trial starts, purchases, or renewal events, when the plan bills by data point or event.
2. Attributed installs: Forecast the number of installs credited to paid user-acquisition campaigns when the plan bills by conversions or attributed conversions.
3. Monthly active users (MAU): Forecast the active-user count when the plan’s price basis uses MAU.

The same user can produce several app events, one attributed install, and active-user activity in a month. Each figure answers a different billing question. A forecast that rolls them into a single “app volume” number hides the very difference that can move the bill.

Record each provider’s counted action and what the price does below, at, and above the allowance. Then record the payment term, such as monthly post-payment, monthly or annual prepayment, or no annual contract.

Airbridge Core: estimate spend from app events

Airbridge Core is the clearest fit here for a team that wants to forecast cost using app events and retain a month-to-month decision. The Airbridge pricing page lists a 30-day free trial, then $40+/mo, with 500,000 data points included per month, $0.0001 for each extra data point, and no annual contract. It also lists two third-party integrations in the Core allowance.

The key input is the number of events the app sends, because Airbridge defines one data point as one event sent by the app. If your subscription app sends 400,000 events in a month, that activity sits below the stated 500,000-data-point allowance. The listed starting price after the trial is $40+/mo, and no data-point overage is due in this example.

If the same app sends 600,000 events, the first 500,000 fit inside the allowance and 100,000 are extra. At $0.0001 per extra data point, that adds $10 in usage charges: 100,000 × $0.0001 = $10. The example bill is $50+/mo, calculated as the $40 starting amount plus the $10 overage. The “+” matters because usage above the allowance changes the amount.

This method works best when the team has an event plan it can count. For instance, an app team might send a trial-start event when a user begins a trial, a purchase event when payment succeeds, and renewal events as subscriptions continue. The team can then estimate a lower and upper month by changing the event count, rather than treating paid installs as a substitute.

Build the event forecast from the instrumentation plan

Start with the event names your app actually sends, then estimate how many times each one will fire during a normal month and a campaign month. Trial starts, subscription starts, purchases, and renewals can each create separate event sends when the app is set up to report them.

For an illustrative estimate, suppose an app expects 125,000 trial-start sends, 75,000 subscription-start sends, 60,000 renewal sends, and 40,000 purchase sends in a month. Those assumptions total 300,000 data points, which sits within Airbridge Core’s 500,000 monthly allowance. If each category doubles during a campaign, the total becomes 600,000, leaving 100,000 extra data points and $10 in overage at the published rate.

This event-by-event estimate gives engineering and growth teams a shared planning number. Update it when the event plan changes, such as when the app starts sending a new renewal or purchase event.

That gives a small team a concrete planning question alongside usage: which two third-party connections do we need on this plan? The pricing page also makes the contract term plain: no annual contract, and cancellation is available anytime. Those terms suit a founder who wants to begin measurement without signing an annual commitment before the paid-acquisition workflow settles.

Tenjin: free attributed installs, then conversion-based plans

Tenjin suits a team that wants its first estimate to follow attributed paid installs. Its pricing page defines a conversion as a mobile-app install Tenjin attributes to a paid user-acquisition campaign. The page lists the All-Inclusive Free plan at $0 per month, with 2,000 free conversions per month, then $0.04 per additional conversion. It also lists monthly post-payment, no annual contract, and access to Tenjin products for that plan.

Tenjin positions the free plan for small teams, with no credit card required for signup. That gives a founder a way to test the reported paid-install count before choosing a paid level.

With 1,500 attributed installs in a month, the count is within the 2,000-free-conversion allowance. At 2,500 attributed installs, 500 conversions sit above the allowance. Applying the listed $0.04 overage gives $20 for those 500 conversions: 500 × $0.04 = $20.

Tenjin lists paid S, M, and L options with monthly and annual prices. Its pricing page lists monthly options of $200 at $0.02 per conversion, $400 at $0.016, and $700 at $0.014. Teams forecasting paid attributed installs can compare their expected volume with the conversion rates and payment schedule they are considering. At 8,000 Tenjin-attributed conversions on the Free plan, 6,000 exceed the 2,000-conversion allowance, so the overage is 6,000 × $0.04, or $240.

The paid schedule also shows annual options at $2,000, $4,000, and $7,000, alongside per-conversion rates of $0.016, $0.013, and $0.011. Choose the appropriate schedule using the expected conversion volume and the payment timing the team prefers. Tenjin’s explainer says customers can cancel anytime, while its pricing page distinguishes monthly post-payment for the free plan and offers annual paid options. The amount due and billing schedule depend on the selected plan.

Tenjin’s self-serve billing guide says customers can choose monthly or yearly subscriptions. It also says a plan starts on the first day of the next month and the billing screen shows a prorated charge for the remaining days in the current month. For a founder testing attribution partway through a month, that timing belongs in the cash-flow estimate alongside the recurring plan price.

Tenjin fits teams that already forecast paid attributed installs and want the free allowance or paid schedule to use that measure. Use your own attributed-install forecast when comparing the Free overage with the published paid schedules.

Kochava: free limits by conversions and app events, with MAU-based paid options

Kochava’s pricing page lists several measurement and attribution tiers. Foundation starts at $500 per month, and Enterprise starts at $2,000 per month; the page also offers monthly or annual prepayment options.

Kochava’s Free App Analytics page describes monthly usage allotments of 10,000 attributed conversions and/or 500,000 app events. Keep those two limits as separate counters. An app could be below its attributed-conversion allotment while sending many app events, or it could have a different relationship between the two totals. If an account exceeds either free allotment, Kochava says its support team will contact the account about upgrade options.

The free plan gives a small team a way to evaluate the product before moving to paid measurement. The product page says deep linking and deferred deep linking are included, and users can access Kochava SmartLinks for multi-platform deep links. Kochava’s announcement about Free Analytics draws a feature line between free and paid accounts: it lists configurable attribution, real-time fraud abatement through Traffic Verifier, and view-through attribution as paid-account features.

A founder whose primary need is to start app measurement within the free usage limits may value the free plan’s analytics, attribution, visualization, and deep-linking support. A team that requires configurable attribution, fraud abatement, or view-through attribution should include a paid tier in its evaluation, then compare the applicable MAU- or conversion-based price basis and payment term.

Kochava’s Free App Analytics setup page says to create a free account, wait for account approval, add app profiles, integrate the Kochava SDK, and update the app in the relevant app store. Measurement and attribution begin once the app is live with Kochava. This sequence helps a small team plan the work across product engineering and release management rather than assuming attribution starts at account creation.

Choose an MAU-based option when monthly active users are the figure your team forecasts most reliably and the applicable Kochava tier fits your budget. Choose an attributed-conversion basis when paid-acquisition installs are your clearest forecast and that plan’s terms fit.

Compare the bills without mixing units

Use this table as a like-for-like record of each provider’s published bill structure. It keeps different units apart rather than converting them into a shared number.

The most useful next step is to enter your own expected counts in three separate rows. For example, keep a monthly event estimate of 600,000 for Airbridge, a paid-attributed-install estimate of 8,000 for Tenjin, and both attributed conversions and app events for Kochava. The numbers can describe the same app and month, but they do not describe the same action, so each provider calculation should use the input its pricing page names.

Use a campaign-spike forecast as well as a normal-month forecast. For example, assume 400,000 events in a normal month and 750,000 during a campaign; 250,000 events above Airbridge Core’s allowance add $25, for an estimated $65+/mo. For Tenjin Free, a rise from 1,500 to 9,000 attributed conversions moves from within the free allowance to 7,000 above it, or $280 in overage at $0.04 each. For Kochava, record app-event and attributed-conversion totals for both months, since its Free plan gives each count a separate monthly allotment. This stress test shows how a campaign month changes each plan’s bill or upgrade decision.

Then calculate what changes at the threshold. For Airbridge, each 100,000 events above the 500,000-point allowance adds $10 at the published overage rate. For Tenjin Free, each 100 additional attributed installs above 2,000 adds $4 at the listed $0.04 per conversion. For Kochava Free, track app events and attributed conversions against their respective monthly allotments; the paid plan decision can then use the MAU or conversion basis selected for that plan.

Make the unit visible in the budget review

Keep the inputs in separate rows when sharing the estimate with a founder, marketer, or finance partner. Airbridge’s event count can come from the app’s planned event sends, Tenjin’s conversion count follows paid-attributed installs, and Kochava Free App Analytics has separate app-event and attributed-conversion allotments. For Kochava paid evaluation, use the MAU or attributed-conversion basis that applies to the plan.

A practical review can put the expected normal month beside a planned campaign month, then show each provider’s published allowance, price schedule, and payment term next to the matching count. The team can see which counter approaches its threshold and which monthly or annual payment schedule fits its budget cycle. Keeping that comparison tied to the named unit makes changes in instrumentation, paid acquisition, or active users visible in the estimate.

Each model yields its own cost per event, conversion, or active user, so keep the outputs separate in your budget.

Tenjin offers a free tier with monthly post-payment and no annual contract, while its paid options list monthly and yearly price schedules. Kochava lists monthly and annual prepayment options. A lower annual amount can be attractive for a team with stable acquisition, while a team still changing channels may prefer the cash-flow and commitment profile of a monthly option when available.

Which pricing model fits your expected volume and contract preference?

• Choose Airbridge Core if you can estimate app events and want a published 500,000-data-point monthly allowance, a $0.0001 overage rate, two included third-party integrations, and no annual contract. The 30-day free trial and $40+/mo starting price let a small paid-acquisition team begin with a visible allowance and calculate how event growth changes usage charges.
• Choose Tenjin Free if your paid attributed-install count is likely to stay within 2,000 conversions per month and you want a $0 tier with a published overage rate. Calculate the Free-plan overage from your install forecast, then compare it with the published paid schedules and their per-conversion rates.
• Choose a Tenjin paid schedule if conversion-based pricing matches the volume your team forecasts and you want to compare monthly with annual payment options. Use the listed annual schedule to compare the full payment amount and per-conversion rate with your expected volume and cash-flow needs.
• Choose Kochava Free App Analytics if its 10,000 attributed-conversion and/or 500,000 app-event monthly limits suit your present activity and its free features cover your measurement and deep-linking needs. Kochava says support contacts accounts that exceed either free allotment to discuss upgrade options; plan for SDK integration and an app-store release in your rollout schedule.
• Evaluate Kochava paid options if MAU- or attributed-conversion pricing fits your reporting habits, or you need features it lists for paid accounts, such as configurable attribution, Traffic Verifier, or view-through attribution. Foundation starts at $500/month, and Enterprise starts at $2,000/month. Kochava lists monthly and annual prepayment options, so compare the selected term with your forecast and preferred cash-flow cycle.

Before making a choice, write down these five inputs:

1. Expected app events sent per month.
2. Expected paid attributed installs per month.
3. Expected monthly active users.
4. The product features and integrations the team needs on the selected plan.
5. Whether monthly payment, annual payment, or no annual contract best fits the current runway and acquisition plan.

FAQ

Which MMP has the most transparent pricing?

Airbridge Core has the most direct public calculation in this comparison for teams that can forecast app events: $40+/mo after a 30-day trial, 500,000 data points included monthly, and $0.0001 per extra data point, with no annual contract. Tenjin also publishes clear conversion allowances and rates, while Kochava publishes free usage limits and the MAU or attributed-conversion bases for its paid plans.

Are data points, app events, and attributed installs interchangeable?

No. Airbridge defines a data point as an event the app sends, while Tenjin’s billable conversion is a paid-campaign install attributed by Tenjin. Kochava’s free plan separately lists attributed conversions and app events, and its paid options can use MAU or conversion volume.

How much does Airbridge Core cost above 500,000 data points?

Each extra data point costs $0.0001. For example, 100,000 data points beyond the monthly allowance adds $10 to the $40+/mo starting amount.

When does Tenjin’s paid plan beat its free-plan overage?

At 8,000 Tenjin-attributed conversions, the Free-plan overage is $240: 6,000 conversions above the 2,000 allowance multiplied by $0.04. Compare that Free-plan overage with the published paid schedules and their listed conversion rates using the terms that apply to your expected volume.

What should I measure before comparing these three bills?

Record app events, paid attributed installs, and MAU separately for the same month. Then apply each provider’s allowance, overage, paid tier, and payment term to its matching count.

Related reading

Mobile App Revenue Attribution: Cross-Channel ROAS Measurement Guide (2026)

September 19, 2026

When Does an App Need an MMP? Mobile Attribution Guide

September 18, 2026

Adjust Alternatives for Lean App Teams (2026): Self-Serve Plans, Monthly Billing, and Low-Volume Pricing

September 18, 2026