Client Inclusion for Distribution Channels

Client Inclusion and Distribution Channels

MassiveMusic supports the concept of client inclusion, allowing you as a content provider to specify exactly where your catalogue should be available. This feature offers granular control over who has access to your content, ensuring that your distribution preferences are strictly adhered to.

Benefits of Specifying Distribution Channels

Specifying distribution channels in a DDEX ERN message allows suppliers to control the availability of their content, enhancing the strategic distribution of music releases. By detailing each <DistributionChannel> within the <Deal> section, suppliers ensure their content reaches the desired platforms and adheres to the commercial terms agreed upon. This structured approach provides clarity and precision in managing the availability of music releases across different services and territories.

How to Specify Distribution Channels

This functionality is defined in the <DealList> section of your DDEX ERN XML specification. Within the <DealTerms> section, the <DistributionChannel> nodes are used to include specific partners. To indicate that a track or release is intended for multiple partners, a separate <DistributionChannel> node must be included for each party.

🚧

Please note that the MassiveMusic DDEX party ID PADPIDA2011021601H indicated general availability i.e. this will be made available to all licensed partners not just the 7digital download store.

• Knowledge Requirement: You need to know the DDEX Party ID and Trading Name of the partner you wish to grant or revoke access to. This information is provided by the MassiveMusic Content Partnership team upon approval of a client agreement.

• Supported Use: Note that this feature is supported only for streaming clearances.

<DistributionChannel>

• Description: Details the specific platforms or services where the release will be available.

  • <PartyId>: A unique identifier for the distribution channel.

    Example: PADPIDA2013041601A

  • <TradingName>: The name of the distribution service.

    Example: AudioStreamingService

<ReleaseDeal>
    <DealReleaseReference>R1</DealReleaseReference>
    <Deal>
        <DealTerms>
            <CommercialModelType>AdvertisementSupportedModel</CommercialModelType>
            <Usage>
                <UseType>Stream</UseType>
                <UseType>NonInteractiveStream</UseType>
                <UseType>OnDemandStream</UseType>
            </Usage>
            <TerritoryCode>GB</TerritoryCode>
            <TerritoryCode>DE</TerritoryCode>
            <DistributionChannel>
                <PartyId>PADPIDA2020082011L</PartyId>
                <TradingName>12907</TradingName>
            </DistributionChannel>
            <DistributionChannel>
                <PartyId>PADPIDA20170213063</PartyId>
                <TradingName>6208</TradingName>
            </DistributionChannel>
            <ValidityPeriod>
                <StartDateTime>2024-05-24T00:00:00</StartDateTime>
            </ValidityPeriod>
        </DealTerms>
    </Deal>
    <Deal>
        <DealTerms>
            <CommercialModelType>SubscriptionModel</CommercialModelType>
            <Usage>
                <UseType>Stream</UseType>
                <UseType>ConditionalDownload</UseType>
                <UseType>NonInteractiveStream</UseType>
                <UseType>OnDemandStream</UseType>
            </Usage>
            <TerritoryCode>GB</TerritoryCode>
            <TerritoryCode>DE</TerritoryCode>
            <DistributionChannel>
                <PartyId>PADPIDA2020082011L</PartyId>
                <TradingName>Social Media Service</TradingName>
            </DistributionChannel>
            <DistributionChannel>
                <PartyId>PADPIDA20170213063</PartyId>
                <TradingName>Background Music Service</TradingName>
            </DistributionChannel>
            <ValidityPeriod>
                <StartDateTime>2024-05-24T00:00:00</StartDateTime>
            </ValidityPeriod>
        </DealTerms>
    </Deal>