MMP comparison · · By Cald
Airbridge vs Tenjin: Specs, Pricing and Reviews
Compare a connected web-and-app measurement brief with a lean gaming monetization workflow. Test the overlap before choosing.
Evaluate Airbridge first when your measurement problem spans website and app; evaluate Tenjin first when a lean game studio needs acquisition and monetization cohorts. That is Cald’s editorial starting point. Both document campaign linking, and either may fit a game business. The final decision depends on your required integrations and the purchased package.
This guide combines official specifications and public review findings checked October 30, 2026. We have not performed a controlled accuracy benchmark. Documented features, reviewer opinions and our evaluation advice are identified separately.
Specifications that change the implementation
| Requirement | Airbridge | Tenjin |
|---|---|---|
| Web-and-app collection | The Web SDK collects website attribution and web-to-app activity. Web SDK. | Deferred links pass campaign destination context to the app after installation. Link documentation. |
| Destination handling | Test the desired app destination and website fallback in your actual SDK implementation. | A deeplink_url parameter carries context; the app implements the destination logic. Implementation reference. |
| Game web-shop purchases | Xsolla documents an Airbridge integration carrying purchased SKU, quantity, revenue and currency. Xsolla integration. | Have the vendor demonstrate the exact web-shop purchase feed and identity mapping you require; do not infer support from app attribution alone. |
| Ad monetization | Require a sample from your mediation provider, with the intended revenue source and cohort definition. | Documents SDK ingestion of mediation revenue and supported ad-revenue callbacks. Mediation ROI. |
| Raw data | Confirm Growth export entitlements in the proposal. Plan comparison. | Raw exporter supplies batch event CSV/API access; each requested dataset covers up to 30 days. Export specification. |
Where the tradeoffs become visible
Airbridge: follow revenue across buying surfaces
A game may acquire players through app ads while selling bundles on a website. Xsolla’s official Airbridge integration documents a concrete purchase feed: its web-shop payment event includes item identifiers, quantities, currency and revenue after discounts but before taxes and fees. That gives a useful starting contract for reconciliation, rather than merely knowing that two products integrate.
Our inference: prioritize an Airbridge demo when the hard question is how an app acquisition cohort relates to later web purchases. Ask the vendor to explain the identity path and unavailable relationships. An integration listing does not establish that every anonymous visit can be joined to a player.
Tenjin: inspect the monetization inputs
Tenjin’s mediation documentation says impression-level revenue requires an appropriate SDK integration; it is not collected automatically by default. Its supported provider list includes AppLovin MAX, Unity LevelPlay and AdMob. Check the exact provider and version before treating an empty ad-revenue chart as zero earnings. Mediation setup and provider list.
Our inference: prioritize Tenjin when the team’s recurring work is evaluating paid-acquisition cohorts against advertising revenue and in-app purchases. Ask to inspect the revenue inputs separately, then the combined view. A headline return-on-ad-spend figure is insufficient if the team cannot explain its numerator.
Pricing: different usage models
Airbridge Core starts at $40/month with 500,000 data points, then $0.0001 each. Growth is custom; verify required network, event and export coverage.
Tenjin includes 2,000 monthly paid-attributed installs free, then $0.04 each. Its S plan is $200/month for 10,000; confirm overages and commitments.
These are published starting points, not equivalent quotes. Forecast installs, website activity, app events, purchases and re-engagement separately. Have each vendor identify billable rows. A game generating many sessions or ad impressions needs a usage calculation based on what the proposed implementation actually sends.
Include the cost of collecting and storing the exports your analysts need. Ask for a worked invoice at current usage and a growth scenario, including support, retention and any required package change. Compare the complete workflow rather than interpreting a lower starting subscription as a lower total cost.
What users report on the web
Airbridge’s G2 reviews praise support and linking; some describe slow report retrieval and difficult integrations. These are user experiences, not measured performance guarantees.
Tenjin’s G2 reviews praise support and centralized acquisition reporting; some describe setup effort, iOS integration difficulties and a learning curve.
The reviews involve different teams, plans and implementation dates; review platforms may also include invited or incentivized submissions. We have not assigned a combined score or treated vendor-supplied product descriptions as independent reviews.
Turn those themes into two tasks: have your marketer build a cohort report unaided, and have your engineer trace one missing revenue event. Record the assistance needed and the explanation received. That evidence is specific to the team that will own the system after launch.
Worked pilot: a game with a companion web shop
Synthetic example: a small mobile game runs rewarded ads and sells a starter bundle both in-app and through a web shop. It wants to measure acquisition cohorts without duplicating the bundle’s revenue. This is an illustrative acceptance plan, not a client result.
| Event | Exact trigger | Required context |
|---|---|---|
starter_bundle_paid | Backend verifies a settled bundle transaction, once per transaction ID. | Transaction ID, player ID where permitted, SKU, purchase surface, revenue, ISO currency, UTC occurrence time. |
rewarded_ad_revenue | Mediation callback supplies the chosen impression revenue signal. | Available impression identifier, mediation source, ad unit, reported revenue, currency, UTC time. |
- Link destination: test a bundle promotion with the app installed and absent. Confirm the intended screen or documented fallback, including an unavailable bundle.
- Purchase identity: buy the bundle through the website after an app login. Inspect the relationship each system can legitimately establish; record unresolved identity gaps.
- Duplicate prevention: replay the purchase webhook and reopen the receipt screen. Acceptance: one business transaction under the agreed delivery and deduplication design.
- Revenue basis: reconcile web and in-app purchases using the same treatment of discounts, tax and fees. Record refunds separately instead of silently reducing an earlier event.
- Ad revenue: verify one controlled mediation signal reaches the intended report. Keep mediation and network revenue sources distinct until their definitions are reconciled.
- Operational reporting: export a sample, rebuild the chosen cohort and document delays, exclusions and ownership. For Apple acquisition, distinguish aggregate or modeled measures from eligible event-level data.
Airbridge’s setup guide calls out app timezone and reporting currency as early configuration choices. Agree on both before the pilot; otherwise two plausible reports may describe different days or monetary bases. Airbridge setup guide.
Airbridge or Tenjin: which should you evaluate first?
Take a four-step quiz and watch the fit forecast change with each answer. This is our editorial routing model, not a product benchmark. Your answers stay in this page and are not stored or submitted.
Your evaluation starting point
How this quiz makes a recommendation
The live forecast divides the points from answered questions between the contenders. Before weighted answers, shares are evenly split. These shares are not winning probabilities. Business-pattern points are our editorial hypotheses about where to begin a demo. They are not ratings of accuracy, quality or exclusive capabilities.
| Pattern | Airbridge | Tenjin |
|---|---|---|
| A mobile app with a broad acquisition brief | 1 | 0 |
| An ad-supported mobile game | 0 | 3 |
| A customer journey spanning website and app | 3 | 0 |
| A team consolidating many ad accounts and spend sources | 1 | 1 |
| None of these, or still deciding | 0 | 0 |
The workflow question adds 3 points for its matching evaluation focus: campaign links → AppsFlyer; operations and callbacks → Adjust; cost normalization → Singular; web-to-app → Airbridge; lean game monetization → Tenjin. A focus outside this pair and “no single workflow” add no points. The higher total is evaluated first; equal totals recommend piloting both. The buying constraint changes the demo task, not the ranking. Mandatory requirements can override the result. Website-only answers bypass the comparison.