frosen.design

← Back To Work

TICKETMASTER / DISCOVERY

Transforming how fans discover events by city

Ticketmaster powers live entertainment at global scale, helping millions of fans discover and access events around the world.
The platform processes 600M tickets annually across 35+ countries, supporting thousands of artists, teams, festivals and venues.

I led the design of Ticketmaster’s City Destination Pages, creating a scalable discovery experience that helps fans explore concerts, sports and entertainment happening in cities around the world.

MY ROLE

Product Design Lead and Researcher

TEAM

Product, Engineering, SEO, Marketing

01 / CONTEXT

From three disconnected page types to one global experience

Ticketmaster already had city-related experiences, but they had evolved separately across platforms and markets.

North America had filterable City Genre Pages that were difficult to discover outside search. International markets had richer city guides that were buried and not indexable, while other markets still relied on legacy city pages managed through older tooling.

Together, city pages accounted for only around 1% of discovery visits, despite being the only part of the experience designed to answer a simple question: what’s happening in this city?

The original brief was relatively tactical: consolidate the existing city experiences. But the evidence suggested there was a larger opportunity than simply recreating what already existed.

Legacy City Pages for North America and UK Markets

Legacy City Pages Click Rate: Nov – Dec 23 (Desktop & Mobile)

02 / OPPORTUNITY

Turning a platform clean-up into a discovery product

The traffic numbers initially made city pages look small. SEO told a different story.

Despite their limited visibility, existing city pages were already Ticketmaster’s third-largest organic entry point behind Artist Pages and the Homepage, and represented 11% of SEO traffic for fans searching for local events.

At the same time, broader searches such as things to do in Los Angeles were being captured by competitors and travel platforms rather than Ticketmaster.
‍
We reframed the project around a new parent experience:

A City Destination Page that could become the starting point for exploring live entertainment by location.

The goal was to connect three things that had previously been treated separately:

Organic acquisition → event discovery → ticket purchase

Rather than immediately optimise everything for conversion, the initial north star focused on search visibility and organic traffic, with deeper commercial optimisation informed by what we learned after launch.

Ticketmaster Discovery Visit Shares vs. Organic SEO Visit Shares

Understanding the competitive landscape

I also reviewed ticketing, event discovery and destination platforms to understand how others approached city-based discovery. The analysis surfaced useful patterns around category navigation, event prioritisation, pricing, nearby-city links and time-based discovery.
‍
It also helped clarify our positioning: rather than trying to compete with travel guides like Time Out, the opportunity was to create a city experience built around live-event discovery and ticketing.

Direct and Indirect Competitor Analysis

03 / ROLE

Leading design and research from definition to validation

I led design and user research across the core initiative, working with Product, Engineering, SEO and Marketing from early discovery through to the validated experience.
‍
I was the sole designer on the core work, responsible for the desktop and mobile experience as well as the research and synthesis that shaped it.

My work included:

Product strategy · User research · Research synthesis · Workshops · Information architecture · Prototyping · Interaction design · UI design · Analytics · Engineering collaboration

I designed and facilitated the discovery workshops, helped turn the opportunity into roughly 200 ideas and an initial prioritisation, planned the research approach with our researcher, co-moderated interviews and led the synthesis into MVP changes and future recommendations.  

A principle I carried through the work was that recommendations needed evidence behind them. Findings were connected to hypotheses and participant counts rather than relying on individual quotes or design preference.

Collaborative Workshop Outcome: Value Proposition

Wireframe Overview and User Flow Diagram

04 / EVIDENCE

Combining behavioural data with fan research

We used different evidence sources to answer different parts of the problem.

Learning from the existing experience

Analytics showed that around 10% of users interacted with filters, while category navigation was used by approximately 2.5%.

Understanding two different discovery behaviours

Research surfaced two meaningful contexts.

Locals were often already familiar with venues and relied on recommendations, friends and existing habits. They were particularly interested in what was happening tonight or this weekend.

Travellers were typically planning further ahead and needed more orientation around dates, venues, areas and what was worth seeing before they could make a decision.

Validating the proposed experience

