What you'll be able to do
- Run tour and show ads from the artist's side of the table without duplicating (or fighting) the promoter's spend
- Split multi-market budgets by data and coordinate the two-party ad reality every show actually has
- Harvest every market so the next routing starts warmer
The short version: This module is DAS 201 viewed from the artist's chair. The mechanics transfer whole - lifecycle, geo doctrine, per-market splits, the final 72 - with one structural twist events promoters don't have: most shows have TWO parties able to spend (artist team and promoter/venue), which means the defining skill is coordination. Who runs what, whose pixel sees the checkout, whose post IDs carry the proof, and how you avoid the genuinely dumb outcome of bidding against your own show in the same auction. Plus the artist-side superpower the promoter can't match: the network. Announcements from the canon, testimony from the fan node, roll-call comments compounding market to market.
The same show, the other chair
If you've taken DAS 201, this module is a translation layer, and a fast one. If you haven't: the full events doctrine lives there, this module cites it constantly, and the artist-track certificate only requires THIS module - but the sickos should read the whole track. (You know who you are.)
If this is your first rodeo: "the advance" = the logistics thread between artist team and promoter before a show. This module adds a marketing paragraph to it - and that paragraph is most of the module.
The two-party problem
Every show has up to two ad operations: the promoter/venue's (DAS 201's whole world) and yours. Uncoordinated, the failure modes are expensive and common:
- Auction friction: both parties running conversion campaigns at the same city's warm audiences = overlapping delivery competing for the same eyeballs (DAS 100 Module 4's self-bidding problem, now with two credit cards)
- Split proof: two separate announce posts each accumulating half the social momentum (a direct violation of everything DAS 100 Module 7 holds dear)
- Attribution soup: two pixels, two report decks, one pile of tickets, and a settlement conversation where both parties' dashboards claim the same sales
The fix is one paragraph in the advance - the take-home has the copy-paste version. The shape of the deal: agree who runs what layer. The common sensible split: promoter runs the local machine (their geo data, their venue audiences, their weekly infrastructure per DAS 201 Module 6), artist team runs the network layer (canon + nodes, cross-market creative, the national warm pool) - with partnership ads letting promoter spend run under the artist's handle where that's the stronger identity (DAS 100 Module 7's machinery, pointed at coordination). And ONE announce post ID, shared, that both parties' spend stacks proof onto - the cross-account post ID mechanic exists precisely for this.
›Go deeper: whose pixel sees the checkout
The DAS 201 Module 2 tier problem, two-party edition: usually the promoter/venue's ticketing relationship controls checkout tracking, meaning THEIR dataset sees purchases and yours sees your smart-link/landing clicks. Don't fight it - architect it: your campaigns optimize on what your side can see (link-outs, landing views - Module 4's walled-garden doctrine transfers exactly), the promoter's purchase data arrives via the advance's report-sharing clause, and the artist side's real harvest is the AUDIENCE (engagers, viewers, market-tagged warm pools) plus whatever buyer data the deal shares. Ask for buyer-list sharing in the advance; the worst they say is no, and promoters who've taken DAS 201 Module 10 understand exactly why you're asking.
The network advantage, on tour
What the artist side brings that no promoter can: the Module 1 orchestra, now geo-split. The canon announces the routing; per-market dark posts (artist identity, market geo per DAS 201 Module 5) localize it; the fan node testifies ("[city] you are NOT ready"); the HQ node wires the sellouts as they land - and each sellout becomes ammunition in every remaining market. The roll-call effect from DAS 100 Module 7's tour story is this module's centerpiece mechanic: one announce post ID across all markets means the fan in city nine scrolls past an announcement carrying eight cities of "already got mine." The tour promotes itself forward.
Budget across markets runs on DAS 201 Module 5's rebalance ritual unchanged: weekly, money to the sellthrough gaps, throttle the near-sellouts, ego nowhere in the spreadsheet.
Harvest, per market
DAS 201 Module 10's ritual, tour edition: every market's engagers, viewers, and (where shared) buyers get tagged BY MARKET into the warm pool - because the next routing through that city starts with retargeting the last one's room. A tour that harvests is routing intelligence: the markets where warm pools run deep and cheap are telling the booking conversation something real. That's the quiet endgame of this module - the ad data eventually informs the map itself.
From the field
A 12-date run, first pass: artist team and local promoters all spending, zero coordination. Two announce posts per market splitting comments, warm audiences double-served, and one market where artist-side and promoter-side ads were verifiably in the same auctions for the same fans. The next run added one paragraph to every advance: layer split agreed, shared post ID per market, report-sharing clause, buyer-list ask (four of twelve said yes - four more than zero). Same spend total across both parties; the second run's cost-per-ticket dropped in every coordinated market, and the four buyer-list markets seeded the following year's routing pools. The paragraph outperformed the budget.
Common mistakes
- Bidding against your own show (two conversion campaigns, same warm city, same week, two proud dashboards)
- Two announce posts per market splitting the proof that should compound
- Fighting for checkout tracking you structurally can't have instead of architecting around it
- Market budgets set at routing announcement and never rebalanced (DAS 201 M5's featured sin, artist edition)
- Skipping the market-tagged harvest, then routing next year on vibes
Take-home
The Advance Marketing Paragraph (added to Downloads inventory) - the copy-paste coordination clause: layer split, shared post ID, report sharing, buyer-list ask; plus the two-party decision table and the market-tagged harvest spec.
Sources & dates
DAS 100 + DAS 201 + DAS 202 cross-references as cited · coordination 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.
- DAS 201 in its entirety - this module is its shadow, and the artist who understands the promoter's whole playbook advances better shows