DataGlue
Xovis integration

Xovis, joined to everything else.

DataGlue joins what Xovis records with your other systems, in one view of each customer. Every count shows how it was worked out, and opens to its records.

Xovis: A maker of 3D sensors for people counting, queue and flow analytics.

  • NO NATIVE CONNECTOR · WEBHOOK

Bring Xovis and one decision to the call. Tool names are enough; no access needed.

Trusted by

  • Ticketek
  • me&u
  • InvestorKit
  • Team Global Express
FIG. 01 · HOW XOVIS CONNECTS
Xovis
THE GLUEONE VIEW
SIGNED WEBHOOK · OPEN ROUTE
  • Webhook
  • REST API
  • File export
HOW IT CONNECTS

What comes in from Xovis. Counts, queue lengths and flow by zone come in. Sensors send counts, never images.

  1. 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.

  2. REST API

    A scheduled job 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.

  3. 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. Deliver results by signed webhook. Read them through our API, ask from an AI assistant that supports MCP, or export on request. Connections are agreed in the build. Before we promise a joined-up journey, we check what the source records, what consent covers and which details link people. Xovis is a trademark of its owner; this page implies no partnership or endorsement.

WHAT DATAGLUE DOES WITH IT

Name the result you want. DataGlue shows how it counts, in plain English.

  1. 01

    With Workspace AI on, describe the result you want in plain English. Without it, build the outcome step by step.

  2. 02

    DataGlue drafts the rule from what each field in your data means, Xovis included, and shows how it counts.

  3. 03

    Use the result in your tools through the open route.

  • EXAMPLE OUTCOME 01

    Long queues

    HOW IT COUNTS

    Queue alert recorded at least 3 times in 1 day, at the same site.

  • EXAMPLE OUTCOME 02

    Zone entries

    HOW IT COUNTS

    Each zone entry Xovis records, at the same site.

Examples only. Which ones your data supports is checked with you in the working session.

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 Call
START WITH ONE DECISION

Bring Xovis and one decision. We'll map the route and the first outcome on the call.

The call is about fit. Any build is a separate engagement, priced before work begins.