Analytics drilldowns and comparisons

Analytics is not only a dashboard. Most tables and charts are entry points into narrower views, so you can move from agency-wide performance into a specific artist, booker, venue, organizer, city, or country.

Compare keeps your analytics filters, then shows the current period beside the matching prior-year window.

Main lenses

Lens	What to use it for
Overview	Agency-wide KPIs, monthly trend, revenue by artist and booker, and top venues.
Bookers	Booker KPI cards, revenue by booker, leaderboard, efficiency chart, monthly booker trends, and deal-size distribution.
Artists	Artist KPI cards, roster table, revenue by artist, new versus repeat artist revenue, ROI scatter, concentration, tier mix, genre revenue, and per-artist trends.
Venues	Venue KPI cards, repeat-rate signals, revenue by city, new versus repeat venue revenue, concentration, and deep venue table.
Organizers	Organizer KPI cards, organizer concentration, deep organizer table, repeat behavior, payment health, payment lag, and deal health.
Geographic	City and country focus, regional KPIs, map, revenue bars, concentration over time, market growth tables, and all-region table.

The filter bar stays with you across these lenses. Period, event status, invoice status, per-event revenue range, artist, booker, country, organizer type, and capacity filters change the numbers and are preserved when you open supported compare pages.

The default event-status filter is confirmed events. Clearing or changing it can make draft, pending, or cancelled records appear in analytics if the current user has access to them.

Analytics Bookers tab with KPI cards and revenue by booker ranking — Booker rankings are not just a people list: they combine show count, revenue, average revenue, margin, trend, and deal-size context.

Analytics Geographic tab with city focus, regional KPIs, and map bubbles — Geographic analytics combines city or country KPIs with map context and regional rankings, so market concentration is visible before you open a detail page.

Analytics Venue Performance table with sortable columns for city, capacity, shows, revenue, dates, and repeat percentage — Venue rows can be sorted, opened, previewed, selected for comparison, or used to move into a narrower venue detail page.

Analytics Organizer Performance table with organizer type, country, deals, revenue, profit, margin, payment lag, and repeat percentage — Organizer rows make buyer-side performance inspectable before drilling down: you can compare relationship type, country, deal volume, margin, payment timing, and repeat rate.

Detail pages

Open a row when you need the story behind a ranking. Detail pages keep the same analytics scope and show only records the current user is allowed to see.

Detail page	What it shows
Artist	KPIs, period trend, top venues, top cities, top bookers, and the underlying show list.
Booker	KPIs, period trend, top artists, top organizers, top venues, top cities, and booked shows.
Venue	KPIs, map context, and the shows connected to that venue.
Organizer	KPIs and the deal list for that organizer.
City	KPIs, map context, venue table, and shows in that city.
Country	KPIs, map context, top cities or venues, and shows in that country.

Analytics artist detail page with compare controls, filter chips, KPI cards, a revenue and profit trend, top venues, top cities, and top bookers — Artist and booker detail pages turn a ranking row into a focused operating view: period KPIs, trend, related top lists, compare actions, and the underlying shows.

Analytics city detail page with compare controls, filter chips, KPI cards, a monthly revenue chart, a location map, and venues in the city — Geographic detail pages add map context and venue or show lists, so a city or country result can be checked against the records behind it.

Analytics venue detail page with venue location, filter chips, KPI cards, monthly revenue chart, map, and shows at the venue — Venue detail pages combine relationship history, map context, period revenue, and the shows at that room, so venue performance can be checked against actual bookings.

Analytics organizer detail page with organizer type, filter chips, deal KPIs, monthly revenue chart, and deals with the organizer — Organizer detail pages use deal language instead of show-only language: they focus on the buyer relationship, deal count, revenue, average deal value, payment context, and the deals behind the numbers.

Analytics country detail page with country KPIs, monthly revenue, active cities map, top cities, top venues, and top organizers — Country detail pages roll up city, venue, organizer, and show data for a market, then keep the top lists visible so the headline number is tied back to the operating records.

