Custom event pages

You could already share filters and selections from the event page. Now you can make custom event pages and control which events the page contains before applying the filters.

Create a custom event page with only your event series? You can link to a page with only your event in the list.

Want to make the event page load faster, skipping events you never want to ride anyway? Right now more than 5.000 events are loaded into the public event calendar. You can link to a custom event page, where you limit the number of events. That custom event page will load much faster.


A single page – which loads quite fast – with only the Zwift Run Festival events: run festival

Do not load any Zwift Run Festival, Tour de Zwift, Festive 500, or TDZ Run events: de zwift;zwift run festival;festive 500;tdz run

Below are the parameters you can use.

Prefiltering (limit loaded events)

The parameter include can be used to include only events with event name containing one of the texts in the semicolon separated value list:



include=Tiny Race

The parameter exclude can be used to prune events (those with names containing any of the values) from the list:



exclude=za tri 2022;zrl

The parameter values are case-insensitive.

include and exclude can be used together. include is applied first to get just the events matching the include list, then exclude is applied to remove those events matching the exclude list.

Apply no event filters

To make sure that no user set filters are applied you can use the filter parameter in your URL.


Opens the page without any active filters.

Limit days per page


You can control the number of days per page with the days parameter. I recommend using it together with the nosave parameter if you publish links to the event page where you select number of days to be shown.

Do not ruin user saved settings and filters


Unless you use the nosave paramter, values for days, filter etc. you put in the URL will overwrite user set preferences for number of days per page, the saved filters, and other settings stored in local storage of the browser. Using nosave in your URL is polite and makes sure that user preferences will still be intact when they navigate to the ‘normal’ event page.

If you find any problems with these parameters you can use the comment section below to report them.

Leave a Reply

Your email address will not be published. Required fields are marked *