TickerDocs
Tools

get_performer_analytics

Shows one performer's numbers now: rank, prices across its events, X activity, or with `view` any of them by date.

When to use it

  • You want where a performer stands now: rank, average prices, listings and social activity.
  • You want a performer's popularity rank, prices or X activity by date: view rank (or range alone), price or social.
  • You want the performer's dates: view events for upcoming ones (add played true for past ones), or view tour for how each date's primary sale went.
  • You want one event's numbers: use get_event_analytics. It replaces get_performer_rank_chart, whose name still answers: see Old names.

Inputs

  • view (string): now (the default): the numbers now. rank: the popularity rank by date. price: the day's mean get-in and median across its events, before fees and all-in. social: the day's X totals. Each by-date view returns one row per date over range. events: the performer's upcoming events, soonest first, at most 50. list: a page of performers with their ranks and upcoming event counts. tour: the performer's upcoming dates with the primary seats each released, the share taken in the first 24 hours, the primary tickets left, the resale get-in against primary and the general admission floor against the cheapest reserved floor, with its 12-month track record (Max plan and above). One of now, rank, price, social, events, list, tour.
  • performer_id (string or integer): The performer, by its Ticker id (pf plus ten characters), as the other tools return it.
  • columns (array of strings): Now: the columns to return, spelled as list_screen_columns gives them in the pa group, without the pa. prefix. Leave it out for every column. It does not apply to the by-date views.
  • range (string): With a by-date view, how far back it reads. Leave it out for 28 days; all reaches back up to one year. Passed alone, it reads the popularity rank. One of 7d, 14d, 28d, 90d, all.
  • render (boolean): With a by-date view, include a chart image ahead of the data. Set false for the data only, a smaller answer.
  • played (boolean): With events, true returns the performer's dates that already took place, newest first, at most 50, each with the last get-in read before the show. Max plan and above.
  • search (string): Find performers by part of the name, at least 2 characters, instead of naming one performer_id.
  • category_id (integer): With a list, only performers in this category.
  • subcategory_id (integer): With a list, only performers in this sub-category.
  • event_count_min (integer): With a list, only performers with at least this many upcoming events.
  • event_count_max (integer): With a list, only performers with at most this many upcoming events.
  • listings_current_min (integer): With a list, only performers with at least this many listings across their events.
  • listings_current_max (integer): With a list, only performers with at most this many listings across their events.
  • computed_at_from (date-time): With a list, only analytics computed at or after this time.
  • computed_at_to (date-time): With a list, only analytics computed at or before this time.
  • sort_by (string): With a list, the sort key: name (the default), a rank, computed_at, event_count or an analytics number. A rank keeps the ranked performers; an analytics number keeps the performers that have one. One of name, popularity_rank, lifetime_rank, computed_at, event_count, avg_median_price_current, avg_lowest_price_current, listings_current, tickets_delta_1d, tickets_delta_7d, likes_current, views_current, price_volatility_7d, price_volatility_14d.
  • sort_order (string): asc or desc. The default is asc for name and desc for every other key. One of asc, desc.
  • include_analytics (boolean): With a list, add each performer's analytics numbers under analytics.
  • parking (string): Parking passes sold as their own events: hide (the default) leaves them out, only returns parking alone and include returns both. One of hide, include, only.
  • page (integer): With a list, the page to read, from 1.
  • limit (integer): With a list, rows per page: 25 by default, at most 100.

Examples

How is this artist doing on the resale market right now?

{ "performer_id": "pf7k2m9q4x1z" }

What is the chance this team makes the playoffs?

{
  "performer_id": "pf9w4c7x2n5q",
  "columns": ["playoff_prob_current", "playoff_prob_asof_date"]
}

How is this artist's tour selling on the primary market?

{ "performer_id": "pf7k2m9q4x1z", "view": "tour" }

What comes back

  • Now: one object with the performer's columns: popularity_rank and lifetime_rank (a higher number is better) and their changes, average prices across its events, listings, tickets and X activity.
  • For a sports team, playoff_prob_current is the chance from 0 to 1 that the team reaches its postseason. A null there means no clear market for that team, never a low chance. prediction_markets when a market covers the performer.
  • x_buzz carries recent activity on X; it is null when Ticker has no recent X reading. A columns pick never removes it. null means Ticker has nothing for the performer.
  • With view rank: one row per date, oldest first, with snapshot_date, popularity_rank, lifetime_rank and their places, and performer_name. A null rank means unranked that date, not zero. A chart image comes first unless render is false.
  • With view price or social: one row per date, oldest first. When your plan reads less far back than range, plan_capped is true and withheld says what was cut.

Limits and quota

  • Reads only: it changes nothing.
  • Each call spends one MCP request.
  • view tour and played are on the Max plan and above.

On this page