What you'll be able to do
- Map an artist's full profile network and know what each node is FOR
- Say things through the network that the artist could never credibly say themselves
- Know exactly where the line sits between fan-page strategy and impersonation - and stay on the right side of it
The short version: Modern artist marketing doesn't run on one profile. It runs on a NETWORK: the artist's main pages, plus fan pages, HQ/update accounts, and meme accounts - and ads can run through any node you control. Each node has a different voice and different credibility: a fan page can hype in ways an artist can't say about themselves without cringe. This module maps the network, assigns each node its job, and then does what no other course will: teaches the policy line honestly. Labeled fandom is a strategy. Impersonation is a ban. The gap between them is where careers are made and accounts are lost.
One artist, many voices
Here's the observation this entire track is built on: the messenger is half the message, and an artist ecosystem has multiple messengers available.
An artist posting "my new single is incredible" is advertising. A fan account posting "this single has been on repeat for 72 hours, I'm unwell" is testimony. An updates account posting "[ARTIST] just passed 10M streams" is news. A meme account making the song the punchline of a relatable joke is culture. Same song, four messengers, four completely different relationships to the viewer - and under Andromeda, where the creative IS the targeting (DAS 100 Module 1), each node's native aesthetic finds its own slice of audience.
The majors have run versions of this for years with street teams and fan clubs. What changed: dark posts and partnership ads (DAS 100 Module 7) mean a small operation - a manager, a DIY artist, one marketing person - can run the whole orchestra from one Business Manager.
If this is your first rodeo: you don't need all five node types on day one. Most developing artists need exactly two: the main profiles, run well, and ONE supporting account that fits the artist's world. The map below is the full menu, not the minimum order.
The network map
- Main artist profiles (IG/FB, the canon). The curated self. Announcements, art, identity. Its grid is effectively the press kit - which is exactly why dark posts exist (unlimited ad variation, zero grid clutter - DAS 100 Module 7's founding use case).
- The fan page. Runs on love, real or manufactured-then-real. Can hype shamelessly, react in real time, repost everything, celebrate milestones the artist would be embarrassed to post. Credibility source: enthusiasm. Named honestly: "[artist]updates," "[artist]archive," "[artist]nation" - the name TELLS you it's a fan page, which is both the policy requirement and, counterintuitively, the credibility.
- The HQ / updates account. The newsroom register: tour dates, chart positions, release info, press clippings. Drier than a fan page, more authoritative. For artists with any momentum, this is the easiest node to run because the content writes itself.
- The meme account. Top-of-funnel culture play: native-feeling humor that happens to orbit the artist or their scene. Hardest to run well (comedy is a skill), highest ceiling when it works, because meme distribution reaches people who would never follow an artist page.
- The street team layer. Real humans with real accounts - covered properly in the festival ambassador model (DAS 201 Module 7) and adapted for artists later in this track.
›Go deeper: what each node can credibly SAY (the voice matrix)
The practical tool: before any campaign, assign the message to the messenger. "New single out now" → artist (canon). "This is his best one since [beloved older track]" → fan page (an artist ranking their own catalog is weird; a fan doing it is Tuesday). "[Artist] just sold out [venue] in 4 hours" → HQ (news register makes the flex classy). "POV: you at a [artist] show when [lyric] hits" → meme account (the artist making this about themselves would be trying too hard; the meme account IS the audience talking). If a message feels cringe from one node, it usually belongs to another node - that instinct is the whole skill.
The honest policy section (the one nobody else teaches)
Time to be adults about this. Meta's platform rules include account authenticity and impersonation policies, and the fan-account world lives adjacent to them. The risk spectrum, plainly:
- Clearly-labeled fan/update accounts: established practice. The name and bio signal fan-run status, the account doesn't claim to BE the artist, and platforms have hosted millions of these for a decade-plus. This end of the spectrum is a strategy.
- Ambiguity: the drift zone. Bio vague, name could be official, DMs answered as if you're management, "official" anywhere it shouldn't be. Every step toward passing as the artist is a step toward the enforcement end. Drift is usually accidental - which is why the take-home has a checklist.
- Impersonation: the ban. Claiming to be the artist, mimicking official accounts to deceive, running paid ads that misrepresent who's speaking. This isn't a gray zone; it's the cliff.
The operating doctrine: run supporting accounts the artist's team controls, label them as what they are, and let the labeling do its counterintuitive work - audiences engage MORE with accounts they understand than accounts that confuse them. And one disclosure norm that costs nothing and buys everything: when a fan-node account is team-run and someone asks directly, don't lie. "We help run this one, the love is real" has never hurt an artist. Getting caught pretending has.
Second honesty layer, rights: fan-node content leans on the artist's photos, footage, and music - which is fine when the artist's team runs the node (you have the rights) and a real problem when third-party fan accounts you DON'T control boost content you sent them. That mechanism has a clean version (partnership ads, next module) and a messy version (don't).
From the field
A developing artist's team ran the two-node minimum: main profiles plus one honestly-named updates account. The updates account did one thing the artist couldn't: posted every single stat, playlist add, and city sold out, in the flat voice of a wire service. Within a cycle it became the campaign's workhorse ad identity for news-register messages - "just passed 5M" hits different from a newsroom than from the artist's own mouth. Total additional cost: an hour a week and zero policy risk, because the account never pretended to be anything. The flex got outsourced to a messenger built for flexing.
Common mistakes
- Running everything from the artist's main voice - one messenger trying to be four
- Building five nodes for an artist with an audience that fits in a group chat (two nodes, run well, beats five run badly)
- The ambiguity drift: vague bios, answered DMs, borrowed officialness
- Meme accounts that are ads wearing a meme costume - the audience smells it instantly
- Treating this module's policy section as optional reading (it's the difference between a strategy and an obituary)
Take-home
Artist Ecosystem Map Template - the node map with per-node voice guide, the message-to-messenger assignment matrix, the anti-drift labeling checklist, and the two-node starter build.
Sources & dates
Meta authenticity/impersonation policy areas (Meta Transparency Center, accessed July 2026) · DAS 100 cross-references as cited · network model 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.
- Meta Transparency Center: account integrity and authenticity policies - read the actual rules once; they're shorter than the folklore about them