Guest360 Overview

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. Guest360 matches on four exact signals only:

• Punchh identity
• Email
• Phone
• Payment token (PARN from PAR Pay)

When a guest orders or pays, Guest360 looks up those signals and either creates a profile, attaches a new identifier to an existing one, or merges an anonymous profile into a known Punchh member. Two Punchh members are never merged, even if they share a card. When the match is ambiguous (three or more profiles), they stay separate.

• PARN is the signal that discovers in-store guests who never enroll. It is stable across tokenized cards, wallets, and reissued cards on the same payment account. It does not mean two different cards are the same person.
• In-store discovery of non-loyalty guests requires PAR Pay (PARN). Without it, Guest360 can still unify Punchh members and online-ordering identities (email/phone), but it will not recognize in-store payers who never enroll.

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 membership status, points balance, and offers redeemed (membership level only if the brand actually has Punchh levels).
• 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 shows loyalty and non-loyalty guests together. Eleven metrics refresh from the nightly data pipeline. You can customize which cards appear. Filter by date range and compare period. Filtering the Dashboard by a Guest360 segment is not available yet.

Guest Profiles

The guest profile view gives you a detailed record for any identified guest in your database. Each profile includes transaction and visit activity, order frequency and lifecycle stage, lifetime value, loyalty status and points (for enrolled guests), identity (merged-profile count), and messaging consent. An activity timeline shows orders and loyalty events.

Profiles get richer as more identifiers attach (for example an email from online ordering on a POS-only guest). Third-party NPS and demographic attributes are not in Guest360 today.

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.

PAR Intelligence

When PAR Intelligence is enabled for a brand, Intelligence appears in the Guest360 header. You can ask natural-language questions and get answers without building a report. It is Punchh’s assistant, not a query layer over the full Guest360 guest graph. Expanding that to all Guest360 guests is not available yet.

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 (you launch Guest360 from Punchh)
• POS transaction data flowing into the Engagement Cloud / data pipeline
• Online ordering connected if you want email/phone from those orders (Olo)
• PAR Pay, if you want in-store recognition of guests who never enroll

Data connections are set up during onboarding, not by the brand through a Data Sources screen.

User Roles

Guest360 uses your Punchh admin role. Super admins see every brand and Cockpit. Major admins and business owners are limited to their brand. Users and roles are assigned in Punchh, not in Guest360.

Limitations

• Data refreshes nightly. New transactions may not be visible until the next business day.
• 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.