Setting up your Supply Chain

Connecting you to DSPs

Revelator can power your digital supply chain if you have direct deals with DSPs or are a Merlin member. It can act as your digital distributor If you don't have relationships with DSPs,

Revelator can also sit on top of your existing distribution or delivery setup, and work just as your reporting and royalties platform, by connecting you to your streaming data and financial reports, streamlining and accelerating your team’s business operations workflows.

Please fill out the information in this Distribution worksheet to help us understand if you will be delivering under your own deals or distributing using Revelator deals.

Please make sure that your metadata is correct before distributing any legacy content via us. Also note that you will NOT be able to update/takedown any of your legacy content via us unless you migrate that catalog to us first.

Certain DSPs need to receive your full catalog via our connection with them before they'll accept any updates/takedowns from our feed for your content.

While you may deliver NEW releases, contact your Customer Success first if you need to do any updates/takedowns with your legacy catalog.

Connecting your Digital Supply Chain

Direct distribution

- please provide your DPID (DDEX Party ID) and DDEX Party Name

- list the DSPs you have direct deals with that you will be using for distribution

- If there is a direct deal in place with Spotify, please provide your Spotify Licensor Name and Licensor ID

Administrative review of releases before distribution

Will your administrator account do manual reviews of releases in an inspection queue before distribution?

Delivery with Revelator's deals


- Your administrator account is required to have a release inspection queue for manually approving releases sent for distribution in order to prevent invalid distributions to DSPs

Direct distribution


- You need to decide whether your administrator account should have a release inspection queue for manually approving releases sent for distribution in order to prevent invalid distributions to DSPs

DSP Status per UPC

For any UPC, our system displays on which DSP the release is live (and also from which DSP it has been taken down).

**Provide a status of each UPC so that we can populate this information in the system.** Otherwise, your users will wonder why it doesn't show on which DSP their historical releases are live/takendown.

- If you CAN provide this information, please try to provide as much as possible of the following:


- DSP name

- Date distributed to that DSP

- Date takendown from the DSP (if applicable)

- If you CANNOT provide this information, please let us know and we will add a note explaining that this information is not displayed for historical catalog. BUT NOTE that this will make it impossible to issue takedowns for historical catalog without a support ticket.

If this doesn't apply to you, skip to the next section.

Last updated