Backend guide for understanding and documenting locations under Companies in Vemcount
Field | Value |
Suggested Intercom title | Companies – Locations |
Suggested subtitle | Learn what locations are, how they are used, and why correct location setup is important for reporting, dashboards, access and sensor data. |
Audience | Vemcount administrators, support users and internal onboarding/training. |
Article status | Draft v1.0 – ready for review and screenshots. |
What is a Location?
A Location is a physical or operational site under a company in Vemcount, such as a store, branch, shopping centre, building, entrance area or other reporting unit. Locations are used to structure visitor data, connect sensors and data sources, manage access, and create reports or dashboards for a specific site.
Locations are the foundation for site-level reporting in Vemcount. A company can contain one or many locations, depending on the customer setup. Each location normally represents the place where visitor traffic should be measured and analysed separately.
In reports and widgets, the Location source is used when the customer wants to view data for the whole location, rather than a single entrance, zone, tag or group. If a location has several entrances, the Location source normally represents the combined visitor traffic for that location.
Go to Setup / backend administration.
Open Companies.
Select the relevant company.
Open Locations from the company menu.
Important note: The exact menu wording can vary slightly depending on user permissions and backend version. If the user cannot see Locations, check their role/permissions and whether they have access to the relevant company.
Locations are used across several areas of Vemcount. They are not only a name in the company structure; they define where data belongs and how it can be accessed, reported and maintained.
Organising customer sites under the correct company.
Connecting sensors, entrances, zones and other data sources to the correct physical location.
Creating reports and dashboards for a specific store, branch, building or area.
Managing which users can access which locations.
Applying opening hours, reporting settings and operational context to a specific site.
Supporting troubleshooting, health checks and data validation for a specific location.
Providing location IDs used in integrations and API requests.
Level | Purpose | Example |
Company | The customer or account that owns the locations. | Retail chain, shopping centre, bank, museum |
Location | The physical site or reporting unit under the company. | Copenhagen Store, Branch 101, Main Mall |
Entrance | A specific entry or exit point within a location. | Main entrance, side entrance, staff entrance |
Zone | A defined internal area or custom sensor-based reporting area. | Checkout area, food court, exhibition zone |
Sensor | The device or data source that collects the visitor data. | Xovis sensor, Milesight sensor, legacy sensor |
Use case | How Locations help |
Retail stores | Each store is created as a location so the customer can compare performance across stores. |
Shopping centres | The mall, specific entrances or reporting areas can be structured so visitor traffic is reported correctly. |
Bank branches | Each branch can be handled as a separate location with local access and branch-level reporting. |
Public buildings | Libraries, museums or exhibition areas can be created as locations or zones depending on the reporting need. |
Large rollouts | Locations make it easier to track which sites are configured, active, offline, assigned to users or missing sales terminals. |
When creating reports or widgets, Location is one of the main source types. Choose Location when the customer wants to report on the complete location total. Choose Entrances when the customer needs data split by individual entry points, and choose Zones when the analysis should focus on a specific internal area.
Source type | Shows | Use when |
Location | Total visitor data for the whole location. | The customer needs the overall store/site traffic. |
Entrance | Visitor data per entrance. | The customer needs to compare individual entrances. |
Zone | Data for a defined internal area. | The customer needs behaviour or traffic analysis inside the location. |
Tags | Locations grouped by tag, usually shown as separate results per location. | The customer wants to filter or compare tagged locations. |
Groups | Combined data across grouped locations. | The customer wants a combined total for several locations. |
Locations are also important for access control. A user may have access to the full company or only to selected locations. This determines what data the user can see in reports, dashboards and widgets.
Company-level access normally gives access to all locations under the company.
Location-level access limits the user to one or more selected locations.
If a user cannot select data in reports or dashboards, check whether the user has been assigned to a company or location.
Use a naming convention that is easy to search, support and understand later. For larger customers, include a store number, branch number, city or other stable identifier where possible.
Recommended format | Example |
Store number + city/name | 101 – Copenhagen Main Store |
Branch number + branch name | 470 – Spetses Branch |
Centre/building + area | Main Mall – Food Court |
Country/region + site name | DK – Aarhus City |
Confirm that the location belongs to the correct company.
Use a clear and consistent location name.
Confirm time zone and opening hours where relevant.
Confirm that sensors, entrances and zones are connected to the correct location.
Confirm whether sales data or sales terminals should be connected to the location.
Assign relevant users to the company or location.
Add useful tags, custom fields or notes if used internally.
Verify data in a report or dashboard after setup.
Issue | What to check |
User cannot see a location | Check whether the user has been assigned to the company or the specific location, and whether their role allows the required access. |
Report shows no data | Check that the selected source is correct, the sensor/data source is active, and that the reporting period and opening hours are valid. |
Wrong total for the location | Check whether entrances, zones or sensors are correctly assigned and whether the correct count source is marked as entrance where relevant. |
Location missing sales data | Check whether sales terminal/integration mapping has been configured for the location. |
API request returns wrong/no data | Check that the location ID is correct and that the user/API token has access to the location. |
Locations are used to represent the physical sites or operational areas that belong to a company in Vemcount. A location is usually a store, branch, building, mall area or another unit that the customer wants to report on separately.
When creating reports and dashboards, choose Location as the source type when you want to view data for the entire location. If you need to analyse individual entrances or internal areas, use Entrances or Zones instead.
Locations are also used for user access. Users can be assigned access to the full company or to specific locations only, which determines what data they can see and work with.
Important note: Do not create unnecessary locations if the customer only needs one combined reporting unit. Too many overlapping locations can make reporting, access management and troubleshooting more complex. Use entrances, zones, tags or groups when those are a better fit for the reporting need.