Mobile analytics city detail page with compare buttons, filter chips, stacked KPI cards, and monthly revenue section — On mobile, the same drilldown model stacks the header, compare actions, filters, KPI cards, and trend section into a single-column review flow.

Each detail page can lead to two comparison paths: compare that entity with similar entities, or compare that entity against its prior-year period.

The monthly trend on detail pages can open the underlying shows for a month or year. Use that when a chart spike needs investigation: it gives you the actual show list with revenue, profit, and margin instead of leaving the chart as a dead end.

Some tables also support preview and row actions. Shift-click or the preview affordance opens a compact preview; the row menu can open the entity, copy a link, or start an entity comparison.

Compare with prior year

Use Compare with prior year when the question is about change over time. The page compares the selected date range with the matching prior-year window.

There are two modes:

Mode	How it behaves
Agency-wide	Opens from the Analytics overview or a tab and compares the whole filtered analytics set.
Entity-scoped	Opens from an artist, booker, venue, organizer, city, or country detail page and compares only that entity.

The agency-wide version keeps the Analytics tabs. Overview shows mover sections for artists, bookers, venues, organizers, and cities; a specific tab narrows the movers to that kind. The entity-scoped version focuses on the selected entity and does not show the full tab set.

If the selected period is All time, there is no matching prior window. In that case the compare page explains that a prior-year comparison cannot be calculated for all-time data.

Prior-year comparison is most useful for bounded periods such as this month, this quarter, YTD, last 12 months, last year, or a custom range. The trend chart uses ghost bars for prior-year values so current revenue and profit can be read beside the same months from the previous year.

Mobile Analytics compare page with stacked current and prior periods plus the KPI comparison table — On mobile, Compare with prior year stacks the same period context and KPI deltas into a scannable single-column view.

Mobile Analytics compare page showing the prior-year overlay chart and artist mover rankings — The mobile comparison continues into the chart and mover lists, so you can still inspect which artists, bookers, venues, organizers, or cities changed most.

Compare entities

Use entity comparison when the question is about relative performance in the same period, such as two venues, several artists, or a group of bookers.

Analytics entity comparison page comparing four artists with selected entity pills, leader cards, and trend overlay — Entity comparison keeps the same filter model, then ranks the selected entities across shows, revenue, profit, margin, and trend shape.

The compare page supports two to six entities of the same type:

Selection	Result
Two entities	Side-by-side KPI strip, shared trend, and top lists.
Three to six entities	Leader cards, shared trend, top lists, and small multiples.
One or zero entities	Empty state that sends you back to choose more entities.
More than six entities	Empty state explaining the selection limit.

You may also see an empty or reduced comparison if a selected entity was deleted, filtered out, or outside your analytics scope.

Entity comparison uses the same period and filters as the page you came from. It supports artists, bookers, venues, organizers, cities, and countries. The shared KPI model is shows, revenue, profit, margin, and average deal size.

Top-list depth depends on the entity type:

Compared entity	Secondary lists currently available
Artist	Top venues, top cities, and top bookers.
Booker	Top artists, top venues, and top organizers.
Venue	KPI and trend comparison; top-list data is not populated yet.
Organizer	KPI and trend comparison; top-list data is not populated yet.
City	Top venues.
Country	Top cities, top venues, and top organizers.

For three to six entities, small multiples help you compare shape, not only total size. Use the normalization option in the trend chart when one entity is much larger than the others and you want to compare relative momentum.

Scopes still apply

Analytics access, artist scope, booker-scoped analytics, and financial-data permissions apply to drilldowns and compare pages too. A comparison should not reveal records or money the user cannot see elsewhere.

For example, a user with booker-scoped Analytics sees only analytics for events where they are the booker. A user without financial-data permission may see less commercial detail than someone with full financial access.

The same rule applies to comparison URLs. Sharing a compare link does not bypass permissions; another teammate only sees the entities and values their role, artist scope, booker scope, and financial permissions allow.

Data quality

Comparison pages are only as useful as the underlying records. Keep shows connected to the right artist, booker, venue, organizer, city, status, dates, revenue lines, cost lines, contracts, and invoices. Missing links can make a real business relationship look absent from Analytics.