AI songs on Tidal sitting under your name come off through an artist mapping correction, and there are three ways to ask for one. The Report tool inside TIDAL Artist Home is fastest if your artist page is already claimed. A support ticket is the route while it is not. A corrected redelivery from your distributor is the only one that fixes the underlying cause, when the tracks arrived carrying your artist identifier. Tidal’s AI policy, the one that started badging fully AI tracks in July 2026, removes nothing from your page by itself.
Table of Contents
Before anything else, work out which page you are looking at
Open Tidal and search your artist name while signed out, or in a private browser window. Count the pages. Three patterns come up and each needs a different request.
- One page, your catalogue plus tracks you have never heard. Somebody else’s releases were matched onto your page. This is the removal request described below.
- Two pages with the same name, your catalogue split across both. Your own deliveries went out inconsistently. You want a merge, and your distributor is usually the faster route to one.
- One page carrying only material you did not make, with your own catalogue nowhere. Your releases were matched onto a stranger’s page. This is the urgent version, because a listener searching your name is meeting someone else entirely.
Write the URLs down as you go. Every route below asks for them, and hunting for them again later is the part that makes people give up halfway.
How a stranger’s track ends up under your name
Every release reaches Tidal from a distributor wrapped in metadata. When that delivery includes a platform artist identifier, which is the Tidal-side ID for one specific artist page, the release lands on exactly that page and no guessing happens. When the delivery carries only an artist name in a text field, Tidal has to match on the name.
Name matching is where it goes wrong. Two acts called the same thing get folded onto one page. A generated release with a name close enough to yours gets folded in with them. It is automated at both ends, and distributors say openly that the matching is not foolproof.
The obvious explanation is that somebody is impersonating you on purpose, and sometimes that is exactly what it is. You were expecting me to lead with that. Most cases are duller. A release went out with your name typed in the artist field, no Tidal artist ID attached, and a matcher did the only thing a matcher can do with a name and no ID.
The volume behind it is new. Deezer reported roughly 90,000 fully AI-generated tracks arriving daily at peak during June 2026, which was more than half of everything delivered to it that month. Every one of those needs an artist page. Deliberate royalty fraud sits on top of that, and it is why Spotify built a review step that lets artists check releases before they appear under their name.
Route one, the Report tool in TIDAL Artist Home
This is your route if you already hold your page, and the page is worth claiming even if you end up fixing this another way.
Claiming starts at tidal.com/ForArtists. You sign in, search your artist name, confirm which releases you are the primary artist on, and verify yourself through a linked social account or manually. Distributors report that a response can take up to six weeks, so start the claim today and work route two while you wait.
Inside Artist Home, the Report button flags inaccurate content straight to Tidal’s content team, including albums and videos mapped to the wrong page. Where a request needs something only your distributor can supply, Artist Home tells you so. Changes made there take around 24 hours to show in the store, so do not refile on day one because nothing appeared to move.
Route two, a support ticket while the page is unclaimed
Submit through Tidal’s support form and make the request easy to action. A ticket saying “there are fake songs on my page” earns a reply asking for details and costs you a week. Send it all at once.
- The full Tidal URL of every track and album that does not belong to you
- The URL of the artist page they are sitting on
- The URL of your correct page, if a duplicate exists
- ISRCs for your own recordings and UPCs for your own releases
- Your distributor’s name and roughly when your releases were delivered
- A link to a social profile or website tying you to the artist name
Be precise about which tracks are yours. This is where artists damage their own case. Sweeping in a release you half remember, because you cannot immediately place it, turns a clean request into a disputed one, and a content team that catches a single wrong claim stops trusting the rest of your list. Check every ISRC before you press send.
Route three, a corrected redelivery from your distributor
The first two routes ask Tidal to move something that already arrived. This one changes what arrives, and it is the only permanent fix when the bad mapping is baked into the delivery metadata.
Ask your distributor to redeliver the affected releases with the correct Tidal artist identifier attached. Every serious distributor has a process for it, usually filed under artist mapping or profile linking, and most keep a dedicated form. If your own catalogue is the thing sitting on the wrong page, this is the route that puts it back where it belongs.
Timings vary by platform. Amuse publishes rough figures for its own users: Spotify usually within a few days, Amazon Music around four weeks, YouTube a few weeks. Tidal does not publish one.
Here is a piece of genuine reassurance for the waiting period. Royalties are processed through a separate system from artist page display, so your money is not quietly flowing to whoever owns the page your tracks landed on. What you have is a display problem. It is a serious one for discovery and for your credibility, and it is not draining your account.
What Tidal’s AI policy actually does
The policy took effect on 15 July 2026. Tracks Tidal identifies as entirely AI-generated get an AI badge in the interface and stop being eligible for royalty payment. They are also excluded from direct-to-fan sales. Work where a human led the process and used AI tools along the way stays eligible. Tidal has said it will block or remove AI content that exploits a person’s name, voice or likeness, and the same applies to content that deceives listeners or is tied to fraudulent activity such as artificial streaming. Listeners can switch AI-labelled recordings off in Settings, after which those recordings stop playing and drop out of recommendations as they refresh.
So report the tracks as AI and let the policy handle the rest. That is what you were expecting to read. A badge changes what a listener sees beside a track. Which artist page that track is attached to is a different field in a different database, and no badge touches it.
Two things follow. Reporting a track as AI and reporting a mapping error are separate requests handled by separate teams, so file both where both apply. And the policy looks forward, so a page that accumulated junk before mid-July stays exactly as it is until somebody asks for a correction.
Fixing Tidal fixes Tidal and nothing else
This catches nearly everybody. Each streaming service keeps its own artist database and runs its own matching, so a correction on Tidal has no effect anywhere else. The same releases can be correct on Tidal and wrong on Deezer on the same afternoon.
Check every platform you are on before you close the ticket. Apple Music asks for your artist name, your artist page URL, a written explanation and links to the albums that do not belong. Deezer, Spotify, Amazon and YouTube each run their own request path. File them in one sitting using the evidence pack you built for Tidal, because assembling that pack was the slow part and it is already done.
Then set a reminder for a month’s time and look at your pages again. The pipeline that put a stranger’s track under your name has not changed, and the volume moving through it is going up. Catching the next one within a week rather than a year is the difference between a support ticket and an artist page you no longer recognise.