The short version
- Split your fans into a few lists on the platform.
- Make one marked version of the file per list. The versions look identical.
- Send each version to its own list.
- If it leaks, the mark tells you which version, so which list. Smaller lists mean fewer possibilities.
- For top spenders and customs, send one marked copy per fan instead.
Why mass messages are the hardest leaks to trace
A PPV sent to one fan has one suspect. A mass message sent to 800 fans has 800. If every fan got the same file, nothing in the leak can narrow that down. And because mass messages carry your broadest content to your biggest audience, they are often what leaks first.
Option 1: one version per fan list
Most platforms let you send a mass message to a list rather than to everyone. Use that:
- Make lists named something like Trace 1, Trace 2, Trace 3, and spread your fans across them.
- In Trace, upload the video once and choose how many versions to make, from 2 to 64.
- Download each version and send it to its matching list.
- Optional: paste who bought each version into Trace. A match then points to those buyers.
When a version leaks, Trace reads which version it is. That tells you which list it went to, and, if you recorded them, which buyers had it. It doesn’t tell you which person on that list leaked it.
How many lists?
More lists mean fewer suspects per list, and a bit more sending. Eight lists of 100 fans gets a leak down to 100 accounts. Thirty-two lists of 25 gets it down to 25. Put new or unknown fans on smaller lists if you can.
Option 2: one copy per fan for the people who matter most
Customs, DMs and your top spenders can each get their own marked copy. A leak of one of those points to one account. Trace handles both in the same place: lists for the mass message, single copies for everyone else. See per-fan watermarking explained.
Option 3: low-tech visible differences
Some creators change a caption, sticker or emoji per list. It costs nothing, and it works until the leaker crops or re-edits. Leak sites often strip captions entirely. Use it as a deterrent, not as your only record.
How well it holds up
We tested the segment marking used for mass messages and streamed video on a 64-second clip with 1,000 recipients, each with their own pattern. In the 22 Oct 2026 run, 18 of 19 attacks were traced, including screen recording, re-uploads, crops and a 30-second clip (which passed, only just). A phone filming a tilted screen was inconclusive. No wrong recipient was named. Every cell is in the robustness report.
A clean leaked clip of about 30 seconds is roughly the minimum to match a version. Short clips and heavy edits leave less to read.
What not to do with a list match
- Don’t treat every fan on the list as guilty. One of them leaked it, the rest didn’t.
- Don’t announce the list publicly. You tip off the leaker and upset everyone else.
- Do watch the list: split it smaller next time, and see whether the next leak comes from the same group.
If two fans from different lists combine their versions, Trace recognises the mix and names nobody rather than guessing. That is safe, but the leak goes unattributed.
After a match
Narrow it down with your next send, report repeat accounts to the platform, and get the copies taken down. What to do when a paying fan leaks your content covers the order. To see how much of your content is already indexed, run the free exposure scan.
Split your next mass message
Make 2 to 64 versions in Trace, one per list. Free for 3 fans and 2 marked drops a month, with 1 traced leak. Pro is $39/mo with a 14-day free trial.