Developer Posts

Note: You are viewing the Native version of this topic. To view this topic for Unity development, see Developer Posts (Unity). To view this topic for Unreal development, see Developer Posts (Unreal).

Developer Posts is a feature that enables you to help engage and grow your community. You provide content including text and images and the content displays in the home feed of Oculus Quest, Go and Gear VR devices and on an application’s product detail page (PDP). You can use the developer post analytics to measure the effectiveness of your developer posts.

The following image shows some examples of how developer posts might look to a user.

The following image shows the detail page when a user clicks on a post:

To Create a Developer Post

To create a developer post navigate to your app in the developer dashboard.

1. Under Manage, navigate to Discoverability -> Posts. The following image shows an example:

   

2. On the Posts page, Click Create.

3. For each post, you must provide:

   • Title: A short title for the post.
   • Description: A 2-3 sentence description for the post. This field cannot include HTML or other markup.
4. You can optionally provide:
   • Image: This should be different than your app cover art. It should reflect the content of your post. It must be in 16:9 Aspect Ratio and a 2560 x 1440 24-bit .png file. If it does not meet these requirements, your image will be rejected.
   • Facebook Trailer Video URL: Provide the URL for any video hosted on Facebook, either public or private. A video trailer can help increase engagement with your post. Details about creating a trailer can be found in the Create a Trailer Video section of the in-app content page. You can also see Videos section of the Facebook Publishing FAQs.
   • Start and Stop Time: The time you would like your post to start and end displaying.
   • Deeplink Message: Provide a deep link message that contains the information your app needs to launch a user directly in a new level or experience that you are promoting with the post. If you include this a deep link message, you will need to add code to direct users to the correct location in your app. For more information, see Integrate a Deeplink in Your App Code.
5. Click Save as draft to preview your post before you submit, or Submit for review when you are ready to have your post reviewed.

Integrate a Deeplink in your App Code

If you include a deep link in your post, make sure to implement a hook into your app that listens for a specific launch detail when the app is started.

• ovrLaunchType_Deeplink

When you see these details in the launch event, your app will retrieve the deep link that you defined to direct the user to the appropriate location in your app.

For example:

ovrLaunchDetailsHandle handle = ovr_ApplicationLifecycle_GetLaunchDetails();
if (ovr_LaunchDetails_GetLaunchType(handle) == ovrLaunchType_Deeplink) {
 string deeplink = ovr_LaunchDetails_GetDeeplinkMessage(handle);
  // ...
}

Preview a Post

To see how your content will look before you submit it for review, do the following:

1. Create a post, and select Save as draft.
2. Navigate to Home on your Oculus Quest, Go or Samsung Gear device. The device you use to test should be the same as the app’s target platform.
3. Choose Developer Settings and then View Developer Feed. You must be an admin or developer for your organization to view the feed.
4. (Optional) If you’ve chosen to integrate deep links, you can click through your post to launch your app and test the deep link.
5. When you’re satisfied with the post and deep link, you can submit the event for review and public release.

Content Review

All developer posts will be reviewed by the Oculus team to ensure that it meets the Oculus Content Guidelines and adhere to the Oculus Code of Conduct. Once you submit your post, it will be evaluated by the Oculus team and the status will change to Approved or Rejected when the evaluation is complete.

To Evaluate a Post’s Reach

You can evaluate the success of your posts by viewing the analytics on the main Posts page. For each post you will see:

• Reach - The number of people exposed to this post.
• Unique Clicks - The number of people who performed a click.
• Unique Conversions - The number of people who purchased, installed, re-installed or launched your app, attributed to your post.

Note the following:

• Each of the provided metrics is an estimate, and may not be precise.
• The metrics apply to the last 30 days. This means if you are looking at analytics for an older post, the numbers for Reach, Unique Clicks and Conversions may be very low.