PIING
Reading Analytics and reportingCheck-ins and channels
Analytics and reporting
- Analytics overview
- Check-ins and channels
- Geographic reporting
- Card and pass analytics
In this guide
- One visit ledger
- Customer-facing recognition routes
- What happens after an accepted check-in
- Why the source matters
- Next steps
Search or browse documentation
Analytics and reporting 2 / 4
Check-ins and channels
How Piing records one recognised visit across kiosks, physical cards, Wallet passes, scan-in points, Shopify POS and authorised system routes.
A check-in is Piing's record of a recognised store visit. It connects a known customer, a location, a timestamp and the route that recognised them. That visit can then feed analytics, customer metafields and the destinations you have explicitly configured.
One visit ledger
Every route resolves an identifier to a customer, applies the relevant safety checks and writes the accepted visit once. A 60-second duplicate guard stops an immediate repeat from being counted as a second visit. Other store cooldowns or daily controls can apply where configured.
The source stays on the record, so reports and operations screens can distinguish a physical card, Apple Wallet, Google Wallet, kiosk, scan-in point, Shopify POS, API, manual or simulated visit.
Customer-facing recognition routes
- Kiosk camera. A returning customer presents the QR on an Apple Wallet or Google Wallet pass to the front camera of a paired tablet. A new customer can scan the kiosk's join QR on their own phone.
- Physical NFC card. The customer taps a linked card on a compatible reader. This works independently of Apple Wallet or Google Wallet.
- Apple Wallet. The pass QR can be scanned by the kiosk or at the till. An iPhone can tap an Apple VAS reader only after the merchant has the required Apple entitlement and NFC configuration.
- Google Wallet. Piing's current Google Wallet pass uses QR for recognition. Do not position it as phone-to-reader NFC or Smart Tap.
- Scan-in point. A customer scans a store-specific printed QR, or opens the same URL from a compatible NFC tag, on their own phone.
- Shopify POS. Staff can use the Piing tile at a mapped Shopify POS location.
Piing also accepts authorised API and manual operations. Test and simulated check-ins use their own labels so they can be separated from live customer activity.
What happens after an accepted check-in
The visit appears in Hardware & check-ins and the relevant analytics views. Depending on your saved configuration, Piing can also:
- update Piing-owned customer metafields such as last check-in, total visits and visits in the last 30 days;
- refresh Apple Wallet and Google Wallet values;
- show customer context to staff in Shopify POS;
- emit a typed Piing event to a connected CRM, automation or webhook route;
- relay a visit reward to a supported loyalty provider when that reward route is enabled.
These are configured outcomes, not automatic promises for every account. A connection must be active and the relevant template, field or reward rule must be enabled.
Why the source matters
Source reporting shows how each store actually recognises customers. One location may lead with a kiosk by the entrance, another may use physical cards at a reader, while a pop-up may rely on scan-in signage. The same customer and event model means those routes can be mixed without creating separate customer records.
Next steps
Related guides
Was this guide helpful?
Next guide in Analytics and reporting
Geographic reporting
Read the fixed 90-day country and city report, its physical-versus-digital holder table and its Protected Customer Data coverage.
Still need a hand? Contact us