Why a Price Tracker Shows the Wrong Price, and How to Fix It
A track that follows the wrong number is annoying in a specific way: everything looks like it is working, notifications arrive, the history fills up — and the figure has nothing to do with the price you meant to watch. The good news is that this is rarely random. There is a short list of causes, and each has a fix.
The store shows different prices in different regions. Open the same page from another country, or without your session, and the currency changes along with the number. A tracker checking the page in the background can land in that other region, and then the history mixes euros with dollars and a harmless conversion looks like a crash in price. The track settings have a switch for exactly this: ignore currency change. With it on, a reading in a different currency is skipped instead of being recorded.
The price is only shown to members, or after signing in. Some stores put a club price next to the public one and set it in a larger, brighter font. Automatic detection judges what it can see, so the club price often wins on looks. If you want the price you actually pay, pick it by hand — that ends the argument for good.
The number is suspiciously small. Almost always this is a monthly installment, a deposit, a shipping fee, or the cheapest option in a size or colour list. These sit close to the real price and can be styled just as prominently. Switching the detection method usually helps; picking by hand always does.
The number is suspiciously large. Here the usual culprits are a crossed-out old price, a bundle, or the total for several items. Detection tries to skip crossed-out prices, but stores mark them in many different ways, and not every way is recognisable.
The page draws the price after it loads. Plenty of stores deliver an empty frame and fill in the price with a script a moment later. A check that reads the page too early sees nothing at all — the track then looks broken even though the page is fine in your browser. The pinned tab mode in the track settings gives the page more time and more of a real browser to work with; it is slower, and it is meant exactly for these sites.
The store asks to confirm you are not a robot. Then no price is read, because no page with a price was ever delivered. A tracker cannot and should not work around such a check. What helps is opening the product page yourself from time to time: the store remembers your confirmation for hours, and checks in that window go through quietly.
The price looks frozen. Before assuming the worst, look at noise smoothing in the track settings. It exists so that a shop nudging the price by a few cents does not wake you every hour, and it works by ignoring changes smaller than a chosen share of the price. Set too high, it will hide real movement too. Comparison is always against the last recorded price, so a slow drift still surfaces once it adds up past the threshold.
If none of this helps, take the shortest road: create the track again and choose the price by hand, from the list of candidates or by pointing at the element on the page. Such a track follows exactly that element and automatic detection leaves it alone. It will not repair itself if the store rebuilds the page — but it will never quietly switch to the wrong number either, and on a difficult store that trade is usually worth making.