How to publish an event on Dizko

Publishing on Dizko costs nothing and takes a few minutes. The event lands on the city map, in the feed, on your organizer page and in the weekly city articles, and you get a page you can send to anyone. What follows is the whole flow, including the parts that reject you and why.

Sign in and create an organizer profile

You need an account to publish. Email, Google, Apple or phone all work.

Events are published by a profile rather than by a person: your venue, your collective, or your promoter brand. That profile is what people follow, what carries your past events, and what your broadcasts go out from. Create it at the setup screen before your first event.

If you run more than one thing, create a profile for each. A monthly ambient night and a warehouse techno series should not share an audience or a page.

Create the event

Go to Create an event. The fields that matter:

• Title. Required, and it is what people scan in a list. Put the thing that distinguishes the night first.
• Date and time. Start must come before end, and the date has to be in the future. Nights that run past midnight are normal; set the real end time rather than rounding.
• Venue. Search for the room. An exact venue is what puts you on the map correctly and connects you to that venue's page.
• Flyer. Required, and it has to be an image URL that actually loads. See below.
• Description. Where the lineup, the genre and the practical details go. The description guide covers how to write it.
• Tickets. Either sell through Dizko or paste the link to wherever you already sell. External ticketing requires a valid http or https link.

Why the flyer is mandatory

Because an event without an image does not get seen. The feed, the map cards and the city pages are visual surfaces, and a listing with no flyer is skipped by almost everyone who scrolls past it. Rather than publish something that will not perform, Dizko rejects it: events without a flyer are not shown in the feed.

The image must be reachable over http or https and must load when checked. A link to a page containing an image will not work; it needs to be the image file itself. Square or portrait artwork crops best across the surfaces it appears on.

Import instead of retyping

If the event already exists on another platform, use Import event URL and paste the link. It pulls the details across so you can check them rather than typing them again, which matters if you are publishing a season of dates.

Check what comes through before publishing, particularly the venue, the end time and the flyer, since those are the fields most often wrong in the source listing.

Fill in the fields that drive discovery

This is the part organizers skip and then wonder why nobody found them. Categories, genres, the exact venue and the artist names are what put your event into browse, search, genre pages, artist pages and recommendations. They are free placement and they only work if the fields are filled.

Two specifics worth care. Spell artist names the way the artists spell them, because that is how their followers find you. And be honest with genre tags: tagging a jazz night as techno gets you in front of the wrong people, who then do not come.

After you publish

Your event has a public page you can send anywhere. From there:

• Set up ticketing at the box office if you are selling through Dizko. Ticketing documentation.
• Create tracked links for each channel so you can tell what sold what. Tracked links.
• Add it to a series if it is a recurring night. Series.
• Message your followers when there is something to say. Broadcasts.

Editing and cancelling

Events can be edited after publishing, and you should edit rather than repost: a reposted event loses whatever indexing and sharing the original had. If a date moves, move the date on the existing event and tell your ticket holders.

If you are selling tickets and need to stop, cancelling ticketing halts sales and invalidates every issued QR immediately, then runs buyer emails and any remaining refunds. It is deliberate and it is not reversible, so use it when the event is genuinely off.