Guides and Resources
Start typing to search…

Download availability

Example Download Deal

<Deal>
  <DealTerms>
    <IsPreOrderDeal>false</IsPreOrderDeal>
    <CommercialModelType>PayAsYouGoModel</CommercialModelType>
    <Usage>
      <UseType>PermanentDownload</UseType>
    </Usage>
    <TerritoryCode>GB</TerritoryCode>
    <TerritoryCode>DE</TerritoryCode>
    <PriceInformation>
      <PriceType>TRFR</PriceType>
    </PriceInformation>
    <ValidityPeriod>
      <StartDate>2024-06-02</StartDate>
    </ValidityPeriod>
  </DealTerms>
</Deal>

<Deal>

This element outlines the terms under which a music release is made available for download, detailing the commercial model, usage rights, pricing, and validity period.

<DealTerms>

  • Description: Contains the specific terms and conditions governing the distribution and availability of the release for download.

    • <IsPreOrderDeal>:

      Description: Indicates whether the deal is for a pre-order.

    🚧

    Please note that MassiveMusic does not support pre-orders and as such any release delivered with a pre-order deal will be suppressed until the official start date.

    Example: false - Specifies that this is not a pre-order deal.

    • <CommercialModelType>:

      Description: Defines the business model under which the release is offered.

      Example: PayAsYouGoModel - Indicates a pay-as-you-go commercial model and is the only supported download model by MassiveMusic.

<Usage>

  • <UseType>:

    • Description: Specifies the type of usage allowed under the deal.

    • Example: PermanentDownload - This use type indicates that the release is available for permanent download and is required for a release or track to pass our validation rules to be made available on download services.

  • <TerritoryCode>:

    • Description: Indicates the territories where the deal is applicable.

    • Example: GB, DE - Specifies that the deal applies within the United Kingdom and Germany.

    • Note: When WW or Worldwide is provided, it is interpreted as available in all territories, avoiding the need for extensive lists when there are no territorial restrictions.

<PriceInformation>

🚧

As per your MassiveMusic contract, a rate card will have been agreed upon, outlining wholesale rates for tracks and releases across various currencies. Upon signing the contract, you will receive a list of corresponding price codes. These codes should be included here to specify the intended price point for the release or track.

  • Description: This element contains pricing details for the release.

    • <PriceType>:

      • Description: Specifies the type of price information.

      • Example: TRFR - Indicates the transfer price type.

<ValidityPeriod>

This element specifies the duration during which the deal terms are effective, including both the start and end dates, and optionally, the start time.

  • <StartDate>:

    • Description: The date from which the deal terms become effective.

    • Example: 2024-06-02 - Marks the beginning of the validity period for the deal terms.

  • <EndDate>:

    • Description: The date on which the deal terms expire.

    • Example: 2024-06-02 - Indicates the end of the validity period for the deal terms.

  • <StartDateTime>:

    • Description: Specifies the exact date and time from which the deal terms become effective.

    • Example: 2024-06-02T08:00:00 - Though specified, this will be interpreted as 2024-06-02 00:00:00 local time.

🚧

While this is supported at the ingestion level, due to limitations in how content is delivered to partners, any release containing a time will be made available at midnight local time of that same day. This ensures that content does not go live ahead of the intended time.

Staggered Deals with Varying Validity Periods

In certain scenarios, you may want to apply different pricing or conditions to a release over distinct periods. This can be achieved using staggered deals in a DDEX ERN message, where each <Deal> element specifies its validity period and corresponding price code. This approach allows for flexibility in pricing and availability, ensuring that the release can adapt to market demands and promotional strategies over time. Each staggered deal provides a structured way to manage and market the release according to your strategic objectives. You can see how this would appear in the example below.

<Deal>
  <DealTerms>
    <IsPreOrderDeal>false</IsPreOrderDeal>
    <CommercialModelType>PayAsYouGoModel</CommercialModelType>
    <Usage>
      <UseType>PermanentDownload</UseType>
    </Usage>
    <TerritoryCode>GB</TerritoryCode>
    <TerritoryCode>DE</TerritoryCode>
    <PriceInformation>
      <PriceType>ALFR</PriceType>
    </PriceInformation>
    <ValidityPeriod>
      <StartDate>2024-06-02</StartDate>
      <EndDate>2024-06-03</EndDate>
    </ValidityPeriod>
  </DealTerms>
</Deal>
<Deal>
  <DealTerms>
    <IsPreOrderDeal>false</IsPreOrderDeal>
    <CommercialModelType>PayAsYouGoModel</CommercialModelType>
    <Usage>
      <UseType>PermanentDownload</UseType>
    </Usage>
    <TerritoryCode>GB</TerritoryCode>
    <TerritoryCode>DE</TerritoryCode>
    <PriceInformation>
      <PriceType>ALBU</PriceType>
    </PriceInformation>
    <ValidityPeriod>
      <StartDate>2024-06-03</StartDate>
      <EndDate>2024-06-04</EndDate>
    </ValidityPeriod>
  </DealTerms>
</Deal>
<Deal>
  <DealTerms>
    <IsPreOrderDeal>false</IsPreOrderDeal>
    <CommercialModelType>PayAsYouGoModel</CommercialModelType>
    <Usage>
      <UseType>PermanentDownload</UseType>
    </Usage>
    <TerritoryCode>GB</TerritoryCode>
    <TerritoryCode>DE</TerritoryCode>
    <PriceInformation>
      <PriceType>ALFR</PriceType>
    </PriceInformation>
    <ValidityPeriod>
      <StartDate>2024-06-04</StartDate>
    </ValidityPeriod>
  </DealTerms>
</Deal>

Communicating Track Availability Restrictions

In some cases, you may want to ensure that a track within a release is only available as part of the complete release and not available for individual purchases. This can be specified in the DDEX ERN message by omitting individual track deals and only including deals for the full release.

How to Specify Track Availability Restrictions

To communicate that a track should only be available as part of the entire release, follow these steps:

  1. Omit Track-Level Deals: Do not include individual download <Deal> elements for the specific tracks you want to restrict. Instead, only provide deals for the full release (R0).
  2. Include Release-Level Deals: Ensure that the <Deal> elements cover the entire release (R0), specifying the commercial model, usage type, and validity period for the complete release.
🚧

A deal is still required at the track level for any streaming CommercialModelTypes.

Updated 5 months ago