PIING
Reading Analytics and reportingAnalytics overview
Analytics and reporting
- Analytics overview
- Check-ins and channels
- Geographic reporting
- Card and pass analytics
In this guide
- What the overview answers
- The attribution windows
- The focused reports
- What sits behind the numbers
- Next steps
Search or browse documentation
Analytics and reporting 1 / 4
Analytics overview
Read Piing's headline visit, attribution, store, Wallet and delivery reports, and understand the window behind each measure.
Piing analytics connects recognised store visits with the activity that follows them. It shows whether visits are growing, which locations are working, which customers return and which paid orders followed a check-in.
Open Analytics in Piing. The overview can be filtered to one store and to the last 7, 30 or 90 days.
What the overview answers
The page is organised around retail questions rather than a wall of counters:
- Are tap-ins growing? Total check-ins, distinct recognised customers, today's activity and the change against the previous equivalent period.
- Which orders followed a recognised visit? Paid orders and revenue that followed the same customer's most recent check-in within seven days. Recognised check-ins do not count everyone who enters the store.
- Which stores are working? A ranked view of visits and unique visitors by location.
- Are tap-ins turning into orders? The share of recognised visitors who purchased within seven days, plus the share of paid orders attached to a recent visit.
- Do recognised members spend differently? A comparison between customers who checked in and those who did not, where enough order data is available.
- Which regulars have gone quiet? Customers with a history of visits whose most recent check-in is now outside the active window.
- Are passes and connected routes healthy? New Wallet passes, Wallet message delivery and integration delivery health for the selected period.
Return rate means the share of distinct recognised customers with at least two visits inside the selected period. It is not shown as zero when there is not enough activity to calculate it.
The attribution windows
The overview and Stores report provide fixed 24-hour and seven-day views so locations can be compared on the same basis. The headline revenue and purchase conversion on the overview use seven days.
The dedicated Attribution report uses your configured store attribution window. It is seven days by default and can be set from 1 to 60 days under attribution settings.
Piing connects an order to the same customer's most recent check-in before that order, provided it falls inside the relevant window. This is directional attribution. It shows that the purchase followed a recognised visit, not that the visit alone caused the sale.
If a customer checks in but does not purchase inside your no-purchase window, Piing can emit piing.checkin.no_purchase. Route that event to a supported CRM or webhook for a considerate follow-up, such as a store-specific reminder or offer. The event is only useful when that destination and journey have been configured.
The focused reports
- Attribution shows the orders and revenue linked to recognised visits using your configured window.
- Stores compares visits, unique visitors, paid orders, revenue and after-check-in performance by location.
- Geography groups recent tap-ins and pass holders by the city and country on their Shopify customer address.
- Push reports Apple Wallet and Google Wallet message delivery.
- Cohorts follows groups of recognised customers over time.
- Integrations shows deliveries to configured destinations, including successful, retrying and failed routes.
What sits behind the numbers
Every accepted check-in enters the same visit ledger, whether it came from a kiosk camera, a physical NFC card, an Apple Wallet pass, a scan-in point, Shopify POS, an API route or an authorised manual flow. Test and simulated visits keep their own source labels.
The reports use the customer, store, visit, pass and order data required for each view. Geography reads Shopify default-address data on demand and aggregates it in memory; it does not persist each customer's city or country in Piing. Availability still depends on Shopify Protected Customer Data approval and on the customer having an address on file. Read more on the security page.
Next steps
Related guides
Was this guide helpful?
Next guide in Analytics and reporting
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.
Still need a hand? Contact us