Adjaba Academy — Partner Guide to Adjaba Pulse
Welcome to Adjaba Academy. This document is the starting point for partners deploying, configuring, and operating Adjaba Pulse — our in-store camera analytics product — without needing to ask us for help on every step. Read it top to bottom once, then use it as a reference.
1. What Adjaba Pulse does
Adjaba Pulse runs on an Android tablet/screen mounted near a storefront or display. It turns the device’s camera into a privacy-safe, aggregate-only audience analytics sensor — no faces, images, or identities are ever stored or transmitted.
How it works, in order:
- Face detection — on-device AI detects faces in each camera frame.
- De-duplication only — a lightweight, on-device comparison recognizes “this is still the same visitor” for up to 60 seconds, so a person isn’t double-counted while they linger. This comparison data is discarded after 60 seconds and never leaves the device.
- Attribute estimation — for each detected (de-duplicated) face, the device estimates:
- Gender and age bracket
- Sentiment — Positive / Neutral / Negative only
- Zone — which area of a 12-zone grid the face falls in, used for the heatmap
- Attention — whether the person appears to be looking at the screen
- Dwell time — how long a unique visitor was tracked
- Live dashboard overlay — the camera screen itself shows a real-time dashboard on top of the live preview: visitor count, average dwell, gender split, the zone heatmap, sentiment, and age-bracket breakdown, refreshed every 2 seconds.
- Aggregation & sync — every 60 seconds, the device publishes one aggregate snapshot (counts, percentages, heatmap, sentiment, age — no per-person data) to Adjaba’s analytics system.
The result: store owners and partners get live and historical footfall, dwell, sentiment, and heatmap analytics — built to be privacy-defensible by design (see §3).
2. Daily operator workflow
- Power on the device and log in with your Adjaba-issued credentials.
- On the setup screen, confirm your Screen ID, camera direction, orientation, and a name for this location/zone (e.g.
entrance,checkout,aisle-3). - Tap Start Camera. The app will request Camera permission if not already granted.
- The first time (and once a year after), a consent screen appears before analytics can run. The operator must confirm a physical privacy notice is posted near the camera (see §3), then choose to start with analytics on, or run the camera preview only with analytics fully off.
- The camera screen runs continuously through business hours, showing the live dashboard.
- Data syncs to the backend automatically in the background, and can also be triggered manually via a Sync button if needed.
- Review analytics on-device via the built-in dashboards, or ask your Adjaba contact for centralized reporting access.
3. Privacy & data handling
Adjaba Pulse is built around data minimization: it counts and classifies, it does not identify or store biometric records.
- Consent gate: analytics will not run unless consent has been accepted, and the notice hasn’t expired (annual re-confirmation required).
- Signage requirement: a physical privacy notice must be posted at the camera before analytics can be enabled — your Adjaba contact can provide a printable template.
- Opt-out mode: choosing “Run Without Analytics” keeps the camera preview active for operational visibility, but fully disables detection, classification, and data publishing.
- What is never stored or transmitted: face images, biometric templates, names, or any individual identifiers. The temporary data used to avoid double-counting a visitor lives only in memory for up to 60 seconds and is then discarded.
- Data retention: footfall data is kept for 30 days, heatmap summaries for 90 days, and consent/compliance records for 1 year. Detailed per-face data is never retained at all.
If you need more detail on the privacy/compliance approach for your own records, ask your Adjaba contact for the relevant documentation.
4. Day-to-day operation
- Keep it powered and connected. The device needs to stay online to sync analytics and receive updates. Wi-Fi/Ethernet should be stable and always-on.
- Mount it where it can see the area you care about — entrance, checkout counter, or a specific aisle, depending on what you’re trying to measure.
- Leave it running during business hours. Don’t force-close the app — it’s designed to run continuously.
- Sync regularly. If the device is ever reinstalled or its storage is reset, any analytics that hadn’t yet synced to the backend may be lost — regular syncing avoids this.
5. Troubleshooting
| Problem | Likely cause / fix |
|---|---|
| Can’t log in | Double-check your credentials; confirm the device has internet access |
| No screens show up after login | Your account may not have a screen registered yet — contact your Adjaba rep |
| Dashboard shows no data right after setup | Aggregates publish once per 60-second window — allow at least one full window before checking |
| Consent screen won’t let me proceed | Confirm you’ve posted the physical privacy notice and checked the signage confirmation box |
| Camera is on but “Run Without Analytics” was selected | Expected — the preview stays active for visibility, but no analytics processing happens in this mode |
| Local data seems to have disappeared after a reinstall | Sync data regularly via the Sync option to avoid this — see §4 |
6. Getting Help
If something isn’t covered here, or behaves unexpectedly, reach out to your Adjaba point of contact with:
– Your Screen ID
– What device you’re using
– What you expected to happen vs. what actually happened
This makes it much faster to diagnose than “it’s not working.”