Skip to main content

Age & Gender Recognition: Setup, Licenses & Troubleshooting

How to set up and manage age and gender recognition in Vemcount — including licenses, widget behaviour, known issues, and troubleshooting tips.

V
Written by Vemco Group

Overview

Vemcount supports demographic analytics including age group segmentation and gender recognition for compatible sensors. This article covers how to enable demographic features, manage licenses, understand widget behaviour, and troubleshoot common issues.


Supported Sensors & Compatibility

Age and gender recognition is available on select sensor models that include built-in AI/demographic processing. Not all people-counting sensors support this feature. Check with your Vemco account manager or support team to confirm whether your installed sensor model supports demographic data.

Compatible sensor types include:

  • Xovis PC2S / PC2SE (with AI module enabled)

  • TD sensors with demographic firmware

  • Select Milesight models (with exceptions — see known issues below)


Licenses for Demographic Features

Age and gender recognition requires a separate add-on license in Vemcount. The demographic license is charged per location/sensor and has an expiry date.

Requesting a Demographic License

Submit a support ticket with:

  • Location name and Vemcount location URL

  • Sensor model and ID

  • Whether you need age recognition, gender recognition, or both

  • Preferred license start date

License Expiry

If your demographic data stops appearing in Vemcount, the license may have expired. Check with support by providing your location name — support can confirm the license status and arrange renewal. Data collection resumes once the license is renewed; no historical data is lost during the lapse period.


Understanding the Age & Gender Widget

How Counts Are Calculated

  • The age widget counts each person detected and classifies them into age brackets (e.g. child, adult, senior) based on the sensor's AI model.

  • The gender widget classifies detected individuals as male or female.

  • These classifications are estimates based on visual detection — accuracy varies based on camera angle, lighting conditions, and whether the person's face/body is within the sensor's field of view.

Why the Widget Total May Differ from Visitor Count

A common reported issue is the age or gender widget showing a higher total than the overall visitor count. This can occur because:

  • The demographic sensor counts at a different point in the entrance (e.g. further inside the store) than the main people counter.

  • A person who passes through multiple times is counted multiple times by the demographic sensor.

  • The widget is aggregating counts across a different time range or zone than the visitor total widget.

If the discrepancy is significant and persistent, report it to support with a screenshot of both widgets and the time range displayed.


Known Issues

Milesight VS125-LW — Demographic Data停 Stopping

A confirmed issue has been identified where Milesight VS125-LW sensors stop delivering gender/demographic data streams. This issue is not related to firmware version and requires a backend fix by the Vemco development team. If you experience this:

  • Note the date demographic data stopped appearing.

  • Confirm other sensor models at the same site are unaffected.

  • Submit a ticket with your sensor model, ID, and the date the data stopped.

Child Count Higher than Adult Count

If your dashboard shows child counts significantly exceeding adult counts in a retail environment, this is likely a calibration or zone configuration issue. Submit a ticket with a screenshot and the affected location URL for investigation.

Age/Gender Widget Showing Zero

If the widget shows zero values:

  • Confirm the demographic license is active.

  • Check that the sensor itself is online and counting visitors normally.

  • Verify the widget is configured to the correct location and sensor.

  • If all of the above are correct, contact support — there may be a processing pipeline issue.


Staff Exclusion for Demographic Data

If staff members are being included in demographic counts and skewing the data, an exclusion zone can be configured for the area where staff typically stand (e.g. behind a counter or near a stockroom entrance). Request this via a support ticket with reference images of the store layout.

Did this answer your question?