What you'll be able to do
- Convert a nightclub's ad operation from per-show rebuilds to an always-on machine
- Separate the funnels that deserve separation (GA vs tables vs guest list) and merge everything else
- Build the content-and-data flywheel that makes every week start warmer than the last
The short version: A weekly night is structurally an ecommerce store that happens to sell Saturdays - recurring inventory, repeat customers, steady demand. Which means the recurring operator gets to use Meta's machine the way it was actually designed: always-on. One evergreen campaign with rotating weekly creative beats rebuilding campaigns per show, because the rebuild resets learning every single week - permanent day-one, self-inflicted, on a schedule. Layer the flywheel on top (shoot every show for next week's ads, harvest every week's buyers) and the venue becomes the compounding asset the one-off promoter can only envy.
The store that sells Saturdays
Module 1 planted the flag: events aren't ecommerce. Now the exception that proves it - the recurring night IS, structurally. Inventory restocks weekly. Customers repurchase. Demand is steady enough for the algorithm's patient optimization to actually work as designed. Everything in this module flows from taking that seriously.
And yet the standard practice across the industry is to market a weekly like 52 separate one-offs: new campaign every Monday, new ads, sometimes a new "strategy," launched into learning phase, killed Sunday, repeat. DAS 100 Module 5 priced this behavior for you - every rebuild is a learning reset. The weekly rebuild habit means the account spends its entire life in the most expensive, most volatile phase the platform has. It's paying cover every week at your own door.
If this is your first rodeo: "always-on" doesn't mean "set and forget." It means the STRUCTURE persists while the CREATIVE rotates. The machine keeps its accumulated learning; the ads stay current. Structure is the building; creative is the booking.
The evergreen build
- One evergreen conversion campaign for the core GA funnel: broad inside the buyer-zip geo (Module 5), optimizing on the event the budget affords (DAS 100 Module 5), running continuously. Weekly creative rotates IN as new ads; proven concepts persist; the campaign never stops.
- Tables/VIP as its own campaign - the DAS 100 Module 4 exception, earned: different buyer, different economics (one table can out-revenue thirty GA tickets), different creative language. Small budget, high value optimization where the platform sees the values.
- Guest list as a third lane where the venue runs one - it's a data-capture funnel wearing a hospitality costume: cheap signups, owned contact info, door-time demand insurance. Optimize accordingly (signup event), and sync the list weekly per Module 3 of DAS 100.
- Headliner weeks get an overlay, not a rebuild: when the big booking lands, add the headliner creative into the evergreen campaign (riding a fresh post ID that the tour's other markets can stack onto - DAS 100 Module 7) plus, if warranted, a short-flight announce push. The evergreen keeps humming underneath. Residents ARE the evergreen; headliners are weather.
›Go deeper: frequency in a fixed metro
The recurring operator's special problem: the same city sees your ads every week, forever. Frequency management therefore matters MORE here than anywhere else in the track - not by shrinking spend, but by feeding the rotation. The DAS 100 Module 6 refresh system (exploration/exploitation) stops being a nicety and becomes the survival mechanism: a weekly needs a real creative pipeline, which is exactly what the flywheel below exists to feed. Watch frequency weekly in the Module 8 ritual; when it climbs while results sag across the whole account (not one ad), the metro is telling you it's seen this season's wardrobe.
The flywheel
The recurring night's structural advantage, operationalized as a weekly loop:
- Shoot every show. The photographer/videographer isn't a luxury line item; they're the creative supply chain. Saturday's room is next Thursday's ad. (DAS 100 Module 6's phone-shot honesty applies - polish optional, REAL mandatory.)
- Harvest every week. Buyer export → custom audience sync → the warm pool grows weekly (Module 2's habit on a cron job).
- Compound the proof. The evergreen's core post IDs accumulate months of comments - the public guestbook effect from DAS 100 Module 10's war story is a WEEKLY's natural habitat.
- Every week starts warmer. New bookings launch into an audience the last fifty Saturdays built. This is the moat one-off promoters cannot buy at any budget: time in market, compounding.
From the field
A club was running exactly the anti-pattern: fresh campaign every Monday for that week's party, killed after close, 52 launches a year, every one of them living and dying inside learning phase. Same venue, converted to one evergreen GA campaign + a tables campaign + weekly creative rotation: within a quarter the account had stable delivery for the first time in its existence, cost-per-checkout down meaningfully, and - the part the owner actually noticed - Mondays stopped being a rebuild fire drill. The booking calendar changed nothing. The account finally got to remember what it learned.
Common mistakes
- Fifty-two launches a year - paying cover at your own door, weekly
- Nuking the evergreen because one Saturday underperformed (one soft Tuesday is a Tuesday; one soft Saturday is a Saturday)
- Tables and GA in one campaign because "it's all the same night" - it is not the same buyer
- Treating the photographer as a cost center while wondering where ad creative comes from
- Letting the guest list rot in the door app instead of syncing it - that's inventory on the loading dock (DAS 100 Module 3 said it first)
Take-home
Weekly Machine Operating Card (added to Downloads inventory) - the evergreen build spec, the weekly flywheel loop as a checklist, the headliner-overlay protocol, and the frequency watch thresholds.
Sources & dates
DAS 100 cross-references as cited · operating 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.
- Hive's 2026 event-marketer shifts piece (May 2026) - the first-party data centralization argument that the flywheel's harvest step operationalizes