How do you use AirTag history in a delivery dispute?

You compare the tag's recorded coordinates and timestamps against the carrier's own claim. That settles the three arguments that stall delivery disputes: the parcel marked delivered that was never at your address, the attempted delivery where the tag never left the depot, and the drop made two streets away. Then you put the specific rows in writing.

Which delivery disputes does a recorded route settle?

All three of the common ones turn on the same missing fact: where the parcel actually was at the minute the carrier says something happened to it. Their system asserts an event. Your record either agrees with it or visibly does not.

• Marked delivered, never arrived. The status flips to delivered at 14:32 and the tag is reporting from a sorting hub eleven miles away at 14:31 and 14:47.
• Attempted delivery, nobody called. The card says they tried at 09:10; the tag never left the depot that morning and reported from the same coordinates all day.
• Delivered two streets away. The coordinates land on a road that is not yours, and stay there, which is a different problem from a driver who was briefly nearby.
• Delivered before it could have been. The timestamp on the delivery event precedes the first report from anywhere near your postcode.

None of this is available from Find My, which shows one pin at the most recent report and overwrites it. By the time you are arguing, the pin has moved on and the afternoon in question is gone.

How do you read coordinates against an address?

Take the latitude and longitude from the row you care about, paste the pair into any map, and look at where it lands relative to your building. The place name in an export is reverse-geocoded convenience; the coordinates are the fact, and they are what you quote.

• An AirTag position is roughly where the passing iPhone that relayed the sighting was, so treat it as a neighbourhood-scale answer, not a doorstep-scale one.
• "Two doors down" is not a finding. "Three streets away, for forty minutes, with no report near my address all afternoon" is.
• Distance matters less than pattern. A single stray point proves little; a run of consecutive reports in the same wrong place is hard to explain away.
• Check the timezone before you compare anything. A one-hour offset turns a contradiction into a coincidence and back again.
• Absence of a report near your address is not proof of absence. Say what you have, meaning reports from elsewhere at those minutes, rather than what you lack.

Write down the two or three rows that matter before you write anything else. The email is easier once you know exactly which timestamps you are standing on.

What does the record not settle?

• That the tag was still inside the parcel. If the box was opened, the tag's route stopped being the parcel's route and nothing marks the moment.
• What was in the box, or its condition. The tag reports its own position and nothing about its surroundings.
• Who moved it. A route shows a path, not a person.
• Anything during a quiet stretch. Inside a metal roller cage in a closed depot, hours can pass with no passing device to relay a sighting.
• Anything before you connected, because those reports were never written down anywhere.

Name these yourself in the email. A dispute handler who finds the hole first discounts the whole message; one who reads you pointing at it tends to take the rest at face value.

What should you check for each kind of claim?

How do you write the email that gets acted on?

Start with the seller, not the courier. The courier's customer is usually the company that shipped the parcel, and that company is the one who can reship, refund, or open an investigation on your behalf. Copy the courier if you have a route to them.

1. Put the order or tracking number in the subject line with two words of what you want: "Order 4417, delivered to wrong address".
2. Open with the claim in one sentence: what their system says, and what your record shows instead.
3. Quote two or three rows exactly, with date, time, timezone and coordinates, rather than describing them.
4. Attach the timestamped PDF evidence report for a human to read and the CSV underneath it for anyone who wants to check the rows.
5. State plainly what the tag does and does not show, including that it reports its own position and not the contents of the parcel.
6. Say what you are asking for and by when: redelivery, refund, or a driver GPS check against these coordinates on this date.
7. Keep it short and unemotional. The person reading it did not lose your parcel and decides faster when there is nothing to defend against.

The single most effective line is usually a request they can act on internally: asking them to compare their own driver telemetry against the coordinates you supplied, on the date you supplied. It is cheap for them to check and it is the check that resolves the argument.

Why does the tag have to be recording before the dispute?

Because there is no retrospective option. Find My holds one pin and replaces it, Apple keeps no readable location history on its servers, and the old trick of reading a Mac's local Find My cache stopped working with macOS Tahoe. If nothing was saving the reports on the afternoon in question, that afternoon does not exist anywhere.

AirTag History polls every 5 minutes and saves each report it gets back with latitude, longitude and timestamp, from the moment you connect onward. Connecting opens a 7-day free live tracking window, and paid passes extend live tracking to 30 days, 90 days, or 6 months. Everything recorded during your window stays stored on your private timeline, ready to export whenever a dispute arises.