Untitled

Getting your Catalog on Revelator

Deliver your existing catalog

Bringing your catalog from Fuga into your Revelator account:

- In your Fuga account, set up a contract to deliver to Revelator and then send your content to the Revelator filepath folder

- Please share with me along the way any delivery status notifications

Bringing your content from CI into your Revelator account:

- A folder will be created on Revelator's ingestion server for delivery of your catalog from CI to our platform.

- The filepath of the folder on our server will be

- Please follow the instructions for delivering to Revelator from your CI account provided here.

- Please share with me along the way any delivery status notifications~~

Catalog import template:

Upon request, we can provide a template spreadsheet for batch inserting your catalog:

- Fill out the corresponding fields in the 8 catalog insert tabs by carefully following the instructions and reading any applicable notes throughout.

- If cover image and audio files need to be batch imported into your Revelator account, please confirm whether you are able to set up direct download URL links to the files from a public server (~~Google Drive,~~ Dropbox, Azure, FTP, etc.). If not, we'll have to figure out other options for bringing in the files.

- There is a 'Sample Data' tab for guidance as well.

Delivering content via FTP:

- IP address of our FTP server: delivery.revelator.com

- Username:

- Password:

- FTP protocol: FTP

- FTP port: 221

- Mode: Passive

- filepath directory: I:\CatalogTemplateAssets\kenny (replacing "kenny" with their directory)

- You can add subfolders to your root directory if you would like

Delivered catalog validation

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:

- UPC

- 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.