Skip to contentMasha Sidorova

Empire State Building

Empire State Building tickets that people understand and buy on the building's own site

The Empire State Building welcomes 4 million visitors a year. Most come once and decide fast, often at the last minute. Many couldn't tell the tickets apart, so they bought from resellers. We made the tickets easy to compare, showed what each one includes, and gave people a reason to book with the Empire State Building directly.

Hero, Tower Lights on the live site: the upcoming light colors, Saturday to Friday, one tap per day

Problems

Most visitors come once in a lifetime and decide fast. 92% of them left between Buy Tickets and checkout.

Empire State Building's own research gave the reasons. A last-minute decision was the top reason for not buying online, 38–43% across the 2025 waves, and "not sure which ticket to buy" came second, 13–18%. The share of tickets bought on the official site fell from 56% to 33% in a year; the rest went to resellers and city passes. The problems on the visitor side were:

  1. A last-minute decision, made on a phone that converted a third worse than desktop.
  2. Ticket tiers that people couldn't tell apart.
  3. Premium tickets and offers sitting where nobody scrolled.
  4. International visitors fighting the language and the prices.
  5. A look that didn't make the official site feel like the place to buy.
On this pageSolution

Solution and impact

  1. A short path for people who already know their ticket, the price on the card opens checkout, and a long path with details and Compare for everyone else.
  2. A ticket card that explains itself, plain names, what is included in 3 lines and Compare in every category.
  3. Every ticket on one page from the first screen, with filters that refine instead of hide.
  4. One language and currency choice that holds from the first page to payment.
  5. A new visual direction, chosen in 4 review rounds, carried to every page.
10/10
Round 2 participants found every ticket type on the new Buy Tickets page.
+5%
The target for sales of non-default tickets, set in the KPI framework before launch.
Summarize with AI

Constraints that shaped the work

  • A third-party ticketing engine, Ventrata. Checkout changes went to another vendor as proposals, each with its own business case.
  • Speed was already good, LCP 1.39 s and CLS 0.01. The redesign could not cost performance.
  • Many languages and currencies. 44.8% of visitors came from abroad, and the language had to be chosen twice.
  • A release date set at kick-off, with a smaller first launch.
  • WCAG built into the concepts from the start.

Discovery research that changed the framing

  • Visitors arrive ready to buy. Buy Tickets was the most clicked element on Home, on every device.
  • Most of the offer was out of sight. On a phone, 27% of visitors reached 5% of the Buy Tickets page and 11% reached 20%.
  • Ticket tiers confused people. "Not sure which ticket to buy" was the second reason for buying elsewhere, and the 86th + 102nd floor page bounced 48.6% against 19.3% for the 86th floor.

Decision 1

Problem: a last-minute decision, made on a phone.

Decision: a mobile-first Buy Tickets page with 2 paths through it. Prices sit on every button, and the photos are a swipeable carousel.

KPI: checkout funnel entry rate, the share of all visitors who reach the ticketing flow. Target set before launch: +20% against the pre-launch baseline, measured in GA4.

The short path

For visitors who already know their ticket, the price on the card opens checkout on the same page.

Buy Tickets: the 86th Floor card, its button reads Buy tickets from $46
Checkout opens on the same page: General Admission, one adult preselected
Checkout: date, today and tomorrow first
Checkout: a sunset time slot selected, the total in the Continue bar

The long path

For visitors still deciding, from Home to Buy Tickets, then everything a ticket includes before booking it.

Home: Your New York moment awaits, Buy tickets
Buy Tickets: the title, the category filters and the Popular tickets
Buy Tickets, Premium & Proposals: the Premium Experience card, Book tour from $175 and More details
More details: everything the Premium Experience includes, Learn more, Compare and Book tour from $175
Checkout: Premium VIP Experience, one person from $175
Checkout: date and time, every slot with its price

Decision 2

Problem: tickets people couldn't tell apart.

Decision: a card that explains the ticket on its own, and Compare in every category. Compare ends every category and opens a table of what each ticket includes, one ticket at a time on a phone.

KPI: premium ticket conversion, the share of premium tickets in all sales. Baseline 55.7% from the Empire State Building revenue team, target +5%.

The 86th Floor Observation Deck card on the live Buy Tickets page
  1. A photo of the real view, 3 per card, swipeable.
  2. The full name. Empire State Building instead of ESB, which participants didn't recognize.
  3. The starting price on the button, which participants used to shop within a budget.
  4. What is included, in 3 lines.
  5. More details, the full list with Compare and a book button.
Buy Tickets: the end of the Popular category, with Compare under the cards
Compare tickets, Popular: the 86th Floor ticket, a tick or a dash for every feature, arrows to the next ticket
Compare tickets: the next ticket in the table, with Buy from $46

Not shipped

What didn't ship: Day and Night.

Plain ticket names across the whole range, and Day and Night, a single photo that turns from day to night instead of 2 stacked pictures. Both were agreed with the Empire State Building, then neither was tested nor built: the content management system couldn't hold them.

The same card with one view by day
Buy Tickets, Exclusive experiences: the AM/PM card with a day photo stacked over a night photo

As it is vs as planned.Point at the screen: the planned photo turns from day to night.

Decision 3

Problem: offers nobody saw.

Decision: every ticket on one page from the first screen, filters that refine instead of hide. We first built filtered categories. In Round 1, 7 of 10 people didn't understand the filter names and 5 of 10 expected to see everything first, so all tickets became the default and the filters a shortcut. In Round 2, all 10 found every ticket type.

KPI: ticket type visibility rate, how many visitors see or tap a ticket beyond the top 3. Baseline 3% on mobile and 5% on desktop in Clarity, target 20–25%, 1 visitor in 4.

The new page: the title, the category filters and the 86th Floor card with its price
Click map above the fold: a hero photo and a reservations notice, no ticket in sight

Above the fold.

The new page a little lower: the Flex ticket, its perks and More details
Click map at 5% of the page: 1 ticket per screen, See ticket details almost never tapped

Click map, 5% down.

The new page: the Holidays category with its own cards
Scroll map at 5%: 27.12% of visitors reached this point

Scroll map, 5% down.

The new page: Express Pass, each category ending with Compare
Scroll map at 20%: 11.11% of visitors reached this point

Scroll map, 20% down.

Decision 4

Problem: international visitors fighting the language and the prices.

Decision: one language and currency choice that holds from the first page to payment. The language had to be chosen twice and prices stayed in dollars until checkout, yet non-English visitors converted better, Chinese at 4.67% and Japanese at 3.21% against 2.51% for English. The proposal: one menu, the language detected and remembered, local prices and date formats.

KPI: localization effectiveness, checkout completion of international visitors. The baseline is set after launch.

Home hero in English: World's most famous building, Buy tickets
Home hero in Spanish: El edificio más famoso del mundo, Comprar entradas
Home hero in German: Das berühmteste Gebäude der Welt, Tickets kaufen
Home hero in French: Le bâtiment le plus célèbre du monde, Acheter des billets
Home hero in Dutch: De beroemdste gebouwen ter wereld, Koop tickets
Home hero in Portuguese: O edifício mais famoso do mundo, Comprar ingressos
Home hero in Italian: L'edificio più famoso del mondo, Acquista biglietti

7 languages.The same hero, the navigation and the button in each language.

Decision 5

Problem: a look that didn't make the official site feel like the place to buy.

Decision: a new visual direction, chosen in 4 review rounds. Concepts came from several designers. Stakeholders judged them by user impact, not taste, and kept mine every round; Round 2 testers called it modern and on-brand, and it is the identity on the live site today.

Round 113 JanRound 1, direction 1: a black page with the tower in a photo frameRound 1, direction 2: World's Famous Building split around a photo of the towerRound 1, direction 4: a big headline over the city at nightRound 1, direction 5: a full-screen event photoRound 1, my direction: the hero with fine gray lines and a blue card with arrows at the bottomChosen
Round 223 JanRound 2, direction 1: the tower in the sky, the headline over itRound 2, my direction: the tower against the sky with rays, ratings, light color, hours and weather under itChosen
Round 35 Feb—Round 3, my concept: the logo badge in the nav, the info row under the towerChosen
Round 418 FebRound 4, Art Deco / Iconic AttractionRound 4, my concept: Modern Attraction / Media-ForwardChosen

The chosen style, carried to every page

The first UI round, the moment the concept became templates. Details changed in later rounds.

Home: the tower in the sky, World's most famous building, Buy tickets
Home: Popular tickets, each card with its starting price on the button
Buy Tickets: the category filters on top, the 86th Floor card first
Premium guided tour: the dark theme for premium experiences, Buy tickets from $180
Premium guided tour: about the tour and what is included
Premium guided tour: compare tickets inside the page
Home: Seen at the Empire State Building, visitors' own photos

Design system

A component library and a section library, so new pages are assembled, not designed.

  • 226 tokens, 117 component sets, 1,213 variants, each with Desktop, Tablet, Mobile and Wide Desktop modes.
  • Sections on top of the atoms, so a first-time event page still looks finished, and templates readable by people and AI search.

Design

  • Figma

    Libraries, 226 tokens, 1,213 variants

  • Claude

    Design-system audit

Data

  • Google Analytics 4

    Funnel, devices, languages

  • Microsoft Clarity

    Heatmaps, scroll depth, recordings

  • Ventrata

    Ticketing and checkout data

Standards

  • WCAG AA

    Built into the concepts from the start

Process

Not a line. A loop with 2 test rounds and 4 feedback rounds in it.

StageWhenDeliverablesWhat sent us back and trade-offs
Kick-off and dataOct 2025GA4, BrightEdge, competitor and Baymard research.—
CRO auditOct–NovFunnel, heatmaps, Core Web Vitals.92% drop, so checkout became the core of the scope.
IAOct 27A reimagined structure: Experiences, Plan your visit, About.Gave up the safety of a structure that already converted, because visitors arrive in planning mode and the museum and exhibits were invisible.
Quick wins for VentrataNov 12Checkout recommendations I defined from the audit.—
KPI frameworkNov → Jan3 versions.Baselines updated as data arrived.
UX-1 → UX-4Nov → JanAll templates, checkout v2.Reviews each round.
Visual concepts 1–4Jan → Feb 184 rounds, my concept kept each time.—
First-launch scopeFeb 24A smaller first release, search limited to tickets.Phased the release: the first launch left out the AI ticket assistant, group sales, planning sections and site-wide search; the second launch shipped the full scope.
Usability testing, Round 1Feb 2610 sessions, mobile wireframes.Filters renamed, show all, add-ons before payment.
Usability testing, Round 2Mar 1210 sessions, mobile UI.Deferred comparison across categories, the most requested feature, 7/10 then 10/10, to the second launch, because the ticketing platform couldn't support it for the first one; compare inside a category at launch. Full name, real views.
UI-1 → UI-3Mar → May4 feedback rounds.Reused system components over bespoke special-experience sections, saving 3 days of build. Price order, included in every ticket, $5 fee.

Lessons

What I'd do again, and what I'd do earlier

  1. Put the vendor in the room on day one. The most requested feature in testing, comparison across categories, waited for the second launch.
  2. Treat baselines as drafts. Funnel entry moved from 2.4% to 6.5% between versions; targets set on the first number would have been meaningless.
  3. Test copy with the layout. Most hesitation in both rounds came from words, "ESB", "Green Room", "From $X", not structure.

See other cases