100 FAQ using umeng statistical analysis (reply for updates)

Umeng statistical usage process
Http://bbs.umeng.com/thread-55-1-1.html

A summary of common intractable diseases is as follows:

1. FAQs about appkey, channel, and version

Umeng statistics believe that the appkey is the unique identifier of each application. Different appkeys must be used for different platforms of the same application, we recommend that you name the app name-platform (umeng statistics client-android) in the background of umeng. channel refers to the ID of your published marketing and promotion channel and Android platform, if it is not entered in the code, it is recorded as "unknown", and in iOS platform, if it is not entered in the code, it is recorded as "appstore". Due to the particularity of appstore, you can use umtrack (www.umtrack.com) to calculate the promotion effect)
Each appkey only records the initial installation channel on each device, and does not change because it is upgraded or re-installed through other channels;
Version is the version number of each application. umeng SDK uses versionname as the version ID of the application. Detail http://bbs.umeng.com/thread-5413-1-1.html

2. FAQs about page statistics
Android platform: you must collect statistics based on the Code on the document integration page. Otherwise, the SDK cannot perform statistics normally. Note, if your activity has an inheritance or control relationship, do not add the onpause and onresume methods to the parent activity and the child activity at the same time. Otherwise, the startup times may be abnormal. (Eg. When tabhost, tabactivity, and activitygroup are used ). Details: http://bbs.umeng.com/thread-5414-1-1.html

3. view statistical FAQs
Because views are defined by developers themselves, they cannot accurately describe how to integrate them. They can only be said that onpagestart is called for View display and onpageend is called for view hiding. Ensure that, the call of these two methods is not crossover. Details click http://bbs.umeng.com/thread-5415-1-1.html

4. Sending policy FAQs
The default sending policy of umeng is "send at startup" and sends messages at intervals. You can change the policy in the background [set]-[send policy]. Note that when sending messages at intervals, application startup data will still be sent at startup, and page access, custom events, and other data will be sent at a set interval. If the start time is insufficient, the next start will continue to accumulate. Details click http://bbs.umeng.com/thread-5416-1-1.html

5. FAQs about custom events
Before using the Custom Event of umeng, you need to add the corresponding eventid on the Settings> Events page (do not use Chinese characters or special characters and do not use English periods ". "You can use the underscore" _ "). At the same time, the code of the custom event must be written between onresume-onpause (the higher part is for Android) and does not support Statistics in the service.
Each application has a maximum of 500 custom events. Each event cannot have more than 10 parameters, and each parameter cannot have more than 1000 values. Please classify them properly. For specific integration methods, see the integration documentation, click the http://bbs.umeng.com/thread-5417-1-1.html for details

6. FAQs about error statistics
Android:
When developers themselves use uncaughtexceptionhandler to add global exception capture to the program, if the developer first registers with umeng and then registers, umeng will not cover the developer, but if umeng first registers, developers may register with umeng. If you do not need error statistics, you can use mobclickagent. setcatchuncaughtexceptions (false); Disabled. If the developer needs to upload an error, umeng also provides the following method: public static void reporterror (context, string error) // or public static void reporterror (context, throwable E ).
IOS:
Umengsignalhandler is not an error. It is a method for capturing crash. It does not cause crash itself. It captures the crash when it occurs. If you do not need error statistics, use [mobclick setcrashreportenabled: No]; To disable it. Http://bbs.umeng.com/thread-5418-1-1.html

