
A Bluetooth tracker can appear under a different identifier even though the physical tag has not changed. That behavior is part of the privacy design of modern tracker networks, and it affects how manual scans, known-device lists, and unwanted-tracker alerts are interpreted.
Google's Android guidance says each Bluetooth tracker has a random ID that changes regularly. Apple says AirTag, Find My accessories, and compatible tracking devices use Bluetooth identifiers that change frequently.
{getToc} $title={What a changing tracker ID means}
The identifier is designed to rotate
A tracker does not need to advertise one permanent public identifier forever. Google documents rotating or ephemeral identifiers in the Find Hub network specification, and Android's user guidance explains the practical result: a tracker can later appear under a different random ID.
The purpose is privacy. A stable identifier would make long-term observation of the same radio device easier for unrelated scanners.

The same physical tracker can look new to a scanner
Google says that after a tracker changes its random ID, Android may no longer identify it as the same tracker and can show it as a new tracker in later scans or alerts.
That is an identity-continuity problem for the scanner, not evidence that a second physical tracker suddenly appeared. You need other context before deciding that two observations represent two different devices.
ID rotation can explain why an earlier action stops working
Changing identifiers can also affect actions tied to an earlier detection. Google lists a changed device ID as one reason Play sound may fail after an alert. Apple similarly notes that if an item was with you overnight, its identifier may have changed, which can affect how Find My associates the current item with the earlier alert.
The unknown tracker alert guide explains what information is worth saving when you receive an alert. The Bluetooth tracker guide covers the difference between raw BLE observations and an operating system's unwanted-tracking decision.
Do not treat one Bluetooth ID as permanent identity proof
A displayed Bluetooth identifier is useful for organizing what your phone observed at that moment. It should not be treated as a permanent serial number or a guaranteed cross-session identity.
| Observation | Reasonable interpretation | What it does not prove |
|---|---|---|
| Same ID seen repeatedly in one session | The phone is probably grouping the same current broadcast identity | Permanent identity across future sessions |
| Different ID later | The tracker may have rotated its identifier | That a second physical tracker exists |
| Known label no longer matches | The stored label may be tied to an older platform ID | That the familiar device has become malicious |
| Alert continuity changes | The platform may be working with a new identifier state | That the original alert was necessarily wrong |
Known-device labels are useful but have a boundary
Tracker Detector: Tag Finder lets you mark familiar BLE devices as known and add a local label. That can reduce repeated review of devices you recognize.
The app does not promise permanent identity across identifier rotation. A familiar physical tracker can later appear under a different platform ID, so a known-device label is a convenience for observations that still match, not a permanent cryptographic identity.
Use several clues when continuity matters
When you are trying to decide whether a current observation matches an earlier tracker, compare more than the identifier. Consider the alert route, approximate time, device family or manufacturer information, repeated signal behavior, physical location, and any serial or manufacturer information the platform exposes after you find the item.
Keep the conclusion proportional to the evidence. Identifier rotation is expected behavior in modern tracker systems, so an ID change alone is not a sign of tampering, evasion, or a new device.