Skip to main content
The Public page section of the console controls the public side of an event: visibility, where on your own site it is presented, and which languages its content is offered in. The event page itself is yours to build. orriven provides the hosted pages — checkout, the order page, and the entry pass — behind it.

​
Publish and unpublish

The section shows the event’s visibility and the switch:
  • Published — the event exists to the outside: your site can list it, checkout sessions can be opened for it, and its hosted pages respond.
  • Draft — not visible outside the Business Unit. Every public address returns “not found” until the event is published, and publishing requires a start time.
“Not found”, not “access denied”: a draft event, an expired hosted address, and a nonexistent address all look identical from outside. A draft cannot be confirmed by trying links.

​
Your event page

The Your event page card holds the page address — the page on your own site where this event is presented, as a full https:// address. Set it once, and three things follow from it:
  • promotion short links redirect there;
  • the hosted checkout sends buyers back there when your site named no other return address;
  • offer share links are that address plus ?code=….
Open page opens it once it is set. The event’s public URL id — the short, unguessable id your site and the APIs address the event by — is shown alongside. It never changes, so renaming the event never breaks a link.

​
Hosted pages

The Hosted pages card summarizes what orriven serves on the event’s behalf: checkout, the order page, and each attendee’s entry pass, reached through checkout sessions your site creates and through the ticket email the platform sends. They show the event name and the Business Unit’s name and logo. There is nothing to design.

Hosted pages

The buyer’s journey, the entry pass, the email check, and managing a person’s pass link.

​
Languages

The Languages card lists the languages the event’s content is offered in and translates what the public sees — ticket names and descriptions, add-ons, bundles, sessions, speakers, and form questions. Translations only replace text: they can never reveal a hidden ticket, change a sold-out state, or alter what a page offers. A string with no translation falls back to the default language, so a partly translated event still reads whole.

​
Rules to know

  • Public visitors only ever see published events; drafts are invisible.
  • The page address is https:// only, and nothing gates on it. An event without one is still published; it simply has no short links or return address.
  • The public URL id is stable across renames.
  • Visibility is the event’s status, always — never a setting on your site or on a hosted page.