7. No data problems after integration
First, check whether you have used the "integration test". To prevent testing data from being contaminated with official data reports, umeng provides the test mode-integration test and integration test mode, the data of the test device is displayed in "real-time logs" and formatted. the test data is not displayed in the report.
Note that custom events and other data are sent at the next Startup by default, after the event is triggered, close the application for more than 30 seconds and then start printing the log again. [Add the following code at the program entry to enable the debug mode: mobclickagent. setdebugmode (true);] to check whether the "event" field exists. (The error statistics test method is the same. Pay attention to the error field)
Page statistics are sample data with a ratio of 3% to the log. To test page data, use the Integrated Test Mode (http://www.umeng.com/test_devices) Details http://bbs.umeng.com/thread-5419-1-1.html

8. FAQs about the use of idfa SDK for ad-free apps (rejected for submitting an appstore)
Integration documentation see> http://dev.umeng.com/analytics/ios/advanced-integration-guide#5
Please call uiwebview to display it by yourself: + (nsstring *) [mobclick getadurl]; after integration, register the test device to use the integration test mode. After the test device triggers the advertisement page, click "manage"> "Application Management"> "built-in ad switch" in the umeng background to view the corresponding ad switch. After the application is successfully published to the appstore, close the advertisement in the background.
Click http://bbs.umeng.com/thread-5420-1-1.html For more details

9. Why cannot I collect statistics after the umeng statistics SDK is obfuscated?
Too much Code involved, please click instruction document http://bbs.umeng.com/thread-5446-1-1.html

10. Why is umeng's page statistics less than our background statistics?
Android platform: you must collect statistics based on the Code on the document integration page. Otherwise, the SDK cannot perform statistics normally. Note, if your activity has an inheritance or control relationship, do not add the onpause and onresume methods to the parent activity and the child activity at the same time. Otherwise, the startup times may be abnormal. (Eg. When tabhost, tabactivity, and activitygroup are used ).
(Android & IOS) Please note that page statistics are sample data, ratio is 3% of the log, if you need to test page data, please use integrated test mode (http://www.umeng.com/test_devices)
Android page Integration Method for your reference integration documentation> http://dev.umeng.com/analytics/android/quick-start#2.3
IOS page integration documentation> http://dev.umeng.com/analytics/ios/quick-start#2.2
Click http://bbs.umeng.com/thread-5414-1-1.html For more details

11. What is cracking and jailbreak in umeng IOS statistics? (How can umeng identify cracking and jailbreak ?)

1) What is jailbreak and cracking first?
Jailbreak is a technical means to obtain the highest IOS privilege (Root) of Apple's mobile device operating system. After the jailbreak is completed, the device still runs the iOS operating system. A software named cydia (or other jailbreak software) will be installed on the device, using this software, you can perform actions that are not possible before jailbreak, such as installing software other than the App Store, changing the appearance theme, running Shell programs, or even unlocking the carrier's restrictions on the mobile phone network.
The so-called cracking means that genuine apps or games can be freely distributed and installed between jailbreaking devices by removing Apple's encryption protection.
2) How does umeng identify jailbreaking devices and crack apps?
The jailbreak device is jailbroken by installing the jailbreak software. Therefore, it is determined by detecting the path of APT and cydia. App. If apt or cydia is installed, the device is considered to be jailbroken.
The app is cracked by removing Apple's encrypted files. After the app is cracked, its structure will be different from that of a genuine app. The app can be cracked by identifying the structure changes.
3) What are the Identification Errors and errors of jailbreak and cracking?
The error of jailbreak is caused by a third-party small jailbreak tool. (cydia, APT, or webshell are not installed. It is not common./applications/cydia. APP,/private/var/lib/APT/). The error is about 5%.
The cracking error may occur during the development process. In the debug mode, the app will be misjudged as a cracked app, but the error will be very small after the app goes online.
Details click http://bbs.umeng.com/thread-5495-1-1.html

12. Why are there fewer (more) new users in the channels recorded by umeng than in the market )?
Due to different statistical principles, the channel market usually collects downloads, which can only be counted after the user network starts. Therefore, the number of new users added to the channel is usually less than the number of downloads provided by the channel.
However, due to the chaos in the Android Market, we do not rule out the release of packet capture through small channels, which may cause the number of new users in the youmeng statistics channel to be less than the market data. Details click http://bbs.umeng.com/thread-5507-1-1.html

100 FAQ using umeng statistical analysis (reply for updates)