Xovis, joined to everything else.
DataGlue marries Xovis data with your other systems in one living model. Every number shows its formula and its records.
Xovis: A maker of 3D sensors for people counting, queue and flow analytics.
- IN
- NO NATIVE CONNECTOR · WEBHOOK
Bring Xovis and one decision to the call. Tool names are enough; no access needed.
Trusted by
- WebhookIN
- REST APIIN
- File exportIN
What comes in from Xovis. Counts, queue lengths and flow by zone come in. Sensors send counts, never images.
- IN
Webhook
Where Xovis supports event webhooks, your system sends recorded counts, presence or plate events to a DataGlue inbound URL. The fields and identifiers are agreed in the build. No footage or face images are imported.
- IN
REST API
A sync you run reads the recorded events available from Xovis and sends them to our REST API. The fields, identifiers and schedule are agreed in the build. No footage or face images are imported.
- IN
File export
Recorded count, presence or plate exports from Xovis are imported as files, with their source ids and timestamps. The available fields are checked in the build. No footage or face images are imported.
There is no native Xovis connector today; the routes above are how it joins. Connections are agreed in the build. We check the source data, consent and identifiers before promising a linked journey. Xovis is a trademark of its owner; this page implies no partnership or endorsement.
Describe the outcome. DataGlue works it out and shows you the formula.
- 01
Describe the outcome you want in plain words, such as "Queues that cost sales".
- 02
DataGlue works it out from the definitions of your data sources, Xovis included, and shows the formula in concise English.
- 03
Send it on: to reports, BI tools, any destination, or the AI tools your team already uses.
- EXAMPLE OUTCOME 01
Queues that cost sales
THE FORMULASales per visitor in hours when queues ran long, against hours when they did not.
- EXAMPLE OUTCOME 02
Floor flow by layout
THE FORMULAVisitors through each zone before and after a layout change.
Tags about people come only from signals your systems already record, under your privacy policy and local law. Sensitive tags, such as gender or income estimates, are marked as estimates and can be switched off. Records link only where recorded identifiers support the match. People are never identified from faces.
Want one of these from your Xovis data? We map the route and the first outcome on the call.
Book a CallBring Xovis and one decision. We'll map the route and the first outcome on the call.
The call scopes fit. The build is a separate engagement, priced before work begins.