Sharing Editorial Features from Velveteen
Updated July 17, 2026
When Velveteen receives a trusted FUGA feature update for a UPC that matches exactly one release, it prepares a private sharing kit for the release administrators. The kit lists the editorial destinations, direct links, territories, suggested post copy, and the DSP handle guide. Feature emails are sent from marketing@velveteen.fm after review unless automatic delivery has been explicitly enabled.
Feature updates begin outside Velveteen, when FUGA reports that a release has been selected for a DSP playlist or editorial destination. Velveteen reads only the narrow feature-report mailbox query, validates the sender and report link, and matches the report to your catalog by exact UPC.
How the workflow works
- 1
Velveteen validates the notice
The message must come from FUGA Marketing Services, arrive through marketing@velveteen.fm, and contain a trusted FUGA Score report URL. - 2
The UPC is matched
The report must contain a valid UPC that matches exactly one Velveteen release. Missing and duplicate matches stop for manual review. - 3
Recipients are prepared
Velveteen selects non-staff users with admin permission on that release. One delivery is reserved per recipient and report version so reruns cannot send duplicates. - 4
The sharing kit is reviewed
The private page shows the release, DSP destination, territories, and sharing instructions. Velveteen can send the email, keep it pending, or revoke it. - 5
You share the feature
Open the direct destination, use the suggested copy as a starting point, and confirm each social handle before posting.
What the email contains
- The artist and release title from the sanitized FUGA report.
- Each trusted DSP placement link and its reported territories.
- A private link to the release-specific sharing kit.
- A link to the searchable DSP handle and post-copy guide.
Tip
Privacy, accuracy, and corrections
The sharing page is not indexed, but it is link-accessible. Do not put confidential campaign notes on it. If the release, placement, territory, or recipient is wrong, do not share the feature. Reply to the message from marketing@velveteen.fm so the report can be revoked and checked.
For broader advice and the handle finder, see How to share an editorial playlist feature.
Frequently asked questions
Who receives a feature update?+
Users with admin permission on the exactly matched release are eligible. Editors and viewers are not included, and Velveteen platform-admin accounts are excluded from artist delivery.
Why did I not receive an email?+
The UPC may not match exactly one release, the report may still be awaiting Velveteen review, or your account may not have admin permission on the release. Email marketing@velveteen.fm with the release title and UPC.
Is my sharing-kit page public?+
It uses a long private token, is excluded from search indexing, and can be revoked by Velveteen. Anyone with the link can open it, so share it only with people working on the release.
Can I correct a placement or recipient?+
Yes. Reply to the feature email or contact marketing@velveteen.fm. Velveteen can revoke the page and stop any pending delivery while the source is checked.
Related articles
Overview
The full pitching workflow: what a pitch is, when to submit, what goes in it, and how Velveteen tracks it from draft to delivery.
After you submit
Review timelines, delivery to editorial teams, and what acceptance does, and doesn't, mean.
Pitch status & lifecycle
Draft → submitted → approved → delivered, plus needs work and rejected paths.