Skip to content
Try free
PTI Digital logoSports Analytics

A 10-person team turned an awkward API into a product they could sell

PTI wanted to make ticketing data usable by the sports clubs they serve, but the portal's API was awkward and its payload buried the useful fields inside columns of JSON. Their own team unpacked it in Mammoth, blended it with historical seasons, and published it to Tableau — a dashboard their clubs had never had access to before.

0
lines of code written to unpack the JSON
1
new service line, sellable to every club
Zero-touch
once set up, it runs without them

The workflow

What replaced the manual work

  • Ticketmaster API, JSON payloads
  • Historical season data
One pipeline
  • Connect
  • Clean
  • Automate
  • Share

Recorded once, re-run on a schedule.

  • Club ticketing dashboards in Tableau, via PostgreSQL
  • A sellable service line

Outcomes

What changed

  • Multiple columns of JSON from the ticketing API extracted into usable fields, by PTI rather than by engineers
  • Current ticketing data blended with past seasons, so a club sees a trend rather than a snapshot
  • A zero-touch process end to end: set up once, then it runs and publishes on its own
  • Ticketing insight put in front of sports clubs who had never had access to it
  • A new service line PTI can sell to every club on its books, without hiring to support it

What they used

The parts of Mammoth involved

  • Data Engine
  • Scheduled refresh
  • Custom roles
  • Free viewers

More case studies

Starbucks · 20 days → hours20 days of report assembly, down to hours — across 17 countriesRethinkFirst · 10x50+ hours a month saved, and new analysts productive in under two weeksMUFG · 19KYC standardised across 19 countries, and a week of Excel became 20 minutes

Start with one source and one question.

That's how this deployment began too. Twenty minutes on the free plan is a fair test.

Try freeBook a demo
  • 21-day Pro trial
  • No credit card
  • Viewers always free