Meta Quest (Oculus) integration with AppsFlyer

App setup

• Create an AppsFlyer account
• Add account users with appropriate permissions
• Add your Meta Quest (Oculus) app in AppsFlyer

SDK integration with your app (via S2S or SDK)

There are two methods of integration you can use: S2S and SDK.

For the S2S method, integrate the AppsFlyer API into your app with commands to report the following events to AppsFlyer.

• First opens
• In-app events
• Sessions

Note:

• First app opens must be reported before in-app events and sessions.
• For the device_ids parameter, select the type custom.
  • The custom generated ID for first opens should match your in-app events, and sessions ID.
  • Send events using the API. Tell your developer which events to send. Verify that when you set up the API, you set up and map the events to send to AppsFlyer. 
  • To report owned media engagements, integrate the impression engagement API.

For the SDK method, there are two versions: Unity, and Unreal.

Note:

If you have an existing user base and therefore want the first session to be considered a session and not an install, the developer can use the method skipFirst=true.

Recommended: A cross-platform landing page running the AppsFlyer Smart Script lets you perform web-to-app attribution. It's most recommended when your campaign promotes an app that's also available on other platforms, like Epic and Native PC.

Learn about cross-platform landing pages

Learn how to set up a cross-platform landing page

Note:

For Meta Quest, the following parameters are required:

• platform: quest
• QUEST_APP_ID: The Quest Store app ID.
  For Quest 2, this is the number in the store URL, for example: 

  https://www.oculus.com/experiences/quest/XXXXXXXXXXXXXXXX/

  where XXXXXXXXXXXXXXXX is your unique app ID.

• media_source

• campaign
• ad
• ad_set
• storefront_redirect_url: The full URL of the Oculus storefront for your app, including your QUEST_APP_ID. For example, https://www.oculus.com/experiences/quest/XXXXXXXXXXXXXXXX/

Link setup