App summary

Facebook's in-app linking via URL schema is not officially supported nor documented, and is liable to change or cease working at any time.

We can link to a brand Facebook page within the app only if the app is installed and the unit is served in a rich environment.

There is no way to programatically detect if the app is installed, though we can attempt to launch the app and have a fallback on failure. This behaviour varies from platform to platform, and is least user friendly on:

  • Android on S4 (and likely some other Android handsets), where the user is directed to the app store instead of the fallback.
  • iOS, where the user is presented with an error popup if the app is not installed as below before being directed to the fallback.

Web summary

We can link to a brand's Facebook page.

We can post a link for a user to share, though we are not able to pre-fill the message text without Facebook Connect, as outlined below.

We can access user information and various posting permissions with Facebook Connect, which requires the user to login to use a Facebook app we build. This will prompt a user to login to Facebook's web interface and grant our Facebook app the necessary permissions. Particular types of information or permissions will result in an additional permissions screen, including but not limited to asking for permission to post on the user's behalf.

Using Facebook Connect and asking for user data and permissions is likely to decrease campaign performance given the privacy cost to the user.

Additional approval requirements exist for extended functionality, including:

  • Action Tagging (includes publishing stories)
  • Mention Tagging (includes mentioning or tagging friends)
  • User Messages
  • User Generated Photos
  • Place
  • Explicitly Shared

We can use Facebook's stories API, a subset of Facebook Connect functionality, only once a build is finalised (i.e. no changes after build) and we have our Facebook web app approved by Facebook. According to Facebook's submission process documentation "Submissions are reviewed, on average, within 3 business days".

See 'Additional Capability Guidelines' within the submission process documentation.

Any campaigns that have a site we build shared via social media will need to consider the user experience across ALL devices, inclusive of tablet and desktop, and the associated production cost.

Compatibility

  Android 4.4.4 (S4) Android 4.4.4 (Note 2) Android 5 (HTC One M7) Android Chrome iOS6 (iPhone 4) iOS7 (iPhone 5) iOS8 (iPhone 6+) iOS Chrome
Facebook app - brand page Y (unofficial)

Missing app fallback: Load Facebook app listing in Play Store

Y (unofficial)

Missing app fallback: Load fallback URL in unit

Y (unofficial)

Missing app fallback: Load fallback URL in new page

Y (unofficial)

Missing app fallback: Load fallback URL in new page

Y (unofficial)

Missing app fallback: Load fallback URL in unit

Y (unofficial)

Missing app fallback: Load fallback URL in unit

Y (unofficial)

Missing app fallback: Load fallback URL in unit

Y (unofficial)

Missing app fallback: Load fallback URL in unit

Facebook web - brand page Y Y Y Y Y Y Y Y
Facebook web - Like URL Y Y Y Y Y Y Y Y
Facebook web - Share URL - no pre-fill text Y Y Y Y Y Y Y Y
Facebook web - Share URL - pre-fill text Y Y Y Y Y Y Y Y

Note: Pre-filling share URL text requires Facebook Connect login, as well as extended user permissions. This is a much longer user journey.

Facebook web - Open Graph API Y Y Y Y Y Y Y Y

Note: Open Graph API usage requires Facebook Connect login, as well as extended user permissions in some cases.

Version distribution: Apple version statistics, Android version statistics

Capabilities that are not supported by all platforms are possible but will reduce your reach.

Test unit

'test-schemas' in customads