The issue on site
Visitor reports are usually kept per branch. A customer visiting three branches counts as three new visitors; the 'new customer' rate inflates, loyalty programmes miss real behaviour and the same person receives a campaign three times.
Check these first
- 01
Do your reports separate 'unique guest' from 'visit'?
- 02
Can you see on one screen which branches a guest visits and how often?
- 03
Is there a rule preventing duplicate campaign messages to the same person?
- 04
Is marketing consent stored independently of location?
HotSpot / LogIQ approach
With MintyRoaming, HotSpot gathers each guest into one organisation-wide profile. Every visit is added with location, date and duration. Analytics show unique guests, return rate, cross-branch movement and first/last visit per location and in total. Marketing consent is collected once and managed as valid across all locations.
Guest and team outcomes
A true returning-customer rate, an answer to 'which other branches does this guest visit?', and campaigns without duplicates.
Frequently asked question
Do branch managers see other branches' guest data?
Access is role-based. Headquarters can see all locations while a branch manager sees only their own.
Is recognition personal data processing?
Yes. The privacy notice should clearly state the purpose and duration of cross-location recognition. This is not legal advice.
This content supports technical assessment, not legal advice. Verify scope against product, version and institutional policies.