It is relatively simple to achieve download statistics. If you want to bind members to the merchant, the following operations are for reference only.
For example:
Use this link to generate a QR code (distinguish different merchants through parameters key):
What the server needs to do to respond to this link:
Read the value of key to determine which merchant it is;
Record data: The merchant’s QR code has been scanned;
Save the current requested IP;
RedirectAppstoreInstall link.
After the App is installed, the API is called and the server determines:
* Use IP to determine which merchant it is and bind member information.
Disadvantages:
* The same IP can only lock one merchant.
* The network where the App is installed and the one where the App is opened for the first time are not the same, so there is no guarantee that the information will match correctly.
The appstore itself will not provide this content, but if it is an enterprise certificate package, you can use different methods to generate an ipa for each store. This way it can definitely be distinguished. Another method is to create a download interface that records information, and then jump to the appstore through this interface.
This requirement can be achieved through personalized APP installation. When your APP is downloaded through a QR code, you can know which QR code it comes from, and then you can do related processing. The third party in this area has openinstall which does a good job.
This requirement of yours can be easily realized with the personalized installation of the app. Multiple QR codes can be downloaded from the appstore, but the user who downloads each QR code can be distinguished. openinstall provides ready-made app personalized installation sdk
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It is relatively simple to achieve download statistics. If you want to bind members to the merchant, the following operations are for reference only.
For example:
Use this link to generate a QR code (distinguish different merchants through parameters
key):What the server needs to do to respond to this link:
keyto determine which merchant it is;IP;AppstoreInstall link.After the App is installed, the API is called and the server determines:
* Use
IPto determine which merchant it is and bind member information.Disadvantages:
* The same IP can only lock one merchant.
* The network where the App is installed and the one where the App is opened for the first time are not the same, so there is no guarantee that the information will match correctly.
The appstore itself will not provide this content, but if it is an enterprise certificate package, you can use different methods to generate an ipa for each store. This way it can definitely be distinguished. Another method is to create a download interface that records information, and then jump to the appstore through this interface.
This requirement can be achieved through personalized APP installation. When your APP is downloaded through a QR code, you can know which QR code it comes from, and then you can do related processing. The third party in this area has openinstall which does a good job.
This requirement of yours can be easily realized with the personalized installation of the app. Multiple QR codes can be downloaded from the appstore, but the user who downloads each QR code can be distinguished. openinstall provides ready-made app personalized installation sdk