Facebook Verification

From Triangle Wiki

Jump to: navigation, search

Contents

Introduction

Facebook introduced a paid service called the Application Verification Program. This page will outline the key points in a far more condensed fashion than the Facebook official pages.

This optional program is designed to provide applications with a way to stand out and reassure users that they will provide a good experience.

Verification Benefits

Verification Badge
  • Greater exposure within the Application Facebook Directory.
    • Ranking above non-verified applications.
    • Verified badge shown on the application profile page.
  • Two-bucket boost for notifications and request allocations.
  • $100 of Facebook advertising.
  • Discounted conference fees.

Costings

  • Each application submitted will cost $375
  • Fee is payable at point of application and is renewable annually.
  • The fee is non-refundable; even if the application fails.

Data Required for Verification

  • General details and valid credit card.
  • Explanation of all the the data the application calls and use cases for this.
  • Screenshots of all of the major features and key flows within your application.
    • These must be uploaded to a Facebook Photo Album with appropriate comemnts.
    • [Example Album]

Evaluation Criteria

If the application is found to be in violation, Facebook will likely suspend use of certain channels; and you will not be able to submit again for at least three months!

Process

  • Facebook will process the submission as soon as possible. It may take 4 weeks after confirmation via email that the application has been verified and has received the badge, increased notification and request allocations. So possibly six weeks to get verified.
  • If the application passes Facebook will notify when the benefits will be implemented.
  • If the applications fails Facebook may take action, if it is a minor fail then the next steps will be communicated.

Checklist

All areas must be compliant with the Facebook Terms

  • Communication
    • Landing pages from news feed links etc must be relevant to content
    • Content should not be inappropriate; language; trademark violation etc.
    • Grammar and spelling of new feed and landing page content should be correct.
  • Email
  • Can be used for time-sensitive or user requested alerts.
    • Email must be from a Direct action by or for the user.
    • The email must be well formatted.
    • Emails are timely and relate to a time sensitive issue.
    • Is email the best form of communication channel for this content.
    • Opt-in is there an option for the user to opt-in to marketing content
    • Soliciting real email addresses should be explained with a reason as to how they will be used.
  • Requests
  • Requests are used permission need to be granted to change content on behalf of the user. If

content will change anyway a notification should be used.

    • The request should not be forced, and should actually change content.
    • If a non-application user responds the application should not require login.
    • Limit repeat requests.
  • Notifications
  • User to user notifications alert the user of content that has changed.
  • Application to user notifications do not need to be triggered by a social action.
  • News Feeds
    • Story should explain what the user has done and to whom.
    • The story must be initiated from a direct user action.
  • Tabs
  • Allows for a dynamic, feature rich application view about the user.
    • Should primarily show compelling information about the user
  • Profile Boxes
    • Should primarily show compelling information about the user.

External Links

Navigation

Edit Navigation

Personal tools