Skip to main content
A template is an event kept only to be copied from. A series groups the instalments of one programme — for example “Quarterly User Conference” holding Q1, Q2, Q3 — and shows each instalment’s figures side by side. Both use one operation: copying an event.

​
Copy an event

On the Business Unit’s Events list, every row has Copy. The dialog asks for:
  • Name — pre-filled as “Name (copy)”.
  • Starts — optional. Scheduled times in the source move with it (below).
  • Time zone — pre-filled from the source.
  • Series — which series to file the new event under, when the unit has any.
  • Save as a template — tick to make the copy a template instead of an event.
Before the button, the dialog lists what is included — “Brings across: 3 ticket types, 2 add-ons, 5 perks, 12 agenda sessions …” — and what is not: registrations, orders, check-ins, exhibitors, codes, and promotion links. There is no checklist of what to include. Configuration is copied; history is not. The copy is created as a Draft, with a new public id and no site URL. Set the new event’s page address once that page exists.

​
What is copied, what is not

Configured content is copied. Records of what happened are not. Three items look like configuration and are not:
  • Redemption codes and promotion links are not copied. They were issued for the source event. A code given to a partner last year must not work on this year’s event.
  • Speakers are not copied. A speaker profile is attached to a registration, and registrations are not copied.
  • Room blocks and exhibitors are not copied; hotels and booths are. A hotel is a reference. A room block is this year’s contract, with nights and rates. Booth types and booths are inventory. An exhibitor is who came.

​
How dates move

Every absolute time in the source — sale windows, agenda slots, survey open and close — is copied as its offset from the source event’s start, then re-anchored to the new start: if last year’s sale opened at T−14 days, this year’s opens at T−14 days. When the copy has no start date, those times are cleared. That is a template: an undated event whose windows wait for a date.

​
Templates

A template is an ordinary event marked as one. It is edited on the same pages as any event, but it never publishes, never takes registrations, and has no public page. Templates live on the Templates tab of the Events list.
1

Save an event as a template

From the Events list choose Copy and tick Save as a template, or open the event’s Settings and choose Save as a template in the Reuse section. Either way the template is a copy. The source event is unchanged.
2

Keep it current

Edit the template like any event: add a ticket type, rebuild the form, change the perks. Events already copied from it do not change.
3

Open an event from it

On the Templates tab choose Open an event (also available from the template’s own Settings). The copy dialog opens with the checkbox off. Give it a name, a start date, and a series. The new event can then be completed and published.
Converting is always a copy. An event saved as a template still exists as an event. A template opened as an event still exists as a template. Nothing changes in place.

​
Series

Series is a page on the Business Unit. A series is a grouping and a board. It holds no settings of its own, so it does not compete with the template.
1

Create the series

Choose Create series and give it a name and an optional description.
2

Point it at a template

On the series page, pick the Template for new instalments. Copying is a snapshot. Editing the template later does not change instalments already opened.
3

Open instalments

Open next instalment on the series page opens the copy dialog on the series’ template, already filed under the series. An existing event is filed from Settings → Reuse → Series, saved as soon as chosen.
The series page shows a chart of confirmed registrations by instalment and a table of every instalment: name, start, status, Confirmed (confirmed / total registrations), Revenue, and Checked in. Every figure uses the same query as the event’s report page, so a number here and the same number on the event match. Revenue is shown per instalment and never summed — two instalments need not share a currency.

​
Rules to know

  • Copying is a snapshot, not a live link. Changing a template afterwards changes nothing copied from it.
  • A copy is always a draft with a new public id and no site URL.
  • A template cannot be published. Publishing is refused. Open an event from it instead.
  • An event belongs to at most one series. A template belongs to none — it has no dates to run on.
  • A series holds no configuration. Ticket types, forms, and perks belong to the template, not the series.
  • Series are archived, never deleted. An archived series takes no new instalments. Events already in it are unaffected.
  • Copying stays inside one Business Unit.
  • A copy is all or nothing. If any part fails, no event is created.

Create an event

Creating one from scratch, and what the start date controls.

Event settings

The Reuse section: series picker and Save as a template.

Ticket types

Definitions a copy carries across.

Offers & redemptions

Codes are issued per event, so they are not copied.