Shedd Ticketing Research: Findings and a Proposed Test

OVERVIEW

Our team combined GA4 findings with 16 moderated eye-tracking sessions to investigate ticket-purchasing friction. I interpreted the Tobii sessions and identified the conversion gap between fixed- and variable-price tickets. We recommended showing variable prices earlier and proposed an A/B test. The potential revenue effect was modeled, not measured.

TIMELINE

Spring 2025

ROLE

UX Researcher

TEAM

Hridya Nadappattel, Iris Sun, Saskia Suherman, Conor Mack

FOCUS

UX Research

The pricing-tier conversion gap

The March 1–31, 2025 GA4 comparison reported 91,000 Chicago-resident visitors to fixed-price tickets ($19.99) at 4.7% conversion, and 145,000 non-resident visitors to variable-price tickets (average $41; range $37–46) at 3.1% conversion. These are different visitor and ticket groups; the comparison does not establish that price presentation caused the gap.

I was responsible for reading and interpreting the Tobii eye-tracking sessions and identified the pricing-tier conversion gap and its financial opportunity. The 16 sessions describe the team study, not my personal moderation count. The team combined the study with GA4 findings and prioritized recommendations using RICE scoring.

What the eye-tracking study showed

Aggregate eye-tracking gaze visualization over Shedd’s ticketing interface

The team’s observations and synthesis identified confusion around inconsistent prices, hesitation at calendar and time steps, and difficulty navigating backward through the purchase flow.

The aggregate gaze visualization shows attention over the interface. Gaze alone does not establish motivation, purchase intent, or conversion impact. These findings supported recommendations about price visibility, calendar complexity, and navigation.

Recommendations and a proposed test

Proposed Shedd ticketing screens with a price calendar and navigation changes; implementation not established

The team recommended a price calendar on Plan Your Visit so visitors could explore variable prices before entering checkout. Other recommendations addressed calendar clarity and navigation through the flow. These were proposed changes, not a shipped redesign.

We proposed an A/B test of earlier price disclosure, including whether it reduced checkout entry just to discover the price. Running a test would produce evidence about that change; it would not automatically validate the entire modeled revenue opportunity.

What the opportunity estimate can and cannot say

If the 145,000 variable-price visitors converted at the fixed-price rate, the 1.6 percentage-point difference would equal 2,320 additional conversions. At $37, $41, or $46 per ticket, the conditional monthly ticket-revenue estimate is $85,840, $95,120, or $106,720—about $86K–$107K.

This assumes one ticket at the listed price per conversion, not checkout order value. It is a modeled scenario, not measured revenue, a verified loss, or confirmed recoverable conversions. Different visitor groups and one month of observational data do not establish a causal effect.

Project status

The record establishes team recommendations and a proposed test. It does not establish implementation, a completed A/B test, or measured revenue or conversion gains.

This page is looked after by the Archivist, an agent I built that works from my primary research and can’t publish without me. Here’s how that works.

Shedd Ticketing Research: Findings and a Proposed Test

OVERVIEW

Our team combined GA4 findings with 16 moderated eye-tracking sessions to investigate ticket-purchasing friction. I interpreted the Tobii sessions and identified the conversion gap between fixed- and variable-price tickets. We recommended showing variable prices earlier and proposed an A/B test. The potential revenue effect was modeled, not measured.

TIMELINE

Spring 2025

ROLE

UX Researcher

TEAM

Hridya Nadappattel, Iris Sun, Saskia Suherman, Conor Mack

FOCUS

UX Research

The pricing-tier conversion gap

The March 1–31, 2025 GA4 comparison reported 91,000 Chicago-resident visitors to fixed-price tickets ($19.99) at 4.7% conversion, and 145,000 non-resident visitors to variable-price tickets (average $41; range $37–46) at 3.1% conversion. These are different visitor and ticket groups; the comparison does not establish that price presentation caused the gap.

I was responsible for reading and interpreting the Tobii eye-tracking sessions and identified the pricing-tier conversion gap and its financial opportunity. The 16 sessions describe the team study, not my personal moderation count. The team combined the study with GA4 findings and prioritized recommendations using RICE scoring.

What the eye-tracking study showed

Aggregate eye-tracking gaze visualization over Shedd’s ticketing interface

The team’s observations and synthesis identified confusion around inconsistent prices, hesitation at calendar and time steps, and difficulty navigating backward through the purchase flow.

The aggregate gaze visualization shows attention over the interface. Gaze alone does not establish motivation, purchase intent, or conversion impact. These findings supported recommendations about price visibility, calendar complexity, and navigation.

Recommendations and a proposed test

Proposed Shedd ticketing screens with a price calendar and navigation changes; implementation not established

The team recommended a price calendar on Plan Your Visit so visitors could explore variable prices before entering checkout. Other recommendations addressed calendar clarity and navigation through the flow. These were proposed changes, not a shipped redesign.

We proposed an A/B test of earlier price disclosure, including whether it reduced checkout entry just to discover the price. Running a test would produce evidence about that change; it would not automatically validate the entire modeled revenue opportunity.

What the opportunity estimate can and cannot say

If the 145,000 variable-price visitors converted at the fixed-price rate, the 1.6 percentage-point difference would equal 2,320 additional conversions. At $37, $41, or $46 per ticket, the conditional monthly ticket-revenue estimate is $85,840, $95,120, or $106,720—about $86K–$107K.

This assumes one ticket at the listed price per conversion, not checkout order value. It is a modeled scenario, not measured revenue, a verified loss, or confirmed recoverable conversions. Different visitor groups and one month of observational data do not establish a causal effect.

Project status

The record establishes team recommendations and a proposed test. It does not establish implementation, a completed A/B test, or measured revenue or conversion gains.

This page is looked after by the Archivist, an agent I built that works from my primary research and can’t publish without me. Here’s how that works.

Shedd Ticketing Research: Findings and a Proposed Test

OVERVIEW

Our team combined GA4 findings with 16 moderated eye-tracking sessions to investigate ticket-purchasing friction. I interpreted the Tobii sessions and identified the conversion gap between fixed- and variable-price tickets. We recommended showing variable prices earlier and proposed an A/B test. The potential revenue effect was modeled, not measured.

TIMELINE

Spring 2025

ROLE

UX Researcher

TEAM

Hridya Nadappattel, Iris Sun, Saskia Suherman, Conor Mack

FOCUS

UX Research

The pricing-tier conversion gap

The March 1–31, 2025 GA4 comparison reported 91,000 Chicago-resident visitors to fixed-price tickets ($19.99) at 4.7% conversion, and 145,000 non-resident visitors to variable-price tickets (average $41; range $37–46) at 3.1% conversion. These are different visitor and ticket groups; the comparison does not establish that price presentation caused the gap.

I was responsible for reading and interpreting the Tobii eye-tracking sessions and identified the pricing-tier conversion gap and its financial opportunity. The 16 sessions describe the team study, not my personal moderation count. The team combined the study with GA4 findings and prioritized recommendations using RICE scoring.

What the eye-tracking study showed

Aggregate eye-tracking gaze visualization over Shedd’s ticketing interface

The team’s observations and synthesis identified confusion around inconsistent prices, hesitation at calendar and time steps, and difficulty navigating backward through the purchase flow.

The aggregate gaze visualization shows attention over the interface. Gaze alone does not establish motivation, purchase intent, or conversion impact. These findings supported recommendations about price visibility, calendar complexity, and navigation.

Recommendations and a proposed test

Proposed Shedd ticketing screens with a price calendar and navigation changes; implementation not established

The team recommended a price calendar on Plan Your Visit so visitors could explore variable prices before entering checkout. Other recommendations addressed calendar clarity and navigation through the flow. These were proposed changes, not a shipped redesign.

We proposed an A/B test of earlier price disclosure, including whether it reduced checkout entry just to discover the price. Running a test would produce evidence about that change; it would not automatically validate the entire modeled revenue opportunity.

What the opportunity estimate can and cannot say

If the 145,000 variable-price visitors converted at the fixed-price rate, the 1.6 percentage-point difference would equal 2,320 additional conversions. At $37, $41, or $46 per ticket, the conditional monthly ticket-revenue estimate is $85,840, $95,120, or $106,720—about $86K–$107K.

This assumes one ticket at the listed price per conversion, not checkout order value. It is a modeled scenario, not measured revenue, a verified loss, or confirmed recoverable conversions. Different visitor groups and one month of observational data do not establish a causal effect.

Project status

The record establishes team recommendations and a proposed test. It does not establish implementation, a completed A/B test, or measured revenue or conversion gains.

This page is looked after by the Archivist, an agent I built that works from my primary research and can’t publish without me. Here’s how that works.