In order to deliver sound recording assets to YouTube Content ID, content owners must enable their YouTube CMS for DDEX delivery. This process is split into two main steps:
Coordination between the content owner, the YouTube ops team, and Random Sounds is necessary in order to complete these steps.
Each step is required, and any misconfigured or missing step along the way will prevent new sound recording assets from being created/monetized on YouTube. Please see the full details for each step below, and contact the Support Team if you have any questions.
Step-by-step
1. Configure an SFTP Dropbox in CMS for DDEX delivery
YouTube provides multiple types of uploader accounts for content delivery into CMS. These uploader accounts are commonly known as dropboxes.
For DDEX deliveries, the CMS must have an active SFTP dropbox.
The list of dropboxes can be found under the Content Delivery > Uploader accounts section of CMS.
If you already have an active SFTP dropbox in your CMS, please share the uploader name with our Support team.
If you do not have an active SFTP dropbox, please contact your YouTube rep to create a new dropbox.
2. Configure the content owner's DDEX Party ID for delivery
To correctly associate sound recording rights with the content owner, YouTube must be able to validate the sender's DDEX Party ID (DPID). Please contact your YouTube rep and ask them to apply your DPID to your YouTube dropbox.
After they have confirmed the DPID has been applied, Random Sounds will verify that this setting is correctly applied in the YouTube delivery target(s).
If you do not have a DPID, please register with DDEX at the link below: http://dpid.ddex.net
📖 Learn more:
What is a DDEX Party Identifier (DPID)? | Random Sounds Support Center
3. Setup the public key in your YouTube uploader account
Go to your Settings > Uploader account and Edit
There, paste the public key that our Support team will share with you, as the image below:
Click Done and then Save your settings.