DAS 201 · Module 10

Post-Event: The Data Harvest

Facts verified: July 2026Last updated: July 2026Curriculum v2026.1

What you'll be able to do

  • Run the post-show ritual that makes the next show structurally cheaper
  • Measure the full cycle on numbers that survive settlement scrutiny
  • Explain the compounding thesis - the actual moat in events marketing - to anyone in one minute

The short version: The show isn't over at close; it's over when the data's harvested. The ritual: export buyers, sync audiences, log the sellthrough curve, bank the footage - because centralizing first-party data across ticketing, email, SMS, and ads is the machine everything else optimizes on (Hive, May 2026). Measure the cycle on cost-per-ticket and show-level MER, never platform ROAS. And internalize the thesis this track has been building the whole time: a promoter who harvests every show has a structurally cheaper next show, forever. That's not a tactic. That's the moat.

The show ends twice

Once at close, when the lights come up and the room empties. And once the following week, when either somebody runs the harvest ritual - or the night's data value walks out with the crowd and the next show starts cold, again, like the operation has amnesia.

The difference between promoters who compound and promoters who grind is almost entirely which version of "over" they practice. The grind promoter runs 12 great shows a year and starts each one from zero. The compound promoter runs the same 12 shows and starts each one warmer than the last, because every previous show is still working for them. Same talent, same rooms, diverging cost curves.

First rodeo

If this is your first rodeo: nothing in this module is glamorous. It's a 45-minute checklist run within a week of doors. It is also, over a year, worth more than any single creative or targeting decision in this track. Boring compounding beats exciting one-offs - in ads as in everything.

The harvest ritual

1. Export the buyers (Module 2's habit, now with a deadline: within the week, while the platform export is easy to find and the show is fresh). Names, emails, opt-in status, order values, zips.

2. Sync everything: buyer list into Meta as a refreshed custom audience · into the email/SMS platform properly tagged BY SHOW (the tag is what makes "everyone who came to a techno night in the last year" a targetable sentence later) · zips into the Module 5 geo dataset. This centralization across channels is the foundation the whole 2026 stack optimizes on (Hive, May 2026) - the harvest is where it actually happens.

3. Log the curve: final sellthrough timeline into the Module 9 tracking sheet. Three shows in, your venue has a curve; six shows in, Wednesday panic is mathematically obsolete.

4. Bank the footage: the recap shoot (Module 8) gets pulled, backed up, and roughly logged while someone remembers which moment was 1:40am. Next cycle's announce creative now exists before next cycle does.

5. Seed forward: fresh buyer list → refreshed seed for value-based lookalike audiences where you still use them, and - more important under Andromeda - the warm pool that day-one retargeting fires at when the next announce drops (Module 3's on-sale ammunition, restocked).

Scoring the cycle

The cycle's report card, per DAS 100 Module 8's honesty doctrine, is two numbers and a note:

  • Cost-per-ticket: total ad spend ÷ tickets sold. The number that survives settlement, comparable across shows, immune to attribution poetry.
  • Show-level MER: total revenue (tickets + tables + bar where you see it) ÷ total ad spend. The was-it-worth-it number.
  • The note: what the curve did, which creative led, what the next show inherits. Three sentences. The institutional memory most operations never write down - and the exact thing that makes a new team member useful in week one instead of quarter two.

Platform ROAS appears nowhere on the report card. It steered the machine mid-flight (its actual job); it doesn't get to grade the semester.

Go deeper: the recap-as-teaser loop, closed

Module 3 called the aftermovie re-cut the highest-authority announce creative you own. Notice what that means structurally: the LAST show's Module 10 feeds the NEXT show's Module 3 - the lifecycle isn't a line, it's a loop, and the harvest is the splice point. This is also the honest answer to Module 9's catastrophic-Wednesday comp decision: a full room on paper still produces a full room on CAMERA, and that footage sells the next three shows at full price. Sometimes the comps are a content budget.

From the field

Two promoters, same city, same genre lane, both came to us the same season. Promoter A had four years of shows and zero exports - every cycle launched cold, and their "audience" lived entirely inside platforms they didn't control. Promoter B had 14 months of disciplined harvests: tagged lists, synced audiences, a sellthrough curve per venue. B's announce-day retargeting pool was 9x A's despite A's longer history and honestly bigger shows. B's cost-per-ticket ran meaningfully lower all season, and when a platform algorithm change wobbled everyone's reach that spring, B's owned lists didn't notice. Four years of shows versus 14 months of receipts, and the receipts won. They usually do.

Common mistakes

  • Treating close-out as the finish line - the amnesia operation
  • Exports "eventually" (the platform having your buyers is not you having them - Module 2 said it, the deadline makes it real)
  • Untagged list dumps - a pile is not a dataset
  • Grading cycles on platform ROAS at settlement (steering wheel ≠ report card)
  • Skipping the three-sentence note, then re-learning the same lessons per show like a goldfish with a media budget

Take-home

Post-Event Data Harvest Checklist - the 45-minute ritual: export spec, sync destinations with tagging convention, curve log, footage bank, seed-forward steps, and the two-numbers-and-a-note report card template.

Sources & dates

Hive (May 2026) · DAS 100 + DAS 201 cross-references as cited · harvest ritual 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 first-party data centralization argument (May 2026) - the strategic case for everything this checklist operationalizes
  • Then: the DAS 201 final. The track is yours.