Sales rep tracking that detects spoofed GPS instead of trusting it
Every system on the market reads the phone's coordinates. The problem is that those coordinates can be faked with a free app from the store. MedicalRep checks whether a spoofing service was active at the moment the visit was logged — and keeps the evidence.
- Fake-GPS detection
- Live map
- Audit log
- Offline caching
What makes tracking trustworthy rather than decorative
Location-spoofing app detection
The app scans installed packages and separately checks whether the mock-location service was active while the visit was logged. Those are different signals: the first puts a user on a review list, the second flags the visit itself.
Visit distance verification
Captured coordinates are compared against the customer's registered address within a configurable radius (100 m by default). A wide gap raises a warning before the visit is accepted — not a week later in a report.
An auditable log
Every attempt is stored with its timestamp. The judgement stays with the manager — a pattern across ten visits matters far more than a single incident that may have an innocent explanation.
Works where coverage is poor
Location is captured and stored locally even with no connection, then uploaded with the visit when signal returns. A network drop becomes neither an excuse nor a hole in the data.
Is this product built for you?
A good fit if you are
- A manager who needs proof a visit happened, not the rep's word for it
- A pharma or medical device company that has already had doubts about fabricated visits
- A field team spread across territories too wide to supervise in person
- A company that wants tracking from the phone app, with no GPS hardware or extra SIMs
- Management that wants an audit log to fall back on when there is a dispute
Not the right choice if
- You want 24-hour tracking outside the work context — the system deliberately does not do that
- You need vehicle or fleet tracking with hardware installed in the car
- You want a system that issues penalties automatically — we supply evidence, the judgement stays yours
Team size is not a barrier: the free plan runs with one active user, Team covers up to 8, and Unlimited has no user cap.
Why conventional tracking stopped being enough
Almost every rep-tracking system does the same thing: it asks the phone where it is, and records the answer. The problem is that the operating system itself provides an official way to lie — the mock location setting in Android's developer options, originally built for testing apps.
The store carries dozens of free apps that use it. The user drops a pin on a map, and that becomes their location as far as every other app on the device is concerned. A rep sitting in a coffee shop can log a visit "from inside" a clinic forty kilometres away, and the system will believe them.
This is not hypothetical. The market knows it — we found one competitor listing the question verbatim in their own FAQ: "how does the system prevent fake visits?" — but the answer was generic, and we found no shipped capability on any of the fifteen pages reviewed in August 2026.
How the detection actually works
Detection runs as two separate layers, and the distinction matters:
Layer one — device scan
The app scans installed packages for known location-spoofing tools. Mere presence is not guilt — it may be installed for gaming — so the user goes onto a review list without being blocked or penalised. This scan is why the app requests the QUERY_ALL_PACKAGES permission, which is documented openly in the privacy policy.
Layer two — submission scan
This is the decisive one. If the mock-location service was actually active while a visit was being logged, the visit reaches the dashboard clearly flagged with an exact timestamp. Here the innocent explanations largely run out: the app was not merely installed, it was running at the moment a work visit was recorded.
Keeping the layers separate is deliberate. Conflating them produces false accusations, and a false accusation destroys team trust faster than the spoofing ever did.
What the manager sees
From the web dashboard a manager gets four layers of information:
- A live map of the team's movement through the day, with logged visit pins.
- A real-time activity feed — each visit appears within seconds of being logged.
- The suspicious-users list from layer one, for a calm weekly review.
- The flagged visits from layer two, with the full audit trail.
The practical recommendation: review the list once a week and look for a pattern, not an incident. One flagged visit may have a technical cause. Seven flagged visits in a fortnight is a conversation that needs to happen.
Tracking and privacy — where is the line?
Reps ask this, legitimately, and we would rather answer it than dodge it.
MedicalRep captures location in a work context: the start and end of a visit, and the working-day movement that appears on the manager's map. This is not 24-hour surveillance of an employee's life, and the stated purpose — verifying that visit data is real — is documented in the privacy policy and terms of service.
Our advice to management: explain to the team what is collected and why before rollout, not after the first flagged visit. An honest rep loses nothing to an accurate system — they gain, because their effort becomes visible instead of being averaged in with someone logging visits from a café.
Location accuracy in the real field
No GPS system is 100% accurate, and any vendor claiming otherwise is selling you a fiction. The real problems you will meet:
- Inside hospitals and concrete buildings, satellite signal weakens and position can drift by tens of metres. This is why the verification radius is configurable, and why a mismatch raises a warning rather than a rejection.
- In dense urban areas, signal bounces off buildings and precision drops.
- "While in use" location permission stops capture when the app is backgrounded — which is why it must be set to "Always".
The design handles this by treating a mismatch as information for a human to review, not an automated verdict. The goal is honest data, not a penalty system.
How to evaluate any tracking system before buying
Five questions separate a serious system from a decorative one. Ask them of any vendor, including us:
- Do you detect mock location being active during submission? If the answer is "we read GPS coordinates", that is not an answer to the question.
- What is kept in the audit log, and for how long?
- What happens when the network drops — is the visit lost or queued?
- Is the price published? Fifteen out of fifteen sites we reviewed do not publish it.
- Can I export my data when I leave?
The fastest practical test: get a trial account, install a spoofing app on a test device, and log a visit. What appears on the dashboard tells you everything. Our free-forever plan makes that test cost nothing.
What actually differs from the rest of the market?
| Criterion | Common in this market | MedicalRep |
|---|---|---|
| Fake-GPS / spoofing detection | No | Yes — mock-location detection with an audit log |
| Visit location verification | Coordinates read only | Yes — compared to the customer address within a configurable radius |
| Pharma-native data model | Usually FMCG / distribution | Yes — doctors, pharmacies, hospitals, samples, detail aids |
| Works offline | Rarely | Yes — offline-first with automatic sync |
| Pricing published on the site | No — "contact us for a quote" | Yes — 750 / 3,500 / 6,000 EGP per month |
| Free-forever plan | No — a 14 or 15-day trial | Yes — one company, one active user, no card |
| Native Arabic and English | Arabic only, or machine translation | Yes — both written natively |
| AI agents | No | Yes — visit planning, data & decision, auto-reporting |
The middle column describes what we actually found when reviewing 15 competing product pages in the Arabic market on 8 August 2026. Sites change — verify for yourself before you decide.
Clear published pricing — no "contact us to find out"
Start free forever with one company and one active user, no credit card. Upgrade only when the team grows.
One company · one active user
Per additional seat
Up to 8 users · full AI agents
Unlimited users
Questions about tracking, privacy and location accuracy
How does the system detect fake-GPS apps?
Does the system block a rep if a spoofing app is found?
How accurate is location inside hospitals?
Does the system track reps outside working hours?
What happens to the location if the internet drops mid-visit?
Do I need tracking hardware or extra SIM cards?
How much does rep tracking cost?
Can the visit distance radius be configured?
Related solutions and courses
Test the spoofing detection yourself
Install a location-spoofing app on a test device, log a visit, and watch it arrive flagged on the dashboard. It is the fastest way to evaluate the system.