Skip to content
itsorted.online
Industry guide

Event and MICE Companies: Registration Sites, Ticketing and Data

An event or MICE company's website does more than market: it registers attendees, sells tickets, collects data that sponsors want, and feeds badge printing on the day. Each of those steps has a Singapore rule or risk attached. This guide covers how to structure a multi-event site, ticket tiers and GST-inclusive pricing, sharing attendee data with sponsors and exhibitors under the PDPA, photography consent, badge and check-in exports, refund terms, and protecting attendees from fake ticket sellers. It also points to the Singapore Tourism Board's business events support.

By IT Sorted teamReviewed 7 min readHow we write guides
in

Key takeaways

  • GST-registered organisers must show GST-inclusive ticket prices to the public, says IRAS.
  • Passing attendee details to sponsors or exhibitors needs the attendee's consent for that purpose.
  • PDPC suggests stating photo-taking in the invitation, at the entrance or on the registration form.
  • Publish one official ticket URL and refund terms before sales open to cut scams and disputes.
  • STB's Singapore Exhibition & Convention Bureau runs programmes such as SMAP and INSPIRE for MICE events.
In this guide · 9 sections
  1. 01Structuring a website for many events
  2. 02Ticket tiers, GST and payments
  3. 03Attendee data, sponsors and exhibitors under the PDPA
  4. 04Photos and videos at events
  5. 05Badges, check-in and exports
  6. 06Refund terms and ticket scams
  7. 07STB support for business events
  8. 08Do it yourself or get help?
  9. 09Frequently asked questions

Short answer

Give each event its own page under your main domain, sell all tiers through one official checkout with GST-inclusive prices if GST-registered, get separate consent before sharing attendee details with sponsors, publish refund terms, and name the only official ticket link.

Structuring a website for many events

Event companies run a series of conferences, exhibitions or incentive trips, each with its own agenda, speakers and sponsors. The usual choices are:

Event pages on your main site

Simplest
  • One domain, one login, one design
  • Past events stay as an archive that builds search traffic
  • Each event gets its own URL, such as /events/summit-2027

Best for: Companies running several events a year under their own brand.

Separate microsite per event

  • Event brand and domain of its own
  • More domains, hosting and logins to manage
  • Needs a plan for what happens after the event

Best for: Large flagship events with their own identity and sponsors.

Whichever you choose, keep registration and payments in one system so reports, refunds and data handling are consistent. Use subdomains of your main domain (summit.yourcompany.com) rather than many unrelated domains, which makes it easier for attendees to recognise the real site.

Ticket tiers, GST and payments

Common tiers are early bird, standard, group, student or member rates, and VIP or workshop add-ons. Set each with its own price, quantity cap, sale window and refund rule.

  • Payment methods: cards for overseas delegates, PayNow for local ones, and invoices with bank transfer for corporate group bookings.
  • Fees: platform and payment fees can eat into low-priced tickets. Our Stripe fees guide works through card, PayNow and international card costs.
  • Booking fees: if you add a booking or service fee that every buyer must pay, include it in the headline price rather than revealing it at checkout.
  • Invoices: corporate buyers need a tax invoice with your GST registration number and the delegate names.

Attendee data, sponsors and exhibitors under the PDPA

Sponsors and exhibitors often ask for the attendee list. Under the PDPA, an organisation generally needs a person's consent to collect, use or disclose their personal data for a purpose, and must tell them that purpose. Registering for a conference is not consent to be contacted by every sponsor.

Data useWhat you needHow to collect it
Running the event (badges, updates, venue access)Notify the purpose at registrationPrivacy notice linked on the registration form
Sharing contact details with sponsorsSpecific consent for that disclosureUnticked box naming the sponsors or sponsor categories
Exhibitor badge scanning (lead retrieval)Attendee aware that a scan shares their detailsExplain on the badge or at registration; scanning is the attendee's choice
Your own marketing for future eventsConsent for marketingSeparate unticked opt-in; DNC rules for SMS or WhatsApp
Dietary or accessibility needsCollect only what the venue needsOptional field; delete after the event

