What you'll be able to do
- Run label spend through artist handles across a whole roster, cleanly
- Know when the artist identity wins, when the label identity wins, and when the node wins
- Keep the standing permission architecture that makes any-release-any-identity a five-minute setup
The short version: The label's structural insight: label spend performs better wearing the artist's face. Partnership ads (DAS 100 Module 7, industrialized here) let every roster campaign run under the relevant artist's handle - and the artist identity wins for nearly everything fan-facing, because fans follow artists, not labels. The label identity has three real jobs: scene curation (the label-as-taste brand), roster-wide moments (compilations, showcases, signings), and the industry-facing layer. The scene nodes (the "[city][genre]posting" moat from DAS 202 Module 5) are the third identity - the top-of-funnel that belongs to no single artist and feeds all of them. The architecture: standing partnership approvals at signing, so release day never waits on a permission flow.
Whose face does the money wear
If this is your first rodeo: partnership ads let one BM's spend render under another BM's handle, with approval and revocability (the DAS 100 Module 7 machinery). At label scale this runs as standing infrastructure: every roster artist approves the label BM's partnership access at onboarding (Module 2's checklist), and from then on any release campaign selects the right face in the identity dropdown.
The identity decision table:
- Artist handle (the default for fan-facing): release announces, presale pushes, the smart-link lane, tour support - the fan's relationship is with the artist, so the ad wearing the artist converts better and reads native. Label spend, artist face, everyone wins, receipts shared (Module 6).
- Label handle (three jobs only): curation moments where the label IS the brand ("new signing," the compilation, the showcase night), roster-wide plays no single artist owns, and industry-facing content (the label's own story). A label handle pushing a single release usually underperforms the artist handle doing the same - the folklore says "build the label brand"; the data says fans follow artists.
- The scene nodes (the moat): the label-owned "[city][genre]posting" accounts from DAS 202 Module 5's third case shape - top-of-funnel culture accounts that feed EVERY roster artist. Node identity carries the discovery lanes (catalog farm, cold release lanes) where scene-native credibility beats both artist and label faces with cold audiences.
›Go deeper: the standing-permission architecture + the offer rule
The onboarding install (once per artist): partnership access approved label→artist BOTH directions where needed, the creative-approval flow written down (who signs off on ads wearing the artist's face, at what notice - the DAS 202 Module 2 Rolling-Stone-screenshot rule, contractualized), and the revocation terms explicit (offboarding without hostage-taking). The offer rule, non-negotiable: no OFFER runs under an artist's handle without their explicit sign-off per instance - identity-level permission is not offer-level permission, and a "50% off" the artist never blessed, rendered in their voice, is how partnerships die in screenshots. The take-home carries the approval-matrix template: which message classes are pre-approved per artist, which require per-instance sign-off. Five minutes at signing; zero fires forever.
From the field
A label ran its priority release both ways as a clean split: identical creative and audiences, half the spend under the label's handle, half under the artist's. The artist-identity half outperformed on every fan-facing metric - cost per click-through, save rate, comment warmth - by margins that ended the debate permanently. The label handle kept its three jobs (its showcase-night campaigns ran fine under its own name; that's curation, its actual lane). And the scene node quietly won the cold discovery leg against both. Three faces, one wallet, each doing the job the audience assigned it - which was the lesson: the audience assigns the jobs; the identity dropdown just complies.
Common mistakes
- Label-handle release pushes on brand-building folklore (fans follow artists; the data has spoken)
- Release-day permission scrambles (the standing architecture exists; install it at signing)
- Offers under artist handles without per-instance sign-off (partnerships die in screenshots)
- The scene nodes underbuilt or underused (the moat that feeds every artist, left unwatered)
- Identity chosen by internal politics instead of audience relationship
Take-home
Roster Partnership Kit - the onboarding permission checklist, the identity decision table, the approval matrix template (pre-approved classes vs per-instance), and the offer-rule card.
Sources & dates
Meta Business Help Center - partnership ads (accessed July 2026) · DAS 100 M7 + DAS 202 M2/M5 cross-references as cited · the architecture is Darkroom practice, presented as such
Learn more
Optional extra credit. Nothing below is required for the quiz, the certificate, or the job - the full lesson is above. This is for the sickos who want more.
- DAS 100 Module 7 - the partnership machinery this module runs at fleet scale