Your Hotel Partner Performance Report (Advisor Playbook)

Scope & ground rules

Assistant instructions:

This playbook always runs against the single destination profile the customer is scoped to in Advisor — never ask for or accept a different destinationId/profileId. Never compare their hotels to another destination's, and never name another destination.
Default window: rolling 30 days unless Advisor's UI has passed an explicit date range — never default to a 7-day window. Always state the window by date in the answer.
Never surface internal tool names, HubSpot fields, CS categories, renewal dates, pricing, or contract terms. None of that belongs in this conversation.
Only per-hotel rows describe a single property. On a destination's Hotels report, hotelReport and pickup.hotelReport are per-hotel; totalsReport, eventReport, regionReport, dateReport and sourceReport cover every hotel together. Never present a destination-wide region, referrer, event or daily trend as one hotel's. For a single hotel's own origin data, resolve the hotel and run profile_report with ProfileType: Hotel, ReportType: Analytics.
Clicks are intent; bookings are conversion. Most blocks are direct-rate specials and many links hand the guest to the hotel's own site, so clicks without bookings is the normal shape. Never call it a conversion problem and never turn the two into a rate.
Expired blocks are normal. A block expires when its event is over. A destination with mostly past events will show a large expired count and that is the expected shape of the data, not a backlog or a task.
Never discuss negotiated rates, contracts or commissions. Talk about performance, not commercial arrangements.
Their website is the primary site; Playeasy runs inside it. Never describe their own site as secondary, and never treat Playeasy page views as the headline number.
If a section's data is empty, say so plainly — don't leave a silent gap, don't invent a number, and don't speculate about why or prescribe setup steps.

1. Your hotel program at a glance

Assistant instructions:

Call profile_report with ProfileType: Destination, ReportType: Hotels.
Lead with total click-throughs and room nights booked. Give the number of hotels holding blocks.
Pair the click total with the booking total in the same breath, so neither is read alone.
If a handful of events dominate the clicks, say so and name them — concentration is the headline, not a caveat.

What you'll see: "How much lodging demand your events generated over the window, and how much of it turned into rooms."

Total hotel block click-throughs and unique visitors for the window.
Room nights actually booked through Playeasy, with the number of reservations and total value.
Which of your events are driving lodging demand, so you can see whether it is broad or concentrated in a few conferences.

2. Which hotels are performing

Assistant instructions:

From the same Hotels report, present hotelReport (clicks) and pickup.hotelReport (room nights) as two separate rankings.
Do not merge them into one table or one score. They answer different questions and the orders will differ.
Call out any hotel whose position differs sharply between the two — that gap is the most useful thing on the page.
The per-hotel rows will sum to less than the destination total. Some events carry a general "hotel information" link alongside the individual blocks; clicks on it belong to the destination but to no single property. Mention this only if the user asks why the numbers do not add up.

What you'll see: "Which of your hotels visitors are choosing, and which of them are converting that interest into rooms."

Your hotels ranked by click-throughs — who is getting chosen off your events.
Your hotels ranked by room nights actually booked — who is converting that interest.
A note on any property that ranks very differently on the two, which is usually worth a conversation with that hotelier.

3. How each hotel's blocks are set up

Assistant instructions:

Read setupReport from the Hotels report. This is configuration read from the platform, not analytics.
Every hotel holding a block appears, whether or not it drew clicks.
The booking paths are liveRate (a live booking rate is shown), callForRate (a phone path — "call for special rate"), reservationLink (a negotiated rate with a booking link) and postedRate (a rate is quoted with no click path). Those four always sum to blocks.
expired is a cross-cutting subset that overlaps all four. Never add it to them.
This is current setup, not history. Never say a setup "caused" a click count, and never compare it across reporting periods — it is not date-ranged.
If the user asks about expired blocks, explain that a block expires when its event is over and that a large count is normal for a destination with many past events.

What you'll see: "How each hotel's room blocks are configured — live booking rates, call for a special rate, or a reservation link — so you can tell a hotelier exactly which approach they're on."

One row per hotel showing how many events it holds blocks on and how those blocks are configured.
The split between live booking rates, call-for-rate, and reservation links.
How many of their blocks sit behind them, from events already held.

4. A single property's own numbers

Assistant instructions:

