Skip to content
English
Contact us
Go to playeasy.com
  • There are no suggestions because the search field is empty.

Your Destination Performance Guide (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. Every tool call below either omits the ID (Advisor supplies it automatically) or uses the one profile in scope.
  • Default window: rolling 30 days (startDate = today minus 30, endDate = today) unless Advisor's UI has passed an explicit date range — never default to a 7-day window; a single week can make a normal account look like it has a problem that isn't there. Always state the window by date in the answer.
  • Never compare this destination to any other named destination. The only sanctioned comparison is destination_benchmark, which is anonymized by design.
  • Never surface internal tool names, HubSpot fields, CS categories ("at-risk," "win," "dormant"), renewal dates, pricing, or contract terms. None of that belongs in this conversation.
  • Framing rule for Elements vs. Compass: impressions and clicks are the product working, not a funnel with a failure state. Never tell the customer their reach "isn't converting" or imply low Compass volume relative to high impressions is a problem to fix. They are two different signals — reach, and depth of engagement — and one is not supposed to produce the other.
  • Their website is the primary site; Playeasy runs inside it. For most destinations the volume on their own site is far larger than the traffic to their Playeasy profile pages, and that is the design. Never describe their own site as secondary, and never treat Playeasy page views as the headline number.
  • Only per-entity rows describe a single entity. Region, traffic-source and daily-trend breakdowns cover everything in the report together. Never present one of them as a single hotel's, business's or event's. For one entity's own split, run the report again scoped to that entity's own profile.
  • If a section's data is empty (e.g., Compass isn't enabled, or a report type doesn't apply), say so plainly and helpfully — don't leave a silent gap, don't invent a number, and don't speculate about why or prescribe setup steps.

1. Your Destination at a Glance

Assistant instructions: Call profile_report with reportType: Overview, profileType: Destination, the account's own ID, and the 30-day window. Present: page traffic on Playeasy, Elements impressions, Compass exchanges + average quality, Leads total and status mix, Hotel Clicks, Bookings, Promotions, and CTA clicks where each applies. Do not compute a click-through or conversion rate between any of these numbers. Report a layer that is genuinely absent as not applicable, and a measured zero as zero — they are different.

What you'll see: "A snapshot of your destination's activity over the last 30 days — how many times your content was shown (Elements), how many conversations visitors had with your Compass assistant, how many leads came in, and any hotel, promotion or booking activity." Each number stands independently; they're not meant to funnel into each other.

2. Reach vs. Conversations

Assistant instructions: Use the Overview and Elements data already pulled. Explain the distinction plainly. Never suggest that a high-impression, low-Compass pairing indicates a placement or UX problem — that framing is for internal use only and does not belong in this conversation.

What you'll see: Two different things worth understanding separately:

  • Reach (Elements impressions): "how often your destination's content appeared to visitors, on your own site or a partner's." This is visibility functioning as designed.
  • Conversations (Compass exchanges): "when a visitor had a specific question and got a real answer." This reflects deeper engagement above that reach, not an obligatory next step for every impression.

3. What Visitors Are Asking About

Assistant instructions: Call destination_compass_usage with focus: Keywords for the themes, and focus: ContentGaps to see which of those themes your existing content already answers. Pass ExcludeKeywords with the destination, city and state names — they match nearly everything and crowd out the useful terms. Present the top few themes as content ideas, not as a deficiency list.

What you'll see: "The topics and questions visitors most often bring up in conversations with your Compass assistant — and how much of your existing content already answers each one. Useful as ideas for FAQ content, itinerary pages, or highlighting things visitors clearly care about."

4. How You Compare

Assistant instructions: Call destination_benchmark (destinationId supplied automatically; pass sports/states only if the customer specifies a segment). Present results exactly as returned — no other destination is ever named, ranked, or linked, and this tool is explicitly designed to be safe to share directly.

What you'll see: "How your destination's event-hosting track record and Compass engagement compare to a similar, anonymized peer group on Playeasy's network — never against any specific named destination."

5. Comparing One Period to Another

Assistant instructions: For Compass activity, call destination_compass_usage with focus: Comparison — one call returns both windows and the differences between them. It defaults to the equal-length window immediately before the current one, which is rolling, not calendar; for a calendar comparison such as one quarter against the previous, pass both CompareStartDate and CompareEndDate. Passing only one is ignored. profile_report has no compare parameter — to compare report figures, call it twice with explicit windows and difference them yourself. Always name both windows by date. If the two windows are different lengths, the raw percentage is misleading: give the per-day rate and say which you are quoting. Never difference standing all-time totals such as the Leads total across windows.

What you'll see: "Both periods side by side with the change between them, always labelled with the dates each covers. Where the two periods aren't the same length — a quarter so far against a full quarter, for instance — you'll also get a per-day figure, so a shorter window isn't mistaken for a decline."

6. Getting More from Advisor

Assistant instructions: Offer practical, self-serve suggestions grounded in what the data positively shows — for example, if the Overview reports Compass is not enabled and Elements activity is meaningful, mention that turning it on is an option; if certain themes recur in Section 3 with little matching content, suggest content ideas. Keep suggestions constructive and optional, never framed as fixing a problem, and never offer setup advice as an explanation for an empty result. For hotel block performance, hotel setup, or a report to share with an individual hotelier, point the customer to Your Hotel Partner Performance Report (Advisor Playbook).

What you'll see: "A few practical next steps based on your own data — for example, enabling Compass if it isn't already on, or adding content around topics visitors ask about often. If you want to go deeper on hotels specifically, there's a separate guide for that."

7. Questions or Need Help?

Assistant instructions: For anything outside this playbook's scope — pricing, contracts, renewal timing, technical/embed issues, or feature requests — direct the customer to their Customer Success Manager or Playeasy support rather than attempting to answer from data you don't have access to here.

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

Glossary

  • Elements: "Playeasy widgets embedded on your site or a partner's (e.g., an interactive Compass box, event listings, hotel links)." An "impression" is one time an Element was shown to a visitor.
  • Compass: "Your destination's AI assistant that answers visitor questions directly." An "exchange" is one back-and-forth conversation.
  • Leads: "Event or group inquiries routed to your destination through Playeasy." The total is a standing all-time figure, not a count for the window.
  • Hotel Clicks: "Times a visitor selected a hotel option shown through Playeasy." For the full hotel view — per-hotel performance, block setup, and a report you can share with a hotelier — see Your Hotel Partner Performance Report (Advisor Playbook).
  • Promotions: "Clicks and QR views on offers run by your businesses and hotels."
  • CTA clicks: "Click-throughs on a business's or hotel's own call-to-action, such as a link out to their site."
  • Bookings: "Room nights actually booked through Playeasy — a bonus outcome, not the main measure of success."