Submitting Content Takedowns

Review a summary of the supported takedown methods for Audible Magic's Identification and Music Delivery systems.

When submitting takedowns for content registered with Audible Magic, it is imperative to understand the various methods and requirements related to the type of delivery. This article outlines the supported takedown types for both our Identification & Copyright Compliance Systems and Music Delivery Systems. Whether you are updating an asset with a past or future takedown date or opting to remove deals altogether, this guide is designed to ensure accurate takedowns processing. Additionally, we provide detailed instructions for submitting takedowns for video deliveries via our proprietary XML, AM XML v2.21.

Supported Takedown Types

Identification & Copyright Compliance Systems

Below are the DDEX takedown types supported by Audible Magic’s Identification & Copyright Compliance systems. During the onboarding process, you will be asked to note which of these takedown methods you are able to support.

Takedown Type

Description

Past EndDate

This takedown type is delivered as an update to a previously delivered asset. In this new update, an <EndDate> for all Deals and all territories is set to a date in the past, communicating an immediate takedown for the asset.

Future EndDate

This takedown type is delivered as an update to a previously delivered asset. In the new update, an <EndDate> for all Deals and all territories is set to a date in the future, and the takedown will go into effect on that date.

Removal of All Deals

This takedown type is delivered as an update to a previously delivered asset that was sent with one or more Deals, except that the updated

delivery has all Deals removed.

 

Submitting Takedowns for Video Deliveries (AM XML 2.21)

To submit a video takedown via AM XML v2.21, update the <Type> element to "Delete". Here's an example of how your XML should look.

<?xml version="1.0" encoding="utf-8" ?> 
<AMXML xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://registration.audiblemagic.com/schemas/A
MVideoXML2.21.xsd">

<Type> Video</Type>
<Version> 2.21</Version> 
<ContentProvider>Name of Content Supplier</ContentProvider> 
<Video> 
<Type>Delete</Type> 

<VendorVideoID>Unique identifier for video</VendorVideoID> 

<Metadata> 

<Title>TV or Film Title</Title> 
<Description>Description of TV/Film</Description> 
<Episode>Name of Episode</Episode>

<RunTimeDuration format="HH:MM:SS" />

<Language>Language of video</Language>

<ReleaseDate format="YYYY-MM-DD">2024-01-01</ReleaseDate>

</Metadata>

<Content>

<FileName>The name and extension of the media file</FileName>

</Content>

</Video>

</AMXML>

Music Delivery Systems

In addition to supporting all takedown methods that our Identification & Copyright Compliance systems can handle (listed above), Audible Magic’s Music Delivery systems will process takedowns when metadata updates are sent for a previously submitted product that omits a Deal for a Territory. A few examples include:

  • An update to a previously delivered product that omits one or more territories that had one or more active deals on the prior delivery. If an initial delivery had a <UseType> of PermanentDownload and Stream in the DealList for US, CA, MX, then an update to that product only contains those same <UseType> values for US and CA, PermanentDownload and Stream rights for MX would be removed. Thus, the product would be taken down for MX.
  • An update to a previously delivered product that omits one or more <UseType> elements that were included on the prior delivery.
  • An update to a previously delivered product that omits one or more <CommercialModelType> that were included on the prior delivery.

An update to a previously delivered product that omits one or more <CommercialModelType> and <UseType> combination that was included on the prior delivery. 

 

To get more information on other DDEX delivery requirements, click here.