5 Attribution Pricing Models: E-commerce MTA vs. App MMPs
Compare ecommerce fees based on ad spend, store GMV or scope with app pricing by events, MAU or installs, and choose the unit that matches your forecast.
Choose the pricing unit that follows the outcome you measure.
- Ecommerce attribution tools can price around media spend, store GMV, or a negotiated scope.
- Mobile app measurement follows app activity, such as events, monthly active users, or installs.
- Airbridge Core starts at $40+/mo, includes 500K data points, and charges $0.0001 per additional data point.
- Airbridge Growth uses custom pricing based on MAU or installs.
If your attribution invoice now rivals an ad channel, start by checking what the tool measures and what causes its bill to change. An ecommerce multi-touch attribution tool assigns credit among marketing touchpoints that lead to store sales. A mobile measurement partner, or MMP, connects campaigns to app installs and in-app events. Their pricing units answer different questions, so a spend-based ecommerce fee is not a direct price comparison with an app-event-based MMP.
For an app team buying paid acquisition, Airbridge offers two clearly stated volume paths: Core follows app events sent as data points, while Growth uses MAU or installs for custom pricing. Core is the concrete starting point for a smaller team that wants a published monthly entry price and event allowance. Growth is the quote path when the team wants pricing to follow active users or installs.
The five pricing models below are spend-linked, store-GMV-based, custom enterprise quote, app-event metering, and MAU-or-install pricing. Use the first three to understand ecommerce offers and the last two to compare mobile-app measurement costs.
1. Ecommerce MTA and app MMPs measure different outcomes
Ecommerce multi-touch attribution (MTA) looks at marketing interactions that happen before an online purchase and assigns credit among them. Google Analytics describes an attribution model as a rule or data-driven algorithm that assigns credit to touchpoints along a user's path to an important action. For an ecommerce team, that action is typically a store purchase, and the touchpoints may include more than one paid channel.
The choice of credit rule changes the channel report, even when the sale itself stays the same. Google's legacy Multi-Channel Funnels guide explains that its Last Interaction model gives all credit to the final touchpoint, while First Interaction gives credit to the touchpoint that began the path. That is why an MTA price should be judged against the order revenue and channel questions it helps you analyze, rather than only by a fee-percentage headline.
An MMP addresses app acquisition and user activity. Samsung Ads' MMP integration documentation describes an MMP as a third-party provider that measures campaign performance based on how users interact with an app. It identifies installations, app opens, in-app events, and purchases as user events. Singular's MMP explainer likewise describes app installs, engagement events, purchases, and ad interactions as mobile events an MMP helps marketers measure.
AppsFlyer’s mobile attribution page describes mobile attribution as identifying the campaigns that drive app installs, in-app events, and revenue. AppsFlyer's attribution-model documentation defines the model as the rules that assign credit for an event to touchpoints in a conversion path. These are app outcomes, so an app MMP bill can follow app usage even when a media budget remains steady.
AppsFlyer's Rockerbox integration guide calls Rockerbox a marketing and analytics platform for mobile and web apps. For a subscription app, compare the store purchase outcome with app outcomes such as attributed installs, in-app events, and revenue.
2. Spend-linked ecommerce pricing
A spend-linked contract ties its fee to eligible advertising spend. When a vendor charges a percentage, calculate the fee by multiplying eligible spend for the billing period by the contracted rate. A tiered offer follows the spend bands in its schedule, so the quoted formula determines how the bill changes as budgets move.
For example, assume a hypothetical provider charges 1% of $10,000 in eligible monthly advertising. The fee is $100 for that month. If eligible spend rises to $20,000 and the rate stays at 1%, the fee becomes $200.
Put the offer’s eligible channels, spend figure, rate or tier, billing period, and any minimum or true-up on one line. Compare that amount with the ad channel’s billed spend for the same period, so the vendor invoice and media charge use a matching time window. For example, use the final amount billed by the channel for the invoice month, alongside the same month’s eligible-spend calculation. Keep a budget forecast in a separate line from actual billed spend, especially when your team changes campaign budgets during the month. This comparison shows which part of a software charge follows media spend and which part comes from another term in the offer.
A spend-linked bill fits an ecommerce team that wants its attribution cost to follow eligible media spend. Store-GMV pricing fits a retailer that wants the pricing tier to follow annual store revenue. A subscription app can instead choose an MMP meter based on app events, monthly active users, or installs.
3. Store-GMV pricing follows sales volume
Triple Whale publishes a store-revenue pricing model rather than an ad-spend percentage. Its pricing page says prices depend on annual GMV and the selected Foundation, Automate, or Enterprise package. GMV means gross merchandise value, the store-sales measure used for the pricing tier.
That basis creates a different cost pattern from a fee tied to paid media. If a store's GMV grows while advertising spend stays level, a GMV-tiered subscription can move to a higher revenue tier. If ad spend rises while GMV stays within the same tier, the basis described on the page does not automatically track that increase as a percentage fee. The outcome depends on annual GMV and package, rather than media budget alone.
Triple Whale says its Foundation, Automate, and Enterprise subscriptions run for 12 months. Customers can choose monthly billing or annual billing, with two months free for annual billing. Annual prepayment locks the selected revenue tier for the full year.
Triple Whale says businesses move automatically to plans aligned with their revenue tier as they grow. For a store planning a seasonal promotion, compare forecast annual GMV with the selected package and keep the monthly payment amount beside the 12-month subscription term. That comparison separates the amount charged on a monthly or annual billing cadence from the length of the paid subscription. It also helps a founder see whether the store-revenue tier and planned cash outlay fit a normal trading year as well as a stronger sales year.
Triple Whale's model is a useful fit when the store's revenue scale is the pricing signal the team wants to follow. It is less directly comparable with app event pricing because GMV measures sales value, while a data point measures an app event sent. If a subscription app also sells through an ecommerce storefront, separate the store tool bill from the MMP bill and identify each product's meter before adding both to acquisition cost.
4. Enterprise MTA custom quotes
Triple Whale’s pricing page bases prices on annual GMV and the selected Foundation, Automate, or Enterprise package. It describes Enterprise as a dedicated package that includes everything in Automate, plus Compass, multi-brand reporting, and procurement-grade security and controls. The page defines Compass as unified measurement across attribution, MMM, and incrementality testing. Its listed controls include SOC 2 Type 2, SSO, comprehensive audit logs, and custom security review. The combination suits a multi-brand organization that needs measurement and access controls in the same package. A buyer can compare those named deliverables with its required reporting and procurement workflow, then relate the selected package to annual GMV when reviewing the price basis.
Triple Whale’s comparison of its offering with Northbeam describes Northbeam’s measurement scope as MTA, MMM+, and incrementality. The comparison sets out those capabilities as distinct measurement approaches, giving a buyer a practical scope list for reviewing a measurement proposal. Ask which deliverable addresses channel touchpoint credit, which covers broader marketing measurement, and what the incrementality work is designed to answer. A team can then compare the quoted work with its own questions about store sales and paid acquisition.
For an enterprise proposal, match each line item to the work your team needs: path-level attribution, MMM, incrementality, multi-brand reporting, or security controls. Record the quoted package, annual GMV basis, subscription term, billing cadence, and any separate charges beside the included work. This keeps the decision grounded in both the commercial basis and the actual measurement scope the team expects to use.
Normalize a 12-month commitment by dividing the total by 12, then compare that monthly equivalent with one ad channel’s billed media spend for the same period. Keep onboarding and add-on charges on separate lines so the recurring package cost remains clear. Use the same calendar month for software and channel amounts, or divide both by the number of covered months when the agreement and channel budget use a different period.
For example, a hypothetical $24,000 commitment for 12 months averages $2,000 per month before separate charges. That gives a founder a consistent period for comparing the software commitment with channel spend while keeping each product’s measurement scope visible. A $2,000 monthly equivalent can be larger than a small channel’s budget and still fund several measurement jobs, so keep the scope beside the number when reviewing the tradeoff.
5. Airbridge Core bills by app events
Airbridge Core gives app teams a usage meter they can estimate from event volume. The Airbridge US pricing page, observed October 1, 2026, lists a 30-day free trial, then $40+/mo, with 500K data points included and a charge of $0.0001 for each additional data point. Airbridge defines one data point as one event the app sends. The page notes that actual usage depends on which events the team tracks.
That unit keeps the forecast tied to activity arriving from the app rather than to the ad budget. If a team sends 620,000 events in a month, the first 500,000 fit within the allowance and 120,000 are above it. At $0.0001 per extra data point, the usage portion above the included amount would be $12; the indicated base begins at $40+/mo, so a simple estimate is the listed base plus that $12 usage charge. The example assumes each sent app event counts as one data point and uses the published US pricing terms.
Two apps with similar active-user counts can send different monthly event totals when their event mix differs. An event-based estimate therefore works best when it reflects the instrumentation your app plans to keep sending, including any planned changes in event types.
Use a recent month of app event logs to estimate ordinary and high-activity usage, then compare the event totals by name. Mark the event types your product and growth teams use in attribution or funnel reporting. Separate purchase and subscription activity from diagnostic events that do not inform growth reports in your workflow. Review the instrumentation planned for upcoming product releases and adjust the high-activity estimate when a release adds or changes event types. This gives the team a concrete event-volume forecast for monthly budget planning.
Airbridge says Core has no annual contract and can be canceled anytime. The plan gives a small team a way to begin with a monthly commitment while it measures actual event volume. Core fits teams that can estimate event sends and want their app measurement charge to follow those sends.
Compare the estimated Core subscription and usage total with the channel’s billed spend for the same month. Then judge the cost against the app measurement your team needs, including attributed installs and app-event reporting that inform acquisition decisions.
6. Airbridge Growth uses MAU or installs
Airbridge Growth offers custom, volume-based pricing based on MAU or installs, according to the Airbridge pricing page. This gives app teams a pricing path based on app scale alongside Core’s data-point meter.
Choose Core when event sends are the clearest way to forecast your measurement volume. Choose Growth when MAU or installs better describe the scale you plan to bring to the measurement workflow. For example, a team that already forecasts acquisition in installs can place that figure beside a Growth quote, while a team that plans around the size of its active audience can use its MAU forecast. A Core estimate instead starts with the event instrumentation and the number of events the app sends. Build normal and peak estimates using the unit that appears in the selected plan’s published pricing basis.
The pricing page lists 330+ ad networks and platforms, custom event tracking, multi-touch and touchpoint reports, and raw data export among Growth additions. The listed export destinations include S3, BigQuery, and Snowflake. An app team can compare those capabilities with the measurement work on its roadmap, such as adding networks, analyzing multiple touchpoints, or moving raw attribution data into its warehouse.
Prepare ordinary- and peak-month forecasts for MAU or installs, the two published Growth pricing bases. Compare the quote against both forecasts and your expected monthly app acquisition budget. Keep the forecast counts separate, so the normal estimate describes ongoing scale and the peak estimate represents a launch or seasonal acquisition push. Put the quote’s stated billing period beside each estimate, then compare its monthly equivalent with the same period’s channel spend. This makes the app-volume basis visible when the team decides whether to request a Growth quote.
Airbridge’s two plans let a team align its price forecast with its measurement roadmap. Weigh the next required network and reporting features alongside the expected volume, then choose the Core terms or Growth quote that matches both.
7. Match the price unit to your channel budget
A billing unit can make an attribution invoice rise for reasons unrelated to the channel that triggered your review. Spend-linked ecommerce pricing moves with eligible media spend. GMV-based pricing follows the store's annual sales tier. Enterprise pricing follows the scope and terms in a negotiated agreement. Airbridge Core follows app events sent, and Airbridge Growth follows MAU or installs.
| Pricing model | What moves the bill | Best fit | Budget comparison |
|---|---|---|---|
| Spend-linked ecommerce offer | Eligible ad spend multiplied by the contracted rate, when the offer uses a percentage | Ecommerce team that wants attribution cost to follow media scale | Apply the offer’s rate or tier to eligible spend for the same billing period |
| Triple Whale store-GMV plans | Annual GMV and selected package | Store team whose pricing tier follows annual sales | Compare projected annual GMV and package with the 12-month subscription and chosen billing cadence |
| Triple Whale Enterprise package | Annual GMV and selected package; package includes Compass, multi-brand reporting, and security controls | Team that needs the listed enterprise measurement and reporting scope | Compare the package scope and price basis, then normalize the 12-month cost to a monthly amount |
| Airbridge Core | 500K data points included, then $0.0001 per extra point; one point per event sent | App team that can forecast monthly event volume | Estimate ordinary and peak event counts against the allowance and per-point charge |
| Airbridge Growth | Custom, volume-based pricing based on MAU or installs | App team that forecasts scale using those app-volume units | Compare a quote against your ordinary- and peak-month MAU or install forecasts |
Use the worksheet below to compare the attribution invoice to a channel budget. It separates assumptions you can measure in your own app from commercial terms the vendor must provide.
| Input | Your estimate or term |
|---|---|
| Monthly ad spend for the channel you are comparing | |
| Spend-based offer rate or tier, eligible media, and spend period | |
| Store's forecast annual GMV and GMV pricing tier | |
| App events sent in a normal month | |
| App events sent in a peak month | |
| Events the app sends that are needed for attribution or reporting | |
| Growth forecast for monthly active users or installs | |
| Contract length, billing cadence, renewal, and cancellation terms | |
| Monthly equivalent for any annual or custom quote |
For a spend-based quote, calculate the fee using the agreed eligible spend for that month. For a GMV subscription, compare the plan tier and 12-month subscription terms with annual store revenue. For a custom quote, divide the commitment by its billed months and list one-time charges separately. These calculations let a finance lead compare the same month of software and media costs without treating different attribution jobs as identical.
For that comparison, use the ad platform's billed spend for the same calendar or contract month as the attribution invoice. A budget target, a daily pacing number, and final billed spend can differ when teams pause campaigns or shift budget midmonth. Keep the observed charge and the forecast in separate rows so a planned increase does not look like a cost already incurred.
A practical decision rule is to choose ecommerce MTA when the question is how channels contribute to store sales, and choose an app MMP when the question is which campaigns drive attributed installs and app activity. Among Airbridge plans, use Core when event sends are your clearest forecast, and request Growth pricing when MAU or installs better represent your scale or you need its broader listed measurement scope.
FAQ
Is Airbridge Core a percentage of my ad spend?
No. Core starts at $40+/mo, and its usage charge follows data points, with one data point for each app event sent.
Does 500K mean 500,000 active users?
No. It means 500,000 data points per month. Airbridge defines each data point as one event sent by the app, so one person can generate multiple points through multiple events.
Is Airbridge Core an annual contract?
No. Airbridge states that Core has no annual contract and can be canceled anytime. The plan includes a 30-day free trial before the listed $40+/mo pricing.
When should I request Airbridge Growth pricing?
Request Growth pricing when your team wants a custom price based on MAU or installs, or it needs the broader scope listed for Growth. Use your expected normal and peak month counts so the quote reflects the scale you plan to run.
Can I compare an MMP invoice directly with one ad channel?
Yes, for budget control, if both figures cover the same billing period. Compare the MMP charge with the channel’s billed spend for the same billing period, then interpret the amount using the MMP’s stated billable unit.
Get Started Free
See how these criteria hold up on the real thing.
