The “Computation method” shows the algorithm selected to interpret the Wi-Fi probes captured by the BlueZoo sensors. There are five computation methods:
- Baseline: By-default computation method with no gain applied. Signal power is the only variable for the inner zone limit.
- Juno: Optimized for visit count in environments where a good number of devices are connected to WiFi (e.g. office spaces).
- Montego: Optimized for visitor counts (“real-time occupancy”) in residential locations.
- Karpov: Optimized for visit count in environments where most of the mobile devices are not connected to WiFi (e.g. streets).
- Molokai: This computation method takes into account the time spent by the device within the area and discards the count of the ones that did not reach a minimum time threshold. This computation method is not compatible with the use of unique visitor metrics (e.g. Unique Visitor, Recurrence, Flow, Convert).
The inner power defines the radius of the inner detection zone in decibels. Recognize that building materials (glass, cement, metal, concrete, etc.) impact detection range.
- The highest power value is -40 decibels (listed in the app as “40”) which corresponds to about 4m (12ft) from the sensor.
- A mid-power setting of -75 decibels (listed in the app as “75”) represents about 25m (75ft).
- The lowest power value is -120 decibels (listed in the app as “120”), which corresponds to about 100m (300ft) in outdoor environments.
By default, the outer perimeter is set to -120 decibels, but can be reduced (e.g. in order to measure proper “window conversion”).
The gain is the final adjustment made to reflect the ratio of mobile devices to people:
- the “Cumulative gain” is the adjustment made to the Visit count
- the “Real-time gain” is the adjustment made to Visitor count, also known as momentary count.
Article is closed for comments.