What you'll be able to do
- Run the Advance Marketing Paragraph across N promoters without N headaches
- Build the promoter matrix that tracks who runs what layer, per market
- Handle the uncoordinated market without burning the relationship or the budget
The short version: DAS 202 Module 8 solved the two-party problem for one show with one paragraph. A tour is that problem × N, with N different promoters, N ticketing platforms, and N levels of sophistication - so the solution industrializes: the paragraph goes out with every advance as standing tour policy, the responses land in a promoter matrix (layer split, shared post ID, report cadence, buyer-list status, tracking tier per market), and the tour team runs its network layer uniformly while local layers vary by what each market agreed to. The market that won't coordinate gets the clean fallback: run your layer, harvest what's yours, note it in the matrix, move on.
The paragraph, industrialized
One show's coordination is a conversation; a tour's is a SYSTEM. The pieces:
- The paragraph ships with every advance, day one. Same text (DAS 202 M8's take-home), tour-standard, sent by whoever owns the advance - which means the tour manager and the marketing operator need one alignment call before the routing announces, not fourteen improvised threads after.
- The promoter matrix is the tour's coordination ledger. One row per market: promoter · layer split agreed? · shared post ID? · report cadence · buyer-list ask (yes/no/pending) · ticketing platform + tracking tier (the Matrix doc, applied per market) · notes. Fifteen markets of verbal agreements is amnesia with extra steps; the matrix is the memory.
- Your layer stays uniform; theirs varies. The tour team's network layer - artist canon, nodes, national warm, the alert list (Module 5) - runs identically everywhere. Local layers flex to each market's agreement. Uniform core, flexible edge: the only architecture that survives N.
The tracking reality across N platforms
The tour will cross Tier 1, Tier 2, and walled platforms in the same month (DAS 201 M2's tiers, now a patchwork). The doctrine: your side optimizes on what YOUR pages see, everywhere - the tour landing page and per-market smart links are the one consistent measurement surface across all N markets, instrumented once (pixel + CAPI, per DAS 202 M4's stack). Platform-side purchase data arrives unevenly per the matrix; your click-through layer is the constant that makes markets comparable. Without it, comparing Denver's Tier 1 numbers to Boston's walled numbers is comparing a thermometer to a mood.
›Go deeper: the uncoordinated market playbook
Some promoter won't answer the paragraph, or answers "we got it" and means nothing. The clean fallback, in order: (1) run your network layer fully - it needs nobody's permission; (2) skip the shared post ID (their loss, noted), run your own announce ID and stack YOUR markets' proof on it; (3) watch for auction collision signals (soft warm performance in that market only) and if found, tilt your layer earlier in the window - occupy announce/sustain while they burn the final week, minimizing same-auction overlap you can't negotiate away; (4) harvest what's yours regardless - engagers and viewers are permissionless; (5) matrix note for next routing: this market's coordination status is DATA about this market. No fights, no cc'd managers, no burned bridges - the tour comes back through here next year, and the promoter who ignored the paragraph in March sometimes asks about it in November after seeing the coordinated markets' numbers.
From the field
A 16-market run sent the paragraph as policy: eleven markets agreed to the full split, three partially, two went silent. The matrix tracked all sixteen. The eleven coordinated markets shared post IDs and weekly reports; the tour's warm layer ran uniform everywhere; the two silent markets got the fallback (early-window tilt, own IDs, full harvest). Settlement season told the story: coordinated markets averaged materially lower cost-per-ticket than the silent two - and the matrix's final column became the next routing's first filter. One of the silent promoters, shown nothing but invited to coordinate again the following year, took the paragraph the second time. The system didn't argue; it just kept receipts.
Common mistakes
- Improvising coordination per-market instead of shipping the paragraph as policy
- No matrix - sixteen verbal agreements living in one person's memory and three text threads
- Chasing checkout tracking uniformity across platforms that will never grant it (your click-through layer is the constant; build it)
- Fighting the uncoordinated market instead of running the fallback
- Treating coordination status as personal instead of as routing data
Take-home
The Promoter Matrix Template - the full column set, the paragraph reprint, the fallback playbook card, and the alignment-call agenda for the tour manager conversation.
Sources & dates
DAS 201 M2 tiers + DAS 202 M8 paragraph as cited · matrix system 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.
- The Ticketing Matrix living doc - the per-platform tier reference the matrix's tracking column points at