Routine Business Issues #
1.Possible Restrictions When Using OpenInstall #
（1）Test Page Limitation (IP Restricted, System Test Pages Limited to Development Testing, Prohibited for External Release)
Restricts the daily access IP to the test web page links provided by the system. Testing is limited to 20 different IP ranges per day,This limitation is unrelated to payment status.
Solution: Integrate self-developed download pages (H5 web pages) using the "Web Integration" documentation to avoid this restriction.
(2) Test Package Limitation (IP Restricted, Test Packages Limited to Development Testing, Prohibited for External Release)
Restricts the daily installations of packages uploaded to the OpenInstall console. Testing is limited to 20 different IP ranges per day.
Solution: The IP restriction will be automatically removed in the advanced version after passing developer authentication and enabling payment. This restriction cannot be removed for the basic version, and it requires providing the installation package address for configuration in the corresponding download configuration.
(3) Feature Testing Limitation (IP Restricted, Limited to Development Testing Before Payment, Prohibited for External Release)
This prompt only exists in the advanced version. Testing is limited to 20 different IP ranges per day.
2.Data Statistical Rules #
Visits: The number of times the download landing page is opened (number of page visits). Reopening or refreshing the page increases the count (number of OpenInstall initialization).
Clicks: The number of times users click the website download button (number of calls to the m.wakeupOrInstall() method).
Installations: The count of non-redundant app installations followed by app activation upon opening, counted as one installation (automatically reported after successful App SDK initialization).
Registrations: The number of times the registration statistic method provided by OpenInstall SDK is called, with each call increasing the count.
X-Day Retention: Refers to devices that exhibit active behavior X days after the first launch of the App from the installation date. For example, if the user installs the app and opens it again after 10 days, it will generate data for both 1-day and 7-day retention
(e.g., if the installation occurs at 23:00 on the 1st and the app is opened again at 00:10 on the 2nd, it still counts as 1-day retention as the days are not distinct).
Active Devices: The number of devices that have opened the app within a specified time range.
Active Users: Among active devices, the number of devices that have called the registration statistics method.
New Devices: The number of newly installed devices.
IP Distribution: The geographical distribution of installation IPs.
3.Data Deduplication Rules #
Visits, Clicks: Data reported on the webpage (download landing page) is deduplicated based on cookies. Therefore, if the same device accesses the page using different browsers, deduplication cannot be accurately performed.
Installations, Registrations: Data on the app side is deduplicated based on device information (not IP). If the same device triggers reporting statistics repeatedly, the non-deduplicated data will increase. However, deduplicated data will only record the first report from the device; subsequent repeated reports will not increase the data.
4.When using the application parameter passing feature, certain scenarios may result in the loss of parameters for parameter installation or inability to accurately collect data #
While OpenInstall parameter passing boasts high precision in the industry, certain situations may lead to parameter loss. Listed below are such scenarios for developers to take note of and avoid.
(1) If you plan to download the application via the HTML 5 page and launch it online, please do so within 24 hours of download. Otherwise, the application may not be able to retrieve the installation parameters. (This does not affect the High Precision Installation Package download option on Android, which is more stable).
(2) Overwriting installations: If the overwritten application also contains the OpenInstall SDK, overwriting installations will result in the installation parameters being cached from the previous installation.
(3) Do not use jailbroken devices, as they may result in the inability to retrieve parameters. Do not use emulators, as the OpenInstall App SDK filters out data reporting behaviors when the application operates on emulators. This hinders accurate statistical tracking. (Does not affect parameter passing during app installation.)
(4) Download and Installation Process: If you download and install the app through methods other than the download button on the webpage, the correct parameter may not be passed in. To ensure the right parameters are retrieved, click on the download button on the webpage, then proceed to install and open the app.
(5) OpenInstall’s parameter restoration solution also has a low probability of restoration failure (approximately 2%). In such cases, it may fail to retrieve parameters or collect statistics even under normal operating procedures.
(6) If developers disable the use of OpenInstall SDK’s access to the clipboard (which helps with improving parameter restoration accuracy), it can also impact the precision of parameter restoration.
Choosing [High Precision Installation Package] option on Android can help avoid this issue and theoretically achieve close to 100% parameter restoration accuracy.。
Note: If there’s a significant loss of data, please refer to the [Troubleshooting Methods] to inspect potential issues with the HTML 5 page and the application integration. Additionally, ensure that the SDK is updated to the latest version from the official website for more stability.
