Adding Aliases to Tracks & Releases

Aliases are secondary identifiers that help you match relevant sales lines to the right Track or Release. For example, if a single Track or Release was allocated two ISRC codes or Catalogue Numbers, or in some reporting you have to map sales based on a DSP code instead, these alternate identifiers can be added on the Alias tab of a Track or Release. This will make sure every time you are being reported revenue linked to alternate identifier, revenue will still automatically be mapped to the right asset in your catalogue.

The most efficient manner to add Aliases to your catalogue happens during your sales ingestion process. The Mapping Manager will flag any identifiers that are not recognised by Curve, and will allow you to map these to the right Track or Release there and then. In the below example Curve does not recognise the four ISRC codes displayed on the right, and asks us to map them to our catalogue via the field displayed on the left. Once you hit Complete or Revalidate, Curve will automatically store this ISRC code as an Alias, and make sure any sales lines for this ISRC will automatically match to the right Track moving forward.

These Aliases can be reviewed or changed via the Alias tab of your Tracks or Releases.

It is also possible to add aliases in bulk using the Alias Mapping excel template. This template can be imported via the Import button on the top right of your Sales > Sales DB page.

If your Aliases do not save as expected, this may be due to a duplicate alias being stored on the Track or Release you are looking to map this new alias to. A duplicate alias will prevent a Track or Release from being saved, so before you can save any changes (such as a new alias) to your Track/Release, you will need to make sure the duplicate alias is removed.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.