Do not ask for NRIC numbers to register unless the venue's security genuinely requires it, and delete delegate data you no longer need after the event. Our guide to privacy policies and cookie consent under the PDPA covers the notice on your site. This is general guidance, not legal advice.

Photos and videos at events

PDPC's Advisory Guidelines on the PDPA for Selected Topics discuss photography at private events. To make attendees aware of the purpose, PDPC suggests stating in the invitation that photographs will be taken and how they will be used, putting an obvious notice at the reception or entrance, or including it on the registration or confirmation form.

If an attendee later withdraws consent for publication, PDPC's guidelines say you must stop future publication of that photo, though you do not have to recall material already distributed. Keep a simple process for these requests, and brief your photographer on attendees who ask not to be photographed.

Badges, check-in and exports

Most registration platforms export attendee lists for badge printing and check-in. Plan the export before the event, not the night before.

  1. Decide the badge fields

    Usually name, company, job title and a QR code. Leave email and phone off the badge itself.

  2. Set a QR code per ticket

    A unique QR code lets staff check people in quickly and stops a screenshot being reused.

  3. Export only what the printer needs

    Send the badge vendor the badge fields, not the full registration data, and ask them to delete it after the event.

  4. Test check-in on site

    Test the scanners and the venue Wi-Fi or mobile data the day before, with an offline list as backup.

  5. Close the loop after the event

    Send the thank-you and survey, then archive or delete data according to your retention rule.

Follow-up emails, survey reminders and sponsor lead handover can be automated. Our guide to automating lead follow-up from enquiry forms shows how.

Refund terms and ticket scams

Before ticket sales open

Ticket scams on social media and resale platforms are a recurring problem in Singapore. The government's ScamShield site lets people check and report suspected scams. Our guide on stopping fake ticket sellers using your event covers the official ticket page, verified accounts and email authentication in detail.

STB support for business events

The Singapore Exhibition & Convention Bureau (SECB), part of the Singapore Tourism Board, is the lead government agency for business events. STB's MICE page lists programmes such as In Singapore Incentives & Rewards (INSPIRE) and the Singapore MICE Advantage Programme (SMAP), and STB's MICE experience programmes page also mentions SHINE, a hotel partnership with negotiated room rates for meeting organisers. These complement STB's Business Events in Singapore incentive scheme. Contact SECB through STB to check eligibility for a specific event.

Do it yourself or get help?

Many organisers run registration on an off-the-shelf ticketing platform and link it from a simple website. That works well if the platform handles GST-inclusive pricing, separate consent boxes and clean exports.

If you want it set up properly on your own accounts, our Website Pro (S$2,990) builds a site of up to 12 pages with registration forms and full on-page SEO. Online Payment Setup (S$290) adds cards and PayNow checkout, and our PDPA Compliance Pack (S$690) prepares the privacy policy, data inventory and breach response plan your attendee data needs.

Frequently asked questions

Yes, if the organiser is GST-registered. IRAS says GST-registered businesses must display and quote GST-inclusive prices to the public, including on websites, and that statements such as prices are subject to GST are not acceptable on their own. At 9% GST, a S$100 ticket should be shown as S$109.

Only with the attendees' consent for that purpose. Under the PDPA, organisations generally need consent to disclose personal data and must tell people why it is collected. Use a separate, unticked consent box at registration that names the sponsors or sponsor categories, and share only the details people agreed to.

PDPC's guidelines suggest making attendees aware that photos will be taken and how they will be used, for example in the invitation, with a clear notice at the entrance or reception, or on the registration form. If someone withdraws consent for publication, stop publishing their photo in future.

Not necessarily. Event pages on your main site are simpler to manage and build search traffic over time. A separate microsite suits large flagship events with their own brand. Either way, keep registration and payments in one system so refunds, reports and data handling stay consistent.

The Singapore Exhibition & Convention Bureau, part of the Singapore Tourism Board, champions business events and runs programmes including INSPIRE and the Singapore MICE Advantage Programme, plus a hotel partnership called SHINE. These complement the Business Events in Singapore incentive scheme. Contact SECB to check what applies to your event.

Rather have it done for you?

Fixed price, set up in your own accounts.

Order online, get a written scope, and keep full ownership of everything we set up. Questions first? Ask us in writing.