Guest360 Overview

Note: Guest360 is currently available to select brands as part of an early access program. Contact your Punchh representative to request access or ask about your brand's eligibility.

Guest360 is PAR's Customer Data Platform (CDP), built natively within the Engagement Cloud. It gives you a complete view of your guest base, including guests who have never signed up for loyalty.

Most restaurant analytics tools only have visibility into the roughly 20% of guests who join a loyalty program. The other 80% pay and leave without ever being identified. Guest360 changes that by connecting POS transaction data, online ordering data, and payment information to build guest profiles for everyone, including guests who have never registered for anything.

Guest360 does not replace Punchh. Punchh manages your loyalty program; Guest360 extends your visibility to the full guest base and unifies the picture. Both live side by side in the Engagement Cloud.

To access Guest360, navigate to your Punchh Platform > Guests > All Guest Profiles > Guest360 Console

How It Works

Guest360 follows a four-step process for every guest interaction:

  1. Recognize: Identify the guest from the transaction
  2. Connect: Link their activity across channels and visits into one profile
  3. Understand: Build a complete view of their behavior, value, and lifecycle stage
  4. Activate: Act on that understanding through campaigns, segments, and journeys in Punchh

Profile Stitching

Profile Stitching connects individual transactions to guest profiles. When a guest orders or pays, Guest360 matches the transaction to an existing profile using exact, deterministic signals:

  • Email address
  • Phone number
  • Credit card matching via Payment Account Reference Number (PARN)

Guest360 never uses probabilistic guessing, so profiles are never incorrectly merged. Credit card matching via PARN is the strongest signal. It links tokenized cards, digital wallets, and reissued cards to a single payment account, so a guest who uses different cards across visits still resolves to one profile.

Profiles update as new activity comes in and get more accurate over time.

Note: In-store guest matching requires either PAR Pay (for PARN-based matching) or coordination with your payment provider to supply the required payment data. If your brand does not use PAR Pay, contact your Punchh representative to discuss your options.

Connected Data

Guest profiles grow richer as you connect more data sources. Each connection improves matching accuracy and adds profile detail:

  • Loyalty: identifies enrolled guests and adds tier, points, and redemption history
  • POS: captures transaction history and in-store spend for all guests
  • Online ordering: adds authenticated email and phone, which helps match the same guest across channels
  • Payments: links in-store card activity to profiles and adds spend frequency

Features

Dashboard Analytics

The Dashboard gives you a view of your full guest base: loyalty and non-loyalty guests together. The dashboard displays 12 metrics that refresh daily. You can filter any Dashboard view by a segment you have created, scoping all metrics to a specific guest audience.

Note: After Guest360 connects to your data, your Loyalty Penetration metric may appear lower than you expect. This is not a decrease. It reflects the fact that Guest360 has expanded your total guest count by identifying non-loyalty guests, so the denominator is larger.

Guest Profiles

The guest profile view gives you a detailed record for any identified guest in your database. Each profile includes:

  • Transaction history across channels (in-store and online ordering)
  • Visit frequency and lifecycle stage
  • Loyalty program status and points balance (for enrolled guests)
  • NPS survey responses and scores (when NPS data has been imported)
  • Demographic attributes (when demographic enrichment data has been imported)

Profiles get richer as you connect more data sources. A guest who starts as a POS-only record gains an email and phone number once online ordering is connected, and card-linking history once payments are added.

Segmentation

Guest360's Segment Builder runs on Punchh's segmentation service, so the available filters and rules are the same ones you use in Punchh today. Segments you create in Guest360 are available in Punchh for campaign execution right away, and you can use any segment as an Dashboard filter.

PAR Intelligence and Guest360 Coach

Guest360 Coach is the built-in AI analytics assistant in Guest360. You can ask natural-language questions and get answers without building a manual report. For example: "Which guests visited 3 or more times last month but haven't returned in 30 days?"

Note: Guest360 Coach currently queries your Punchh loyalty data. Expanded querying across all Guest360 guest data is planned for a future release.

Coming soon: PAR Intelligence will extend Guest360's AI capabilities across your full guest base, surfacing the segments growing fastest, recommending the next audience to activate, and suggesting campaigns based on behavioral signals. The more data sources you connect, the better the recommendations get.

What You Need to Get Started

Before using Guest360, confirm the following are in place. Contact your Punchh representative if you are unsure about any of these.

  • An active Punchh account
  • POS transaction data is connected to the Engagement Cloud
  • Online ordering data is accessible (via Olo webhook or PAR Ordering)
  • Payment data is available (via PAR Pay or through your payment provider)

User Roles

Guest360 includes three user roles. Your Punchh representative can help assign roles during onboarding.

Role Access Level
Admin Full access to all platform features, including data sources, users, and settings
Marketer Access to analytics, guest profiles, segmentation, and data export
Viewer Read-only access to analytics and guest profiles

Limitations

  • Data refreshes daily. New transactions may take up to 24 hours to appear.
  • Guest profiles are built from transaction-derived data by default. Third-party demographic attributes require a separate import.
  • In-store guest matching requires PAR Pay or coordination with your payment provider.
  • Guest360 is optimized for desktop. Mobile and tablet views are not fully supported.