Strategy for a web to keep track of URL parameters from a QR Code after users scan it?

Consider this scenario:

You have a QR code, which contains an URL with some query parameters. The URL is pointed to your own web but later redirected to the third-party that open its mobile APP. After users open the APP, they can connect back another page of your web.

When user connect back to your web service in the APP, you want to know the parameters from the original URL in QR code.

In my case, users can use that APP to scan QR code, so my first instinct is to store the parameters in the session, then check it again after user connected back to the web. In reality, however, there are too many ways to go wrong. Users can easily open first URL in different APP and ended up in different session after they come back to the web.

My question is, what is a good strategy to handle this type of tracking ?