A publisher's name and the account shown on a store listing can differ. That creates a practical scouting problem: a team watching only familiar publisher accounts can miss a game shipped under another account. Here is one real, already-public AppBird example, the evidence available to a reader, and the checks still needed before making a business decision.
Source checked: October 31, 2026. This case uses the saved public example embedded in AppBird's landing page, not a fresh teardown. The landing dataset identifies October 27, 2026 as its generation date; its partner-studio row is dated October 22. Those dates do not establish the binary's build date or a publishing agreement's start date.
The public evidence, field by field
| Field | AppBird's public value | What it supports |
|---|---|---|
| Store-account / developer label | Game town | The account label recorded in the public sample; it is not automatically the game's ultimate owner. |
| Publisher attribution | YSO Corp | AppBird's reported publisher connection for this example. |
| Publisher SDK label | GDMonetization / EverMaker (YSO Corp) | A publisher-related technical signal reported by AppBird; runtime use is not established by this summary. |
| Engine | Unity 2022.3.62f2 | The engine version recorded in the sampled technical summary. |
| Mediation | AppLovin MAX | The mediation technology recorded in that summary. |
| Inventory counts | 27 SDKs; 16 ad networks | Reported inventory counts, not proof that every integration is active or generating revenue. |
Download the dated public evidence excerpt (JSON). It preserves these fields and their source locations so a changing landing page does not erase the example. The excerpt contains no private report, credentials, app assets or additional paid findings.
How to investigate the publisher connection
- Start with the store identity. Record the exact store ID, platform, account name and observation date. The public landing sample identifies this game as Google Play, but does not include its store ID. We therefore preserve its exact title and do not invent a package ID or attach a similarly named store result.
- Separate the account label from the attribution. In this sample, Game town and YSO Corp occupy different fields. Searching only a publisher's own store account would not reproduce that relationship. The useful research result is a connection to investigate, not permission to rename the developer or claim an acquisition.
- Inspect the technical signal. AppBird labels GDMonetization / EverMaker as publisher-related. A complete assessment should check the matching report's platform, app version, analysis date and underlying artifacts, and distinguish active configuration from an unused library.
- Corroborate before acting. Check publisher or studio statements, store history and any ownership-transfer evidence available. The public excerpt alone cannot settle the commercial relationship or its current status.
What the technical summary adds
The engine and mediation fields let a researcher ask a more useful follow-up than simply whether the game exists: is this build relevant to the technical cohort we are studying? Here, the public sample identifies a Unity build and AppLovin MAX mediation alongside the publisher-related SDK label.
These facts can help a studio shortlist games for deeper product or monetization research. They do not reveal revenue, retention, acquisition spend, profitability or which network served an advertisement. The summary does not contain the app version, binary hash or analysis timestamp, so it must not be presented as a reproducible inspection of the latest installed build.
The decision this changes for a scouting team
A publisher-focused watchlist can include this connection for follow-up even though the recorded store account says Game town. A technical researcher can put the game in a Unity/AppLovin MAX investigation queue, then verify the underlying report before drawing conclusions.
That is the value this example demonstrates: connecting discovery, publisher research and technical context in one workflow. It does not demonstrate time saved, investment returns, a complete publisher portfolio or better business outcomes. Those require separate measurements.
What this example does and does not prove
- It documents AppBird's public attribution. The technical and publisher fields come from the same AppBird source. Their agreement is internal consistency, not two independent confirmations.
- It is a dated example. Store accounts, integrations and commercial relationships can change. Recheck a specific game and build before using the result for diligence.
- It does not prove ownership or a contract. A publisher SDK can be a lead. A generic ad-network SDK does not establish a publisher, and a packaged library does not establish active use.
- It does not expose a full teardown. Source files, complete findings, detailed histories and paid datasets stay in the product. No new binary analysis was performed for this article.
Evaluate AppBird against your own research question
Choose a few games your team knows. Check whether the platform can answer the publisher, release and technical questions you actually need, with report availability and dates visible. For professional use, Elite is $399/month for one user and Team has custom pricing, as checked October 31, 2026. Pro is personal-use only. API/MCP workflows require the separately priced API add-on on an eligible plan; see the API documentation.
For a broader purchasing decision, compare our Sensor Tower alternatives, data.ai alternatives and AppMagic alternatives guides. AppBird's publisher and technical research should be assessed separately from iOS revenue-estimate requirements.
Sources and method
- AppBird public landing page, retrieved October 31, 2026. The saved example appears in the page's embedded fallback data and can be superseded by live examples when the page runs.
- Preserved public-field excerpt, including the source-page SHA-256 and observation timestamp. This is a curated excerpt, not the complete landing payload or an independent source.
- AppBird pricing, checked October 31, 2026, for business-use eligibility. Consult current terms before purchase.
Disclosure: this article is written by AppBird about its own product. It is a worked example, not a customer testimonial. Revisions to the example should retain the original observation date and explain changed evidence.