Zooza logo

The activity calendar your website is missing: live, filterable, yours.

People choose by their own week before they choose by your programme. Which evenings are free, which venue is on the way home, whether Saturday morning is realistic. The Zooza calendar widget puts every class you run on a page of your own site, reads straight from your live data, and lets a visitor narrow it down to the venue, the course and the instructor that fit. One click goes to the course page or straight into registration — and they never leave your domain.

What the calendar widget does

It is one of seven widgets you can publish on your own website — booking form, calendar, client profile, sales form, map, video and contact form — and it is usually the one people land on first. Each renders inside your page’s own markup rather than in a frame, so your site stays your site.

Every class, in real time

The calendar reads your live Zooza data. Availability shows as a count like 10/10, as wording such as “Last spot available”, or not at all, whichever suits how you sell. Change a class in Zooza and the website is already right; there is no second timetable to remember.

Two views, one widget

The default is an abstract Monday-to-Saturday week, which is how most people hold a regular class in their head. Turn on the classic calendar view and the same data lands in a normal dated calendar — the better choice for camps, holiday weeks and one-off workshops.

Filters the visitor controls

Switch on filtering by location, course, course type and instructor, together or separately, and hide the whole bar behind a button when the page is tight. Someone whose only free evening is Tuesday finds their class without reading your entire offer.

Pre-filtered copies anywhere

Embed the same widget as many times as you like. Pin one copy to a venue with place_id, one to a programme with course_id, one to a single term with bps. A landing page per location then shows that location’s classes and nothing else.

Styled like the rest of your site

The widget renders in your page, so your own CSS reaches it: prefix your selectors with .zooza and restyle anything. Download the default stylesheet as a starting point, or switch it off entirely in Publish and build the tiles from scratch. Labels can be overwritten too.

Click-through you decide

A tile can open the course page, open the registration form, or do both with a button for one action and the tile for the other. Instructor, session number, duration and course description are each a toggle, so the tile says what your audience actually asks.

Getting it on your site

The embed is two lines. Most of the work is deciding what the page should show.

  1. Step 1

    Publish the widget

    In Team & Settings → Publish, create a calendar widget and set the address of the page it will live on. Then pick how you want it: the WordPress plugin, the Wix element, an npm package for React, Next.js, Vue, Nuxt, Svelte or Web Components, or the raw embed for anything else.

  2. Step 2

    Paste two lines

    A placeholder div where the calendar should appear, and a loader script that can sit in the body or in the head if you want it to start earlier. On WordPress it is the shortcode [zooza type="calendar"] instead. Nothing to install, nothing to keep updated.

  3. Step 3

    Decide what it shows

    Availability wording, which filters appear, instructor and duration, rooms merged into one location, dates for future terms, cancelled sessions, the classic calendar view. All of it lives in the widget settings, so changing your mind later does not need your developer.

  4. Step 4

    Make it look like you

    Override the defaults under .zooza, or turn them off and style it yourself. For full control of a tile there is the event_tile_render callback: it hands you the tile’s data and the default markup, and renders whatever you return.

Who puts a calendar on their own website

The widget does not know how old the attendee is. It works the same whether the week belongs to a four-year-old or to you.

  • Children’s activity providers, where a parent picks the venue first and the day second.
  • Pilates, yoga and adult fitness studios, where the whole decision is which evenings are genuinely possible.
  • Swim schools with several pools and a different timetable in each.
  • Language schools publishing a term’s groups by level, day and tutor.
  • Franchise networks where every location’s page shows only that location’s classes.
  • Camps and holiday weeks that need real dates rather than an abstract week.
  • Studios running sessions that are not in Zooza at all, imported into the same calendar so the page is complete.

People decide by the calendar. Put yours where they are looking.

Create a calendar widget, paste two lines into your site, and let visitors filter to the class that fits their week. On your own domain, in your own styling, part of every plan.

Try for Free No credit card needed.
Book a live demo We’ll embed one on a test page with you.

FAQ — what people ask before embedding the calendar

  • Does it work on WordPress, Wix or a custom-built site?
    Yes. There is a WordPress plugin with a [zooza type="calendar"] shortcode, a Wix element, npm packages for React and Next.js, Vue and Nuxt, Svelte and SvelteKit, Web Components and vanilla JS, and a raw embed for everything else. Each route is covered in deploying Zooza on your website.
  • Is this only for children’s activities?
    No. The calendar shows the classes you run, whoever attends them. A pilates studio, an evening language course and a toddler swim school publish the same way; what differs is which filters you expose and how the tiles are worded. Zooza is built around course-based activities rather than around an age.
  • Can I style it to match my site?
    Yes. It renders in your page’s own markup, so your CSS applies — prefix selectors with .zooza, which sits on Zooza’s main div. The default stylesheet can be downloaded for reference or switched off completely under Publish → Widget → Calendar → Use CSS, in which case you supply the styling, including utility classes such as .hidden. What is adjustable from the admin and what belongs to your developer is laid out in customizing widgets.
  • Can one page show only one venue, or only one term?
    Yes. Pass place_id for a location, course_id or data-zooza-filter-courses for programmes, and bps to limit the calendar to a single billing period. They work as embed attributes or as URL parameters, and several pre-filtered copies can live across your site as long as at least one sits on the address you configured.
  • Do visitors leave my website to register?
    No. A tile opens either the course page or your registration form, both on your own domain when you have embedded the booking widget there. The booking form then keeps the parent on that page: choosing attendees, signing in with a one-time code and paying all happen in place. There is no app to download.
  • What happens with holidays and cancelled sessions?
    The default view is deliberately undated, which is why a skipped week never makes it look wrong. If you want dates, the custom selection shows session dates in current classes and dates for future classes, and can include cancelled sessions without a click-through and classes that are already full. You choose how much of the real week a visitor sees.
  • Can I show sessions that are not in Zooza?
    Yes. A JavaScript import adds your own locations and sessions — zooza_places and zooza_events — to the same calendar alongside the live ones, so the page can be complete even while part of your operation still lives somewhere else.
  • Will Google index the classes in the calendar?
    Treat the calendar as something visitors use, not as the page’s indexable content: it is rendered in the browser from live data, so the page still needs real text of its own. Making class data readable by search engines and AI assistants is a separate job, and it lives in AI visibility.

For developers

The calendar widget reference carries every initialisation option and data attribute, the regional API URLs, the CSS entry points and the event_tile_render callback — plus the import format for sessions that are not in Zooza.