Deal List

The features described in this article are available only to partners who use YouTube's Content Manager to manage their copyrighted content.

The <DealList> defines the key commercial information for each release, such as which territories the release can be made available in, usage rights, and the start/end date for each release. Each <ReleaseDeal> element defines the deals for a release from the <ReleaseList>, which is referenced by its <ReleaseReference>.

Specifying deals for YouTube Red only

On YouTube, streaming operates on a per-track basis, and as such, only deals for individual tracks will be processed; that is, for releases whose <ReleaseType> is TrackRelease.

The <DealTerms> for the track must grant YouTube rights for subscription and advertisement-supported streaming; that is, the terms must include two <CommercialModelType> elements (SubscriptionModel and AdvertisementSupportedModel) with the <UseType> of Stream or OnDemandStream. YouTube ignores any deals for other release types and any other deal terms.

If the <DealTerms> don't specify a start date for the validity period, the deal becomes valid as of the date of reception of the ERN message. If the <DealTerms> don't specify an end date, the deal is valid indefinitely (until further notice).

For details on Start/End Dates and timezone handling for multiple-territory releases, please refer to the DDEX documentation.

YouTube supports ISO 3166-1 alpha-2 country codes for the <TerritoryCode> element. This ISO standard is newer than the ISO 3166-1 standard specified in the DDEX ERN standard. If you include a country code that is no longer valid in ISO 3166-1 alpha-2, YouTube ignores it.

The following example shows the <DealList> for a single track that has different release dates in the United States and Canada.

Specifying deals for Content ID only

To create a reference file for Content ID, the <Deal> for the track must specify the match policy that YouTube should apply to content uploaded by other users that matches the Sound Recording. This can be done in one of two ways:

By referencing an existing Saved Policy from your CMS account using the <DealReference> tag, or

By defining a custom match policy using the <RightsClaimPolicy> tag

Using a saved policy

To apply a saved match policy, use the <DealReference> tag with the policy name (as defined on the Policies page in your CMS account), prefixed by “YT_SAVED_POLICY:”. For example, if you have a policy named “My Saved Policy” in CMS, you can apply it using:

Defining a custom match policy

To apply a custom match policy, you must include a <RightsClaimPolicy> with <CommercialModelType> set to RightsClaimModel and the <UseType> set to UserMakeAvailableUserProvided.

YouTube does not currently support scheduling of match policies. Therefore, to enable a Sound Recording for Content ID, you must provide either an empty <ValidityPeriod/> tag or one with a <StartDate> that is in the past, and no <EndDate>. This will result in the match policy being applied immediately and indefinitely (until further notice).

The XML below will apply a match policy of Monetize regardless of the location of the consumer:

Combined deals for YouTube Red and Content ID

To enable a Sound Recording for both Content ID and YouTube Red, you must send an Audio Album feed that has both YouTube and YouTube_ContentID as MessageRecipients and includes deals for both Content ID and YouTube Red.

To enable a Music Video for both Content ID and YouTube Red, you must send a Video Single feed that has both YouTube and YouTube_ContentID as MessageRecipients and include deals for both Content ID and YouTube Red.

To combine YouTube Red and Content ID dealterms into a single feed using the Audio Album profile, both sets of deals from the above two sections should be linked to the releases that have <ReleaseType> set to TrackRelease.

For example, the XML snippet below will enable a track Worldwide for both YouTube Red and Content ID: