DSP Declarations & Delivery Changes

DSP declarations are the statements and metadata supplied when music is delivered to digital service providers. Depending on the destination and delivery route, they can describe contributors, release versions, availability, and generative AI use.

For independent artists, the task is to make those answers accurate and confirm that the intended information reaches the service.

A successful upload is one milestone. A correctly presented live release is another. Build time into the schedule to review both.

1. Understand what DSP declarations carry

DDEX’s Electronic Release Notification standard communicates information about releases and their resources, together with the terms describing when, where, and how a release may be offered. These messages commonly travel from a label or distributor to a DSP. Source: DDEX’s ERN overview.

Think of the distributor’s form as an interface to that delivery process.

Some fields describe the music. Others describe its availability or the rights supporting delivery. Review those answers against the approved release plan and the agreements behind it.

Save a dated record of the submission. When a support team asks which version, territory, or date was selected, an exact record is more useful than memory.

2. Check AI declarations with your distributor

YouTube’s music-partner guidance supports Fully Gen AI, Partly Gen AI, and No Gen AI declarations. Missing information is treated as unknown unless other signals support a determination. Source: YouTube’s music delivery guidance.

Ask your distributor which fields it accepts and which destinations receive them. Confirm how to correct an answer after delivery.

Document the production facts before selecting a category. The question is what actually happened during creation, then how the destination instructs partners to report it.

If the dashboard does not provide an appropriate option, ask support for the documented process. Keep its response with the release record.

3. Work backward from the release date

Spotify’s pitching guidance says editorial placement is not guaranteed. It also says submitting a song pitch at least seven days before release gets the song into followers’ Release Radar playlists. Distributor processing must happen early enough to make that step possible. Source: Spotify’s pitching guidance.

G.U.M.M.’s recommendation is to separate four milestones:

• Internal approval of audio, artwork, and metadata.
• Submission to the distributor.
• Any platform pitching deadline.
• Public release.

Give each milestone an owner. Leave room for an incorrect credit, rejected file, or release that has not yet appeared in the artist dashboard.

Ask about holiday schedules and current delivery estimates before announcing a date.

4. Review the actual live release

Once the music appears, open the public links and check the product listeners receive.

Confirm the artist mapping, audio version, track order, artwork, explicit designation, and visible release information. Where practical, check availability in the intended market.

For a mismatch, collect the release identifier, destination URL, expected value, and observed value. Include any relevant distributor message.

Keep the correction open until the result is verified. A submitted ticket confirms that a request exists; it does not establish that the public release has changed.

5. Separate delivery problems from audience results

Low streams alone do not establish that a declaration failed or a platform applied a hidden restriction.

Investigate specific evidence: an unavailable track, incorrect profile, rejection notice, missing release, or documented policy message. Audience response requires its own review of promotion, listener activity, timing, and reporting.

This distinction helps a small team direct its effort. A metadata correction belongs in the delivery workflow. A campaign that is not reaching listeners needs a different investigation.

DSP declarations become manageable when each answer has a supporting record and each release has a final check. The objective is clear: the correct music, on the correct profile, with accurate information and an understandable path for corrections.

Related reading: AI vs AI: New Labeling Rules · Metadata Is Your New Defense