Turnout Ads — the honest roadmap.
Advertising on Turnout is not built. You cannot create, launch or pay for a campaign here, and nothing on this page pretends otherwise: no disabled buttons dressed up as features, no fake dashboard, no invented reach numbers.
The planned Ads Manager, module by module
This is a specification, not a screenshot: six modules, the fields each one is expected to own, and the data each one is allowed to read.
Campaign
Objective, budget, flight dates and the organizer whose inventory it buys.
Audience
Segments derived from real attendance history — category affinity, city, repeat behaviour. Never from a list that was sold to us.
Inventory
Placements inside the platform: the Discover catalogue, the organizer's event pages, and the notifications an organizer already controls.
Delivery
Reach, frequency and pacing, with a hard stop when the budget or the flight ends.
Reporting
Attribution back to tickets: spend, impressions, registrations and verified attendance attributed to the campaign.
Agent control
One scope exists today: campaigns:write. It drafts a campaign and queues reminder rows. Nothing is sent by Turnout.
- ✕ No launch button — there is no delivery pipeline to launch into.
- ✕ No budget field on a live campaign — nothing records spend.
- ✕ No impression or reach counter — that data does not exist yet.
- ✕ No cost-per-attendee figure — the analytics page prints it as absent for the same reason.
The design intent is that an advertiser buys attention inside Turnout, and the measurement is the same verified attendance the organizer already trusts — rather than a click that may never have been a person.