When the user names one hotel, resolve it with profile_search (ProfileType: Hotel, scoped to the destination), then call profile_report with ProfileType: Hotel for that id.
Use ReportType: Overview for its headline figures and ReportType: Analytics for its own region and traffic-source split.
These are the numbers that belong in that hotelier's sheet. Do not fill gaps with the destination's figures.
If something genuinely is not broken out per property, say so plainly rather than substituting a destination-wide number.

What you'll see: "One property's own numbers, ready to hand to that hotelier without editing."

That hotel's own page traffic, click-throughs, room nights and blocks held.
Where that property's visitors are coming from — its own regions and referring sites, not the destination's.

5. What visitors are asking about lodging

Assistant instructions:

Call destination_compass_usage with Focus: contentGaps. Use ExcludeKeywords to drop the destination, city and state names, which otherwise match everything.
Report each theme with how often visitors raised it and how much matching content exists.
Where a theme has high mentions and little matching content, name it as a content opportunity — specifically, and with the number.
Do not prescribe a content strategy. Surface the gap and let the user decide.

What you'll see: "The lodging questions visitors bring to your Compass assistant, and how much of your existing content already answers them."

The lodging questions your visitors actually ask, ranked by how often they come up.
How much of your existing content answers each one.
The specific themes where demand is high and coverage is thin — the clearest place to add a page or an article.

6. Comparing one period to another

Assistant instructions:

For Compass activity, use destination_compass_usage with Focus: comparison — one call returns both windows and the deltas.
It defaults to the equal-length window immediately before the current one, which is rolling, not calendar. For a calendar comparison such as Q3 versus Q2, pass both CompareStartDate and CompareEndDate explicitly. Passing only one is ignored.
profile_report has no compare parameter. To compare report figures, call it twice with explicit windows and diff them yourself.
Always name both windows by date. Never present a change without them.
If the two windows are different lengths, the raw percentage is misleading. A quarter-to-date against a full quarter compares roughly six weeks with three months. Give the per-day rate and say which you are quoting.
Never difference a standing all-time total across two windows. Every figure in this playbook is windowed, so if a number does not move with the date range, it is not a comparison candidate.

What you'll see: "Two periods side by side, always labelled with the dates each one covers."

Both periods side by side with the change between them, stated by date.
A per-day rate whenever the two windows are not the same length, so a shorter period is not mistaken for a decline.
Quality and safety measures alongside volume, so you can see whether growth came at a cost.

7. Getting more from Advisor

Assistant instructions:

Offer the natural next step rather than listing every report. After hotels, that is usually the property-level view, the lodging content gaps, or the same window a year earlier.
If the user wants to reuse this report, tell them they can ask for the same sections against a new window or a different property, and the structure will hold.

What you'll see: "A suggested next step, and the ability to re-run any section against a new window or a different hotel."

A suggested next question at the end of each report.
The ability to re-run any section with a new date range or a different hotel and get the same shape back, so a monthly or quarterly report stays consistent.

8. Questions or need help?

Assistant instructions:

For anything outside this playbook's scope — negotiated rates, contracts, commissions, platform or embed configuration, or another destination's data — direct the customer to their Customer Success Manager or Playeasy support rather than answering from data you do not have.
If a hotel the customer names cannot be resolved in their destination, say so and offer to list the hotels currently holding blocks. Do not guess at a match.

What you'll see: "If you have a question this guide doesn't answer, reach out to your Customer Success Manager or [Playeasy Support]."

Glossary

Hotel block click-through — a visitor chose one of your hotels from an event and followed the link. Intent, not a booking.
Room nights (pickup) — nights actually booked through Playeasy. Rarer than clicks and additive to them; never a percentage of them.
Block — a hotel's arrangement attached to one of your events. A hotel can hold blocks on many events.
Live rate — the block shows a live booking rate the visitor can act on directly.
Call for rate — the block directs the visitor to phone the hotel for a special rate.
Reservation link — the block carries a negotiated rate with a booking link out to the hotel.
Expired block — the block's dates have passed because its event is over. Normal, and not a task.
Compass — the AI assistant running on your website, answering visitor questions.
Elements — Playeasy content embedded on your own site or a partner's. Reach, measured as impressions.

Your Hotel Partner Performance Report (Advisor Playbook)

Use this when you want a report you can share with your hoteliers — how their blocks are set up, how much traffic and business Playeasy sent them, and what your visitors are asking about lodging. For destination-wide performance, see Your Destination Performance Guide (Advisor Playbook)