Fan Pages, HQ Accounts & Meme Strategy

What you'll be able to do

• Build a fan or HQ node from zero to ad-carrying credibility
• Run meme-account top-of-funnel that reaches people artist pages never will
• Keep the whole play inside the policy lines Module 1 drew

The short version: Module 1 mapped the nodes; this is the build manual. A credible supporting node needs an honest name, a consistent register, and a content cadence it can sustain - grown organically until it has enough life to carry paid. Then the pipeline: node content that proves itself organically gets boosted to warm audiences, and winners graduate to proper dark-post campaigns on stable post IDs. The meme node is the hardest and highest-ceiling play: native culture that happens to orbit the artist, reaching people who would never follow an artist page. The policy reprise from Module 1 applies to every word of this module: labeled, honest when asked, artist-team rights only.

The build manual

Building a node that deserves to exist

• The name does the disclosure: "[artist]updates" · "[artist]archive" · "[artist]daily" · "[scene]posting" - the handle IS the label (Module 1's anti-drift rule, enforced at birth). Bio states the register plainly. No "official," ever, anywhere it isn't true.
• The register stays pure: the HQ node never does jokes; the fan node never does press releases; the meme node never does announcements straight. Register purity is what makes each node feel like a real account instead of a marketing channel with costumes.
• Cadence over volume: three on-register posts a week, sustained forever, beats a launch-week flood and a ghost town. Nodes earn credibility with time-in-feed - and per Module 6 of DAS 100, the aesthetic consistency is literally targeting data.
• The organic runway: a node starts carrying ads when it has a real (small is fine) engaged following and a proven content register - a few months of honest life, typically. Boosting a two-day-old account's posts reads exactly like what it is. Patience here is a spend decision: the runway is what makes the later paid media feel native.

The content pipeline (organic proves, paid amplifies)

The operating loop that connects this module to the whole DAS 100 creative doctrine:

1. Nodes post on register, organically. Real accounts doing their thing.
2. Organic traction nominates. The fan-node testimony that popped, the meme that traveled, the HQ stat post that got shared - organic performance is the cheapest creative test that exists (a free exploration lane, in Module 6-of-DAS-100 terms).
3. Winners get boosted to warm - the flash-boost exception from Module 2, capturing live momentum with the artist's engager/viewer audiences.
4. Proven winners graduate to the machine: rebuilt properly in Ads Manager as dark posts on stable post IDs, entering the main campaign's exploitation lane, running as the node's identity to cold audiences.

That pipeline means the node network isn't a side project - it's the campaign's creative R&D department that also happens to be free distribution.

›Go deeper: the meme node, honestly

Why it's the highest ceiling: meme distribution is the only format here that reaches people with zero prior artist relationship - scene-humor travels on its own fuel, and under Andromeda the native-feeling creative finds the scene's whole audience, not the artist's existing one. Why it's the hardest: the audience's spam detector for "ad wearing a meme costume" is flawless, and one on-the-nose promotional post can spend a year of credibility. The working rules: the node's job is the SCENE, with the artist appearing as a natural citizen of it (mostly-scene content, artist-adjacent when it's actually funny); promotion arrives as jokes that would still land if you didn't know the artist; and the drop of an actual announcement is rare enough to be an event. If the team can't be funny in the scene's native register, don't run this node - a bad meme account is negative marketing with a content calendar.

›Go deeper: case shapes that work (anonymized composites)

The testimony engine: fan node posts genuine-register reactions through a release cycle; the three that pop organically become the cycle's best-performing cold ads, because testimony from a labeled fan account reads as discovery, not advertising. The archive play: an "[artist]archive" node posting era content builds a nostalgia audience that becomes the highest-converting warm segment for anniversary/catalog pushes (Module 3's sustain phase, with a purpose-built audience). The scene-node flip: a "[city][genre]posting" meme node built around the SCENE (not one artist) becomes an owned top-of-funnel for every artist and show in the operation's orbit - the node is the moat, portable across the roster. That third shape is the bridge to DAS 203.

From the field

A team built an updates node exactly by this manual: honest name, wire-service register, three posts a week, four months of organic runway before a single boosted post. By the next release cycle it was the campaign's second ad identity, and its milestone posts - boosted modestly to warm - consistently beat the artist-identity equivalents on cost-per-click-through, because "just passed 10M" is news from a newsroom and bragging from an artist. Total build cost: consistency. The register did the rest.

Common mistakes

• Launching the node and the ads the same week (no runway, no credibility, reads as exactly what it is)
• Register drift - the HQ node attempting humor, the meme node posting press releases
• "Official" creep in bios and replies (Module 1's drift zone, entered voluntarily)
• The meme node that's 80% artist promotion (a costume, instantly smelled)
• Building three nodes at launch-week enthusiasm and sustaining zero by month two

Take-home

Fan Page Setup & Policy Checklist - the node birth checklist (name/bio/register rules), the cadence commitment worksheet, the organic-runway gate, the content pipeline as a flowchart, and Module 1's anti-drift checklist reprinted because it belongs in both places.

Sources & dates

Meta authenticity policy areas (accessed July 2026) · DAS 100 + DAS 202 cross-references as cited · build manual 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 authenticity policies - Module 1 told you to read them once; if you skipped it, this module is your second chance