Use Veezi Custom Templates and Fields

Jeero can start with a simple Veezi import: title, description, date, location, image, and ticket link. After that first sync works, custom templates and fields help make imported events match the WordPress theme more closely.

Use this when you want to:

Change imported event titles, descriptions, excerpts, or calendar-specific fields.
Save ticketing data into WordPress fields your theme already uses.
Add subtitles, practical info, venue details, prices, or other structured data to event pages.
Keep the first import simple while still giving the theme richer data later.

Start After the First Sync

Do not start here before events are importing correctly.

First confirm that Jeero can connect to the ticketing platform, create events in WordPress, and send visitors to the right ticket page. Once that path works, custom templates and fields can improve the event page without changing the ticketing connection itself.

What Jeero Makes Available

Jeero passes common event values into Twig templates, including:

title
description
start
end
venue
categories
tickets_url
status
prices

Veezi also provides platform-specific values. Jeero can use the fields below in custom templates and custom fields.

Those extra values are available directly by their field name in Twig. If Jeero receives a field called PriceCardName, use:

{{ PriceCardName }}

Do not use:

{{ custom.PriceCardName }}

Custom Templates vs Custom Fields

Jeero uses custom templates in two related ways.

Post field templates change the WordPress event fields Jeero imports. These include title, content, and excerpt, plus calendar-specific fields like a venue or location field. Use these when you want to change the main imported event content.

Custom fields write a rendered template into a WordPress custom field. Use these when your theme, page builder, custom block, or calendar plugin expects a specific post meta field.

A custom field has two parts:

Name: the WordPress custom field key Jeero should write.
Template: the Twig template Jeero should render for that field.

Example: Save a Subtitle as a WordPress Field

If your ticketing platform provides a field such as PriceCardName and your theme expects a WordPress field called event_pricecardname, add a custom field like this:

Name: event_pricecardname
Template: {{ PriceCardName }}

On import, Jeero renders the template and saves the result to the WordPress event as the event_pricecardname custom field.

You can use the same pattern for any Veezi field from the table below:

Name: event_extra_info
Template: {{ OpeningDate }}

Or combine values:

Name: event_teaser
Template: {% if PriceCardName %}{{ PriceCardName }}{% else %}{{ title }}{% endif %}

Only use field names that your WordPress theme or plugin actually reads. Creating a custom field does not automatically make it visible on the event page.

Available Veezi Fields

These field names come from the current Veezi adapter code:

Field	What it means	Twig example
`Distributor`	The name of the distributor	`{{ Distributor }}`
`OpeningDate`	When did this film first show	`{{ OpeningDate }}`
`Rating`	Censor rating	`{{ Rating }}`
`Content`	Content advisory for the film	`{{ Content }}`
`Duration`	The duration of the film in minutes	`{{ Duration }}`
`Format`	The format that this film will play in	`{{ Format }}`
`IsRestricted`	Is this film be restricted to adults only	`{{ IsRestricted }}`
`AudioLanguage`	The original audio language of the film	`{{ AudioLanguage }}`
`People`	The people involved with the film. Possible values for Role are: Actor, Director, Producer.	`{{ People }}`
`BackdropImageUrl`	A link to a backdrop image of the film	`{{ BackdropImageUrl }}`
`FilmTrailerUrl`	A link to a trailer video of the film	`{{ FilmTrailerUrl }}`
`Seating`	How seats are allocated for this session	`{{ Seating }}`
`AreComplimentariesAllowed`	Are complimentary tickets allows to be used for this session	`{{ AreComplimentariesAllowed }}`
`ShowType`	Is this session Public or Private	`{{ ShowType }}`
`SalesCutOffTime`	The time when the sales close for this session	`{{ SalesCutOffTime }}`
`TicketsSoldOut`	Are all tickets sold out for this session	`{{ TicketsSoldOut }}`
`FewTicketsLeft`	Is the current available tickets percentage lower than the low tickets threshold set in the database	`{{ FewTicketsLeft }}`
`FeatureStartTime`	The time the feature is scheduled to start	`{{ FeatureStartTime }}`
`PriceCardName`	The price card is a set of ticket prices that can be applied to a session	`{{ PriceCardName }}`
`TotalSeats`	Total number of seats for this screen	`{{ TotalSeats }}`
`HouseSeats`	The number of seats that are reserved by the house for exceptional circumstances	`{{ HouseSeats }}`
`WheelChairSeats`	The number of seats that are reserved for customers with wheel chairs	`{{ WheelChairSeats }}`

Good First Improvements

Start with one visible improvement:

Add a subtitle below the event title.
Save doors-open time into a field your theme already displays.
Add practical information to a consistent event-page section.
Include venue city in a location field.
Add price or status information to the event content.

Avoid changing every field at once. It is easier to verify the import when each change has a clear purpose.

Check the Result

After adding a custom template or field, import or update one event and check:

The event still imports successfully.
The field value is present in WordPress.
The public event page shows the value where expected.
The template still behaves well when the ticketing field is empty.

If the field is saved in WordPress but not visible on the public page, the next step is usually a theme or template change, not another import setting.

When to Ask for Help

Send me the WordPress event page, the ticketing link, the field you want to show, and the place where it should appear. If you know the custom field key your theme expects, include that too.

I can help decide whether this needs a post field template, a custom field, category mapping, or a small theme change.