App Deep Linking

App deep linking allows you to launch users directly into another app and can be configured to launch directly into that app’s special event or gameplay mode.

For example, you may have two separate applications, one single player and one multiplayer. If you implement App Deep linking in both apps, a user can join a multiplayer session from the single player app.

Deep linking requires an integration in both the app the request originates from, and the target app. The next sections describes the implementation required for both apps.

Monetizing the use of deep links between apps is not permitted. See Cross-app linking in our app policy topic for more details.

You should obtain informed user consent for accessing links. For cross-app linking, you must provide meaningful information about the destination, including the content rating of the destination app, whether it is a free or paid experience, if the destination app includes multiplayer or voice communications, what user information will be shared with the destination app, and if parental approval will be needed for users under 13.

Additionally, you must comply with our Developer Data Use policy which limits data sharing with third parties. For example, if you share a user ID with the destination app, that app will then become subject to Data Use Check-up for receiving that information. We recommend that you only share a session ID to avoid this if the destination app is not already subject to Data Use Check-up.

The originating app will call the LaunchOtherApp method to launch the other application.

This method launches a different application in the user’s library. If the user does not have that application installed, they will be taken to that app’s page in the Meta Horizon Store.

Once the request has been made, you should check to see if the target application launched successfully. The request will only succeed if the user is both entitled to (owns) and has installed the target app. If the user does not own the app, or has not downloaded the app, they will be directed to the product information page in the 2D Store where they can purchase and download the app.

Apps launched by

will launch as normal, and will receive a notification of type

on the message queue.

All notifications generated by this API will have a launch type of DEEPLINK. This information allows you to direct the user to the proper app location.

If the user is on Link PC-VR device and the user does not own the app, the LaunchOtherApp request returns an error, which should be handled appropriately in your code. If the user does own the app, after receiving the notification that the target app was launched successfully, you must quit the originating app yourself before the target app can continue.

If the user is on a Meta Quest device, and the user does not own the app, or has not downloaded the app, they will be directed to the product information page in the Store where they can purchase and download the app.