If you want to have this feature, you should use one of the services like Appsflyer or any other that you can find on the WWW, or implement your own for this purpose.

There are nuances when you use services, they have Privacy Rules. For you, this meant that you can’t send more than 10 parameters in URL and all of them can’t have custom names( with custom names, you will be unable to handle these params during all edge cases ), at least Appsflyer has this rule, named UDL privacy protection.

I'm not sure how this mechanism works inside services, but I think it's based on the IP address, because if you open your deep link in one network and then change networks and install and open the app, services will be unable to deliver to your client params. I saw this problem during the implementation of Appsflyer.

This mechanism works in the following manner:

1 - You must implement Universal Link, with details needed for you.
2 - Server side should detect when a user visits your Universal Link, fetch all the needed data for you, user will have some IP address.
3 - You should have a client-side mechanism that will detect launching and make a request to your server side when you match a request by some unique parameter to detect that it was the same user, it will be the IP address, or something else.
4 - Server should return these params to the client side for further processing, or your own logic.

As an example of how this logic works, if you use AppsFlyer:

1 - You create a deep link.
2 - Define rules and params that should be in your UniversalLink using the web client.
3 - Integrate the SDK on the client side and listen response of these params from Appsflyer SDK.

Also, in this case, you should implement the logic of IDFA, it’s needed to catch some params, + you will not have data from SDK if the user changes the network where the link was opened and where the app was installed.

If your application, already installed, it will be handled normally, you will just be redirected to the app by clicking on Universal Link.