To ensure smooth and safe experiences for players on YouTube, all Playables must go through a review process before being publicly launched. This includes required APIs, relevant restrictions, Trust and Safety, Privacy, and other content requirements.
Contact
Review the contact information on the support contact page.
Requirements
The review process is intended to confirm the Playables meet various requirements. Check the navigation to review the different types of requirements.
Test
Use the test suite to validate your integration the with Playables SDK.
Release
Speak to your Partner Manager for details on this process.
Definitions
The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "MAY" and "EXPECT" used throughout these documents are to be interpreted as described in RFC 2119. An abridged list is included below for reference:
- MUST: This word, or the terms "REQUIRED" or "SHALL", means that the definition is an absolute requirement of the specification. If a Playable cannot meet any of such requirements, it will not be allowed to publish on YouTube.
- MUST NOT: This phrase, or the phrase "SHALL NOT", means that the definition is an absolute prohibition of the specification.
- SHOULD: This word, or the adjective "RECOMMENDED", means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. Completing those requirements would help Playables get better visibility.
- SHOULD NOT: This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
- MAY: This word, or the adjective "OPTIONAL", means that an item may or may not be implemented at the discretion of the implementer.
- EXPECT: This word is used exclusively to indicate requirements that YouTube EXPECTS to make required (aka MUST) in the subsequent version of these requirements, but which is optional for this document (MAY).