We tested the designed experience through 5 moderated interviews and 40 unmoderated sessions across New York and London, covering desktop and mobile and including both locals and travellers.
‍
The overall proposition tested positively, but several findings directly changed the product:

  • Users wanted better ways to narrow large amounts of content

  • Top-level categories sometimes felt too broad

  • Price was the most consistently requested missing information

  • “Featured” was interpreted as paid promotion

  • Editorial content was the least valued module

  • 33 of 40 participants wanted “This month”, compared with 29 wanting “This weekend”

User Research (Usertesting.com) Tested Designs

User Testing: City Page Module - Results

05 / KEY DECISIONS & TRADE-OFFS

Balancing what ranks with what helps fans choose

Build the parent, not another legacy page

Rather than simply globalising the existing City Genre Page, we created a new parent destination that could eventually bring the fragmented city experiences into one structure. The trade-off was accepting some temporary cross-platform complexity in exchange for a better long-term architecture.

Treat SEO vs filtering as a product problem

SEO needed crawlable links and inventory exposure. Fans wanted stronger filtering. Rather than optimising completely for one side, we validated both behaviours. The MVP retained crawlable category journeys, while later sub-category pages gave users greater depth and created new indexable destinations.

Prioritise launch speed over price

Price was the strongest missing information signal in research, but was excluded from the MVP. We accepted the scope trade-off to get the product to market while retaining the research evidence as a future recommendation. It remains one of the decisions I would challenge more strongly today.

SEO vs Fan Value: Circles = kept in MVP; squares = changed/deferred by research. Blue = validated, amber = contested.

06 / SOLUTION

One flexible system for hundreds of cities

The final City Destination Page was designed as a journey from orientation to choice.

It combined:

  • City introduction

  • Must-see events

  • Date-based discovery, including 'This week' and 'This month' pre-defined filters

  • Best-selling events by major category

  • All events list

  • Venue discovery

  • Editorial content

Behind the interface, we designed the experience as a configurable system rather than an individual page.

The solution included:

  • A consistent global URL structure

  • City identifiers and geographic radius

  • City-specific configuration

  • Rules for indexing and SEO metadata

  • API-fed event and venue content

  • Configurable editorial and module ordering

The same underlying experience could therefore support a market like New York with thousands of events as well as much smaller destinations.

Evolving after launch

The product continued to evolve based on the initial research and live experience tracking. Later additions included 'Happening This Week/Weekend' event carousels, sub-category city pages, and internal linking to other city pages.

The shipped experience remained recognisably connected to the product we tested, while the system allowed new discovery modules to be layered in over time.

SEO vs Fan Value: Circles = kept in MVP; squares = changed/deferred by research. Blue = validated, amber = contested.

Project Timelime Overview

07 / IMPACT

From migration task to global discovery surface

By September 2025:

Performance began improving noticeably around 45 days after launch, before accelerating through the following months.
‍
Following the migration of the North American genre pages into the new structure, the SEO team described City Destination Pages as becoming the default landing experience for geographic queries.

The results also gave us a clearer picture of where the product was strongest. Transactional geographic queries such as concerts performed particularly well, while broader things to do searches remained a larger, less-proven opportunity.
‍
That evidence helped shape what should come next rather than treating launch as the end of the project.

08 / CONCLUSION

Designing the system behind the page

City Destination Pages started as a consolidation task and became a new way for Ticketmaster to capture and serve geographic discovery.

The most important design challenge was not determining how a city page should look. It was defining what it needed to be good at, then balancing search visibility, fan utility and global scalability without pretending those needs would always align.

The project reinforced three principles that continue to shape how I work:

Hold competing needs long enough for evidence to decide.

SEO and fan experience did not always point toward the same solution, and treating that tension explicitly led to stronger decisions.

Structure research so it can survive beyond the first release.

Connecting recommendations to hypotheses and evidence gave later phases a foundation rather than forcing the team to rediscover the same problems.

Design the system, not the individual screen.

The template, configuration model and API-driven modules were considered alongside the experience itself, allowing one product to scale across markets and hundreds of destinations.

There are also things I would approach differently today. Price remains absent despite being one of the clearest research signals, and I would challenge that feasibility question earlier. I would also bring engineering setup into discovery sooner and invest earlier in the inspirational things to do layer that remains one of the largest opportunities for the product.

Want to get in touch?

Always happy to chat about interesting products, teams and opportunities.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.