Skip to main content
orriven does not host the event website. The event is presented on your own site, and orriven hosts only the pages that must be the platform’s: the checkout, the order page, and the entry pass each attendee carries. Each lives at an address unique to one order or one person. There is nothing to browse and nothing to log in to.

​
What is hosted, and what is not

Hosted pages use orriven’s neutral look, with the event name and the Business Unit’s profile name and logo on top. There are no themes to edit.

​
The buyer’s journey

1

Choose on your site

The buyer picks a ticket (and, optionally, a redemption code) on your event page. Your site opens a checkout session for that selection through the Storefront API or the Developer API and sends the buyer to the address it receives. The buyer’s email, name, and form answers can be prefilled; the checkout page asks for anything left out.
2

Complete the checkout page

The page shows the selection and its prices, collects what is missing — email, name, registration form answers, add-ons — and places the order. The order holds its places for 15 minutes while the buyer reviews and confirms. A free order settles immediately; a paid order continues to the payment page.
3

Land on the order page

After payment, the buyer returns to the order page, which shows the outcome and a Return to button back to your site — to the return address your site named when it opened the session, or otherwise to the event’s page address. Your site receives the order number and status on that return, so it can show its own thank-you page.
A buyer who is already registered and checks out again is acknowledged as registered, never sold a second seat. This is the same rule as everywhere on the platform.

​
The ticket email

The moment a registration becomes confirmed — bought on the checkout page, approved by an organizer, or added from the console — the platform emails the person their ticket: the link to their entry pass and, when there is one, the link to their order. No setup is required. It is not an automation, and it does not appear in the send history. Your own emails can carry the same links: the email template variables Entry pass link and Order page link are filled in per recipient.

​
The entry pass

The entry pass is the page a person opens from their ticket email. It shows:
  • their name, ticket type, and registration status;
  • the check-in QR code — shown only on a confirmed seat of an event that runs on-site check-in, because otherwise no door would scan it;
  • Add to Apple Wallet and Add to Google Wallet, when the platform offers wallet passes;
  • their certificate of attendance, once they have checked in at the event door (see Agenda for session credits);
  • any open surveys for the event, with what they already answered;
  • the lead desk, when the person staffs an exhibiting company.
The link works for as long as the event does. A cancelled seat still opens the page. It states that the registration is cancelled rather than behaving as if the link never existed.

​
The email check

Opening an order page, an entry pass, or the lead desk asks the person to enter the email the link was sent to. The link and the email must match. A wrong email reads exactly like a dead link, and the page never says which of the two was wrong. The browser remembers the email afterwards, so the check happens once per device.
This is what makes a link safe to forward by mistake: whoever holds it still needs the inbox it was addressed to. The checkout page is the one exception. The buyer types their email there anyway, and a prefilled address is shown masked.

​
The lead desk

Exhibitor staff open the lead desk from their own entry pass. Entering a visitor’s badge code records that visitor as a lead for the company. Leads are team-shared and the exhibitor’s asset: they never appear in the console. See Exhibition overview. On the attendee detail page, the Entry pass link card shows the person’s link with three actions:
  • Copy link — to paste into a support reply or your own system.
  • Regenerate link — every earlier address stops working immediately, including the one in emails already sent. Use it when a link has leaked, and resend the ticket afterwards.
  • Resend ticket email — sends the platform’s ticket email again.
Order detail pages show the Hosted order page address the same way.

​
Your event’s page address

The Public page section of each event records the address of the event on your own site. Three things depend on it:
  • Promotion short links redirect there. A short link for an event with no page address answers “not found”.
  • Return after checkout goes there when your site did not name a return address for the session.
  • Offer share links are that address plus ?code=….

​
Rules to know

  • Every hosted address is unique to one order or one person. There is no home page and nothing to enumerate. An unknown address, an expired one, and a regenerated one all answer “not found”.
  • Link and email. Order, pass, and lead pages open only for the email they were sent to. The checkout page does not ask.
  • The ticket email is automatic on every confirmed registration, however it was created.
  • A checkout session holds nothing. The 15-minute hold starts when the buyer places the order on the checkout page. A session lasts 24 hours.
  • The QR code appears only on confirmed seats of on-site events. Wallet passes follow the same rule.
  • Regenerating a link invalidates the old one, including emails already sent.

The event page

Publishing, and the page address your site presents the event at.

Storefront API

Open checkout sessions from the browser with a publishable key.

Checkout from a backend

Server-side sessions, and building a “my tickets” area from the Developer API.

Attendees

Where the pass link, regenerate, and resend live.