Qimai Data
Research shortlist of China-market options commonly evaluated for this global service. Confirm replacement fit, compliance, and operating constraints before production adoption.
Global service map
Adtrace China: does it work?
. Regenerated with each Chinaready Landscape publish.
Quick answer: Chinaready marks Adtrace Limited for mainland China — not because it is blocked, but because there is no documented mainland deployment path: no China data region, no ICP-filed collection endpoint, and no published integration with the Chinese Android app stores and OEM channels that China attribution actually depends on. Mobile attribution is also the part of the stack where China diverges most from the rest of the world, so a general-purpose MMP rarely transfers cleanly. For China app attribution and store analytics, compare Qimai Data and Umeng+.
Availability in China: Limited
China app attribution when your MMP has no mainland path
Before choosing a tool, it is worth being precise about what breaks. Mobile attribution in China differs from the rest of the world in three ways that no vendor can configure around.
Why China attribution is structurally different
- There is no Google Play install referrer. Google Play is not present on mainland Android, so the install-referrer mechanism most attribution SDKs rely on simply does not exist. Installs arrive through Huawei AppGallery, Xiaomi, OPPO, vivo, Honor, Tencent MyApp, and others, each with its own channel identification.
- No Google Advertising ID. Mainland Android has no GAID. The domestic equivalents are OAID and, on Huawei devices, its own identifier — these are administered through the Mobile Security Alliance rather than Google, and an SDK that only reads GAID collects nothing.
- Ad networks are domestic. Spend runs through Ocean Engine, Tencent Advertising, Kuaishou, Baidu, and Huawei Ads. Attribution is only useful if the tool has working postback integrations with those networks, which is a commercial relationship, not a configuration setting.
iOS is the easier half: the App Store operates in China and SKAdNetwork and ATT behave as they do elsewhere, so an overseas MMP can often cover mainland iOS. Android is where the gap is real.
What the domestic options actually do
| Option | What it covers | Best fit |
|---|---|---|
| Qimai Data (七麦数据) | China app store intelligence and ASO — rankings, keyword coverage, review and version tracking across the domestic Android stores and the China App Store | Understanding store-side performance and competitive position; it is market intelligence rather than an install-attribution SDK |
| Umeng+ (友盟+) | Mobile analytics suite with channel and campaign tracking built for the Chinese Android landscape, alongside product analytics, push, and remote config | Teams that want China analytics and channel attribution from one SDK already tuned to domestic stores and identifiers |
A practical pattern
Most teams do not find one tool that spans both worlds. The common arrangement is to keep the existing MMP for global traffic and mainland iOS, add a domestic analytics and channel-tracking SDK to the China Android build, and reconcile the two in your own warehouse on a shared user or order key rather than expecting either vendor to produce a unified view. Decide up front which system is authoritative for spend decisions, because the two will not agree.
Before committing, verify with each vendor: OAID and Huawei identifier support, per-store channel identification for the app stores you actually ship to, working postbacks with your ad networks, and where the data is stored. Options named here are alternatives-page orientation candidates for research, not Chinaready Explore tiles — confirm replacement fit, data-handling terms, and pricing before production adoption.
Adtrace alternatives in China
Mapped China-ready candidates
Umeng+
Research shortlist of China-market options commonly evaluated for this global service. Confirm replacement fit, compliance, and operating constraints before production adoption.
Related lookups
FAQ
Does Adtrace work in China?
Chinaready marks Adtrace Limited for mainland China. The issue is not blocking — it is that no mainland deployment path is documented: no China data region, no ICP-filed collection endpoint, and no published integration with the Chinese Android app stores, OAID identifiers, or domestic ad networks that China attribution depends on. Verify current China support directly with the vendor before you rely on it, and treat this page as orientation rather than a vendor statement.
Why do overseas attribution SDKs fail on Chinese Android?
Three reasons stack up. Google Play is absent from mainland Android, so the install-referrer mechanism most attribution SDKs depend on does not exist. There is no Google Advertising ID — the domestic identifiers are OAID and Huawei's own, administered through the Mobile Security Alliance rather than Google — so an SDK that only reads GAID collects nothing. And spend runs through Ocean Engine, Tencent Advertising, Kuaishou, Baidu, and Huawei Ads, which require working postback integrations rather than configuration. Mainland iOS is the exception: the App Store operates in China and SKAdNetwork and ATT behave normally.
What are the best China alternatives for app attribution and ASO?
Chinaready Landscape currently maps this page to Qimai Data, Umeng+. Qimai Data covers China app store intelligence and ASO across the domestic Android stores and the China App Store, and Umeng+ provides mobile analytics with channel and campaign tracking built for the Chinese Android landscape. They solve different halves of the problem, so read them as a shortlist to evaluate rather than a one-to-one replacement.
Can I keep one attribution tool for both China and global traffic?
Usually not, and it is better to plan for two. The common pattern is to keep the existing MMP for global traffic and mainland iOS, add a domestic analytics and channel-tracking SDK to the China Android build, and reconcile the two in your own warehouse on a shared user or order key. Decide up front which system is authoritative for spend decisions, because the two will not agree.
Where should teams go after shortlisting China attribution options?
Compare the AppsFlyer, Adjust, Branch, Singular, and Kochava pages, since every overseas MMP hits the same OAID and app-store constraints and their China postures differ. Then use the App Attribution & ASO section of the Chinaready Guide for where this sits in a China stack. If the path remains unclear, book a call with Chinaready.