DIZKO
Dizko · InfoHub · How Dizko works

How Dizko works

Broadcasts, followers, and knowing what your crowd listens to

Dizko · August 14, 2026 · 4 min read

The most valuable channel any organizer has is the one nobody can switch off: a direct line to people who already decided they like what you do. On Dizko that is your followers, and the tools around them sit at broadcasts and audience.

Broadcasts

A broadcast goes to everyone following your events. Write a title, write the body, and optionally add a button with your own label so the message lands somewhere specific rather than just being read.

The screen shows how many people you are reaching and how many of them have notifications switched on, which is the number that actually matters. A list of 900 followers with 300 notification-enabled is a 300-person channel, and knowing that stops you over-estimating your own reach.

What to send, and what not to

The rule is the same as email: every send should be worth the interruption, because the cost of a bad one is people turning notifications off permanently.

Two to four sends per event cycle is a healthy rhythm for most nights. The announcement, one piece of news in the middle, one in the final week, and the recap.

The audience view

This is the part organizers underuse. It reads your actual crowd rather than a generic demographic, and it answers four practical questions.

What your crowd listens to

The music taste of the people who come to your events. Useful for programming, and extremely useful in a sponsorship pitch, where "our audience listens to these fifteen artists" is far more persuasive than an age range. The sponsorship guide shows how to use it in a pitch.

Artists your crowd loves that your city has not booked

The most directly actionable thing on the screen. It is a booking shortlist derived from demand that already exists in your room, against supply that is not there yet. If an artist shows up here repeatedly, that is a night waiting to be programmed.

Who else your crowd goes to see

Which other events and promoters your people attend. Read it two ways: as competition for a date, and as a list of the promoters worth doing something with rather than against.

Testing a lineup before you announce

You can check a proposed lineup against your own audience before it is public. This is the cheapest booking decision available: it costs nothing to find out that the guest you were about to pay for is unknown to the people who actually come.

Treat it as one input rather than a verdict. Sometimes the right booking is the one your crowd does not know yet, and taste data cannot tell you that. It can tell you when you are about to spend a fee on a name that will not move a ticket.

Growing the follower list

Followers accumulate from the surfaces you already run, so make sure they are switched on:

The point of all this

An organizer with a thousand followers and a broadcast channel does not have to buy attention for every event. That is the difference between a promoter who is always marketing and one who announces a date and sells a room. It compounds, it survives platform changes, and it is the reason capturing attendees is worth more than the profit on most early events.

Questions organizers ask

How often should I broadcast?

Two to four times per event cycle. The announcement, one piece of news in the quiet middle, one in the final week, and a recap. More than that and people mute you.

Do all my followers see a broadcast?

It reaches everyone following your events, and the screen shows how many have notifications enabled. Treat the notification-enabled number as your real reach.

Is the audience data about individuals?

It is aggregate taste and attendance signal about your crowd, meant for programming and pitching. Use it to decide what to book, not to profile individuals.