Ingesting Your Catalog

Recommendation: For any questions about bringing your catalog from the distributors below, please contact us at [e-mail]. Unless detailed below, we are unable to assist with liaising with your previous distributor, and the instructions provided are for guidance purposes only.

1. Overview

Whether you are using Revelator for distribution or not, your catalog must exist inside of our system in order to be able to use our Reporting and Royalties workflows. Revelator has integrations with some of the industry’s largest content providers and/or aggregators so you can easily deliver your data and keep your catalog in sync. If you do not use a supply chain / delivery partner, you may import your metadata and assets (audio & cover art) directly into our platform by using our Google Sheet integration. Please communicate with your Customer Success Manager to discuss your preferences.

There are four ingestion methods to have your catalog within your Revelator Platform:

1. Providing DDEX compliant packages: See the Delivering via Content Providers (DDEX) guide for further explanation on this procedure.

2. Providing Metadata and media files: See the Importing via Spreadsheet guide for this.

3. Using Revelator Pro UI. You will be guided to know how to do this during your onboarding process. Write to [e-mail] for further questions.

4. Using Revelator API (suitable for API customer's only): Refer to Revelator API docs for more information.

Our team will provide API customers the details and troubleshooting necessary to undertake this for additional questions.

Requirement: Ensure that the accounts in Revelator, where your catalog will be allocated, are created/existing. This is the only requirement for the process to be finalized once the content has been sent to Revelator system via DDEX or shared via spreadsheet. This setup can be performed concurrently as the content is retrieved from external sources. API Customers must be compliant with this requirement prior to make any API call. Should you need assistance with creating these accounts, please reach out to our support team for guidance.

Notes

Metadata Important Reminder ⚠️

This is crucial! Regardless of the method used to ingest the catalog, to ensure the success of the migration of the assets, please avoid changing any of the following fields until after your migration. Maintaining these fields as is will ensure the highest likelihood that your new instance will merge with your old instance and maintain its stream count, listing on playlists, and more.

• 🔑 Essential Metadata Requirements

  • Tracks

    For tracks, the following metadata must remain unchanged:

    1. ISRC

    2. Audio

    3. Track Length

    4. Title

    5. Title Version

    6. Artists

    7. Lyrics Language

    8. Parental Advisory

  • Releases

    For releases, ensure the following metadata remains consistent:

    1. UPC

    2. Track Count

    3. Metadata Language

  • Additional Required Metadata:

    1. Any territorial restrictions

    2. Any non-default pricing

    3. Any future release dates

  • 🎧 If Using Revelator's Spotify Deal or Spotify Preferred Provider Program (PPP):

    💡 Once your catalog is ingested, we will run our Spotify Artist Id lookup tool which will return most Ids for your catalog. Please be ready to provide any missing Ids.

    You'll need to include the Spotify artist URIs for artists on a release (or its tracks) with these roles:

    • Primary artist

    • Featuring artist

    • Remixer

  • 🍏 Apple Artist IDs

    💡 Once your catalog is ingested, we will run our Apple Artist Id lookup tool which will return most Ids for your catalog. Please be ready to provide any missing Ids.

    Include the Apple Artist IDs for artists on a release (or its tracks) with these roles:

    • Primary artist

    • Featuring artist

    • Remixer

    • With

    • Composer (for Classical music only)