Confirm a delivery
location with a link.
Text the customer a link before the courier rolls. They see a clear notice, tap "Share my location", and approve their phone's own "Allow location access" prompt. Dispatch gets the exact drop-off coordinates, an accuracy radius in meters, a Google Maps pin, and a timestamp. They can always decline — and only approximate IP location is used.
PRO feature · consent required every time · for last-mile, food delivery, courier dispatch & trades arrival — never covert tracking
The part that makes it honest
How the confirmation works
Two affirmative taps stand between your link and any drop-off coordinate. There is no silent path to a customer's precise location — by design, and by the laws of the browser.
1. Customer opens the link
They see a plain-language screen: this link is asking for your location, who sent it, and why — to confirm your delivery address. No coordinates have left their phone yet.
2. They tap "Share my location"
Only if they agree. This triggers the phone's own native "Allow location access" prompt — controlled by the OS, not by us. Or they tap "Continue without sharing".
3. Dispatch gets the pin
After they approve, the device returns the precise drop-off lat/lng + accuracy radius. We reverse-geocode it, pin it on a map, and stamp the time. If they declined, you get approximate IP location instead.
Decline is a real option. "Continue without sharing", dismissing the prompt, or a pre-blocked site all let the customer carry on — you simply fall back to approximate IP location (~50 km) or the typed address. No dark patterns, no nagging.
Nothing is hidden from the customer
Before any coordinate leaves their phone, the customer sees this consent screen. It names you, explains what's requested, offers a one-tap decline, and carries a report button. There is no silent capture and no fine print — the prompt is the product.
- Our consent notice fires first — before the browser prompt
- The phone's native Allow prompt is OS-controlled and unfakeable
- "Continue without sharing" is right there, every time
- A report button lets any recipient flag misuse instantly
This link is asking for your location
The person who created this link wants your precise location. It's being used to confirm your delivery drop-off so the courier reaches the right spot. You can decline.
Visual mock-up of the notice that precedes the phone's own Allow prompt. This is the consent screen every visitor sees — nothing is hidden.
Pinpoint Links are a PRO feature. Start free and upgrade when you need meter-accurate, consent-gated delivery confirmation.
What dispatch captures on a confirmed drop-off
When the customer confirms, this is the full record — precise, mapped, timestamped, and exportable per order.
Precise drop-off lat / lng
Device-reported coordinates, typically accurate to 5–50 m outdoors.
Accuracy radius (meters)
The confidence radius the device reports — know a tight pin from one worth a call.
Reverse-geocoded address
Street / city / region / country resolved from the precise coordinates.
Navigable Maps pin
An embedded pin the courier taps through to maps.google.com for directions.
Confirmation timestamp
When the customer confirmed — your proof-of-delivery-location time record.
Order ref + device
Your order reference (passed as a parameter) plus device, browser, and OS.
{
"consent": "granted",
"source": "gps",
"order_ref": "TL-20488",
"timestamp": "2026-05-31T14:22:09Z",
"lat": 51.514230,
"lng": -0.142500,
"accuracy_m": 9,
"address": "12 Brook Mews, rear gate",
"city": "London",
"country": "United Kingdom",
"maps": "https://maps.google.com/?q=51.514230,-0.142500",
"device": "mobile",
"browser": "Safari 18",
"os": "iOS 18"
}Declined visits return "source": "ip" with an approximate city and no precise pin.
Built for last-mile operations
Confirmation Links shine wherever a customer wants their order to arrive at the right spot. The recipient is actively trying to receive something and chooses to share — that's consensual by nature.
Last-mile parcel delivery
Text the recipient a link before the van is loaded. They tap Share, you lock the exact drop-off pin — no more "left at the wrong door" disputes or failed-delivery redeliveries.
Food & grocery delivery
For apartment complexes, offices, and parks where a street address is useless, the customer confirms the exact spot. The rider gets a tappable pin and the food arrives hot.
Courier & same-day dispatch
Send a confirmation link per stop on a route. Each customer pins their own drop-off, so the dispatcher builds an accurate run instead of chasing vague addresses by phone.
Locksmith, plumber & trades arrival
A customer locked out or with a burst pipe shares their exact location in one tap. The tradesperson navigates straight to the property — no fumbling with a half-remembered address.
Proof of delivery location
Keep a timestamped, mapped confirmation per order for disputes and audits. Export to CSV alongside your order reference for a clean proof-of-location trail.
Hard-to-find sites & new builds
Rural lanes, construction sites, and addresses GPS apps don't know yet — the customer pins where the truck should actually pull up, accurate to the gate.
Confirmation pin vs typed address vs the sketchy "exact location" tools
The honest comparison search engines bury. We're the consensual, brandable option built for deliveries.
| Feature | Confirmation Link (this) | Typed address / IP geo | Grabify / IPLogger "exact" |
|---|---|---|---|
| Drop-off accuracy | 5–50 m (GPS pin) | Building / ~50 km | Claims exact, delivers IP |
| Customer consent | Required, every link | n/a / none | None — covert by design |
| Accuracy radius in meters | Yes | No | No |
| Navigable Maps pin + timestamp | Yes | No | No |
| Proof-of-location record | Yes (CSV per order) | Address only | No |
| Honest about what it does | Yes | Yes | No — false 'exact GPS' claims |
| Reportable by recipients | Yes (button on notice) | n/a | No |
| Looks legit on a custom domain | Yes (your brand) | Yes | No (blocklisted) |
| Allowed on the platform | Yes (consensual) | Yes | Banned / disabled on report |
"Exact location" grabber tools either deliver only IP geo (so the "exact" claim is marketing) or rely on the same consent prompt we use — they just hide that from you and land on Gmail and antivirus blocklists. There is no covert path to a precise drop-off. We don't pretend otherwise.
Confirmed GPS drop-off (this page)
- Meter-accurate, from the customer's GPS chip
- Requires consent every time — notice + browser Allow prompt
- For last-mile, food, courier, and trades arrival
- PRO feature
IP geolocation (the other page)
- City-accurate (~50 km), from the visitor's IP
- Passive — no popup, no consent step
- Too coarse for last-mile — fine for aggregate attribution
- Free forever
Platform-wide, Track Link has served ~2,560 users and ~232,000 tracked clicks across 96 countries. Delivery confirmation is built on the same consent-first Pinpoint Links engine.
The honest part: covert tracking is not a feature
If you came here hoping to use a delivery-styled link to pinpoint someone without them knowing, read this carefully — then leave.
- It's prohibited. Using Track Link to capture anyone's location without their knowing, affirmative consent violates our Terms of Service and applicable law.
- It's reportable. Every link shows the recipient a notice with a Report this link button. One tap flags it to us.
- It gets the link disabled. Reported or detected covert-use links are disabled and the account is reviewed. We cooperate with lawful requests.
- It doesn't exist anyway. No legitimate tool can return precise GPS without the browser's OS-level permission prompt firing. Any service promising silent "exact location" is either lying or delivering mere IP geo.
- Consensual delivery use is welcome. Last-mile, food, courier dispatch, and trades arrival where the customer is expecting their order and taps to confirm — that's exactly what Confirmation Links are for.
FAQ
Straight answers about confirming delivery locations, consent, and what's allowed.
How does a delivery location confirmation link actually capture the drop-off point?
It uses the browser's standard Geolocation API — the same one Google Maps and every food-delivery app already use. You text or email the customer a short link before the courier sets off. When they open it, they first see a plain-language notice: this link is asking for your location, who it's for, and why. If they tap 'Share my location', their phone fires its own native 'Allow location access' prompt. Only after they approve that prompt does the device return precise coordinates from its GPS chip, Wi-Fi, and cell signal. Dispatch then sees the exact drop-off latitude/longitude, the accuracy radius in meters, a reverse-geocoded address, a Google Maps pin to navigate to, and a confirmation timestamp. No approval, no coordinates.
How accurate is the captured delivery location versus a typed address?
A typed address gets you to a building; a confirmed drop-off pin gets you to the door. Precise GPS from the customer's device is typically accurate to 5–50 meters outdoors, often within a few meters on a modern phone. That's the difference between 'apartment block on Elm Street' and 'the rear gate by the loading bay'. Every confirmation stores the device-reported accuracy radius in meters, so dispatch knows instantly whether a fix is a tight 9 m pin or a loose 800 m estimate worth a quick call. Typed addresses can't do that, and IP geolocation is only city-accurate (~50 km) — useless for last-mile.
Can I capture a customer's delivery location without them knowing?
No. Not on Track Link, and not through any legitimate tool. The browser physically will not hand over GPS coordinates without the customer approving a permission prompt that the operating system controls — we can't suppress it, fake it, or pre-approve it. On top of that OS-level prompt, we add our own visible notice before the prompt even fires, plus a report button on that notice. A link built to capture someone's location covertly is prohibited here, gets disabled on report, and simply does not work technically. A delivery confirmation only works because the customer is actively trying to receive their parcel and chooses to share — that's the whole point.
What happens if the customer declines to share their location?
Nothing breaks. If they tap 'Continue without sharing', dismiss the browser prompt, or have already blocked location for that site, the link still works and they can carry on. You simply get the approximate IP-based location for that visit (~50 km, city level) instead of a precise pin — clearly flagged in the dashboard as 'IP (approximate)' versus 'GPS (confirmed)'. In practice you'd then fall back to the typed address or a quick driver call. Declining is a first-class path, not a dark-pattern dead end, which is exactly why customers trust the prompt enough to say yes.
What exactly does dispatch see after a customer confirms?
For a confirmed drop-off you get: precise latitude and longitude, the accuracy radius in meters, a reverse-geocoded street/city/region/country, an embedded Google Maps pin the courier can tap for turn-by-turn directions, the confirmation timestamp, plus the usual click metadata — device, browser, OS, and any order reference you passed as a UTM/query parameter. For a declined or IP-only visit you get the approximate city and the same metadata, flagged as approximate. Everything exports to CSV so you keep a proof-of-delivery-location record per order.
Is capturing a delivery location from a link legal?
When it's consensual and for a legitimate purpose, yes — it's the exact consent model every delivery and ride-share app already uses. The lawful part is the consent: the customer is shown what's being requested, by whom, and they affirmatively agree before any coordinates are sent, specifically so their order reaches them. What is not legal — and is banned under our Terms — is using a delivery-styled link as a pretext to extract someone's location for stalking, surveillance, or any purpose they didn't knowingly agree to. In the EU/UK, precise location is sensitive personal data, so disclose it in your privacy policy and only use it to complete the delivery. Use it to drop parcels at the right door. Never to trick anyone.
Why is this a PRO feature?
Precise GPS capture carries reverse-geocoding costs, the Maps embed, stricter abuse monitoring, and consent-record retention, so it lives on the PRO plan. Our free IP-based location link stays free forever. You can start free, test the IP-based location-tracker link, and upgrade to PRO when you need meter-accurate, consent-gated drop-off confirmation for real deliveries.
Can I send these confirmation links in bulk for a dispatch run?
Yes. Create a Pinpoint Link per order (or per route stop) and append your order reference as a query parameter so each confirmation maps back to the right delivery in your dashboard and CSV export. Send them however you already reach customers — SMS, email, WhatsApp, or your order-tracking page. Each link still shows the same consent notice, so every confirmation is individually, knowingly agreed to. Custom branded domains keep the links looking like they came from you, not a random shortener.
Related
GPS location tracking link
The consent-gated, meter-accurate Pinpoint Link this is built on.
Request location by link
Ask someone to share where they are — the consent-first way.
Exact location tracker link
What "exact location" really means — and what it can't mean.
IP location tracker link
The free, passive, ~50 km counterpart to precise GPS.
Get parcels to the right door — the consensual way.
Delivery Confirmation Links are a PRO feature: meter-accurate drop-off coordinates, an accuracy radius, a navigable Maps pin, and a timestamp on every confirmation. The customer always sees the notice first and can always decline. Start free, upgrade when you need precision.