Mobile Proxy Price Monitoring
Competitor prices are assembled per visitor, so a single vantage point does not return the market price — it returns one shopper’s price. This guide covers what moves the number, how to collect a series you can defend, and where mobile IPs are worth their cost.
- There is no single price — location, device, session history and whether you are signed in all move the number you are shown.
- The response window closed — AI shopping agents now surface competitor gaps to consumers in minutes, not the days a weekly report assumes.
- A blocked crawl is the good outcome — the expensive one is a decoy price served quietly to an address the retailer does not trust.
- Continuity is the product — a price series with a fortnight missing cannot tell you when a competitor actually moved.
See the number a shopper in that country is quoted.
Reach pricing that only exists on a phone.
Price Monitoring Overview
Price monitoring sounds like reading a number off a page. It is not, because most large retailers do not have a number to read — they assemble one per visitor. Location, device class, whether you are signed in, what you looked at previously and the currency and tax treatment implied by your address all feed into the figure you are shown. Ask from one place and you learn one shopper’s price with great confidence.
That is why the first decision in a monitoring programme is not which scraper to use. It is which shoppers you are trying to be. A brand checking whether resellers respect a minimum advertised price needs the view of a customer in each reseller’s market. A retailer defending margin on a category needs the view its own customers get. These produce different collection designs, and choosing the wrong one produces data that is internally consistent and answers nobody’s question.
| What moves the price | How it shows up | What you have to reproduce |
|---|---|---|
| Location | Different currency, tax treatment, shipping and often a different list price entirely | An exit IP genuinely inside the market |
| Device class | App-only offers, mobile-web discounts, and layouts that surface different variants | A mobile connection and a matching client |
| Session state | Member pricing, loyalty tiers, basket-dependent discounts | A decision about whether you monitor signed in at all |
| History | Retargeted offers and personalised ranking of variants | A clean identity, or a deliberately aged one — not an accidental mixture |
Write down which of these four you are holding constant before the first run. A price series is only comparable across days if the shopper it describes stayed the same, and the most common cause of an inexplicable price move is a change in the collector rather than in the market.
Scraping Competitor Prices
The mechanical part is the well-understood part, and it is covered in depth in the ecommerce scraping guide. What matters commercially is what you attach to each observation. A price on its own ages badly; a price with the market, the device, the availability state and the identity used to fetch it stays useful for years.
Minimum advertised price monitoring deserves particular care, because breaches are usually regional and often only visible to shoppers in that region. A brand checking compliance from head office reliably sees the compliant listing and files a clean report. The violation is real, it is simply not being shown to that address. This is the single most common reason a MAP programme reports nothing for months and then discovers a long-running problem.
timestamp 2026-08-24T09:14:02Z market FR # exit country, not the office country exit_ip … # and the ASN behind it device mobile # matched to the client you presented signed_in false sku … price … # with currency, before and after promotion availability in_stock seller … # who is actually selling on a marketplace
One habit saves a great deal of argument later: record what you were shown even when it looks wrong. A price that seems implausible is often a genuine regional promotion or a personalisation artefact, and both are findings. Silently discarding outliers at collection time removes the evidence you would need to tell the two apart.
Real-Time Price Tracking
The economics of speed changed recently, and it is worth being explicit about why. Through early 2026, several large technology and commerce platforms put agentic shopping systems into production — software that compares prices across retailers on a shopper’s behalf and acts on the result. The practical consequence is that a competitor’s price cut reaches your customers in seconds. A weekly pricing report was built for a world where it reached them in days.
That does not mean everything needs polling every minute. It means the cadence should follow the category rather than the reporting calendar. Electronics, travel and anything with visible promotional cycles justify several passes a day. Furniture, industrial supply and most business-to-business catalogues rarely justify more than one. Spending your request budget uniformly across a catalogue is the usual way a monitoring programme becomes expensive and slow at the same time.
- Tier the catalogue — A small set of price-leading products drives most competitive decisions. Watch those closely and sweep the long tail slowly.
- Alert on movement, not on schedule — A report that arrives whether or not anything changed trains people to ignore it.
- Distinguish a move from a variance — Before escalating a change, confirm it from a second vantage point in the same market. Personalisation produces convincing false positives.
- Keep the clock honest — Store collection time in UTC alongside the market’s local time. Promotional windows are local, and a series that mixes the two is unreadable.
Avoiding Detection During Monitoring
The failure that hurts is not the block. A block is loud, it appears in your error rate, and somebody fixes it. The expensive failure is being quietly served a plausible but different page — a decoy price, a stale cache, a generic fallback — and recording it as fact for six weeks. Retailers running bot mitigation frequently prefer that response precisely because it is cheap and it does not alert the collector.
Most of the defence against that is unglamorous. Keep request rates per host at a level a person could plausibly generate. Let the exit address rotate between sweeps rather than hammering one for a whole catalogue. Make sure the client you present and the network you arrive from agree with each other — a mobile user agent from a hosting range is a contradiction that costs nothing to detect. And watch your own collection health as a metric, because a rising share of suspiciously round or suspiciously identical prices is usually the first sign that you are being handled rather than served.
| Symptom | Most likely cause |
|---|---|
| Prices stop changing across a whole category | A cached or fallback page is being served. Confirm from a fresh address in the same market. |
| One market is always cheaper by a round factor | Currency or tax presentation, not a real price difference. Check what the page states rather than what you parsed. |
| Results differ between two runs minutes apart | Personalisation or an active test. Sample repeatedly before treating it as a move. |
| Mobile and desktop disagree consistently | Genuine app or mobile-web pricing. This is a finding, not an error. |
| Everything works, then nothing does, on a schedule | Your cadence is recognisable. Stagger the run and vary the order. |
For the collection mechanics behind all of this — crawl cadence, geo-priced catalogues and which proxy tier a job needs — see the ecommerce scraping guide, and scraping best practices for running it at volume without burning the pool.
Monitor Prices From the Market That Sets Them
Live PXM2 locations — pick the country whose pricing you need, and collect it from a real carrier IP inside it:
France
India
Singapore
Frequently Asked Questions
Why does the same product show a different price to different people?
Because most large retailers price per visitor rather than per product. The inputs typically include the country and region the request comes from, the device class, whether you are signed in, what you have looked at before, and sometimes the currency and tax treatment implied by your location. None of that is hidden or unusual — it is ordinary commercial practice. It does mean that "the price" is a question about an audience, not a fact you can look up once.
What is MAP monitoring and why does it need proxies?
Minimum advertised price policies set a floor below which a reseller may not advertise a brand’s product. Brands monitor for resellers breaching it, because one channel undercutting the network damages every other channel. It needs distributed collection because violations are usually regional and often only visible to shoppers in that region — a check run from head office sees the compliant listing and reports everything as fine.
Do I need mobile proxies, or will residential do?
Residential is the sensible default for most price intelligence and costs less. Mobile earns the premium in specific places: app-only or app-exclusive pricing, retailers whose mobile site prices differently from desktop, markets where the residential pools are already burnt, and any target that has learned to distrust the residential ranges available in that country.
How often should prices be collected?
From how fast the category moves, not from the reporting calendar. Fast-moving electronics and travel justify several passes a day; furniture and industrial supply rarely justify more than one. The consideration that has changed is speed of consequence: automated shopping agents compare across retailers in real time, so a competitor’s cut is visible to your customers long before a weekly report reaches your pricing team.
How is this different from the ecommerce scraping guide?
That guide is about the collection mechanics — geo-priced catalogues, crawl cadence, which proxy tier a job needs, and how not to burn a pool. This page is about the commercial job: what to monitor, how to tell a real price move from a personalisation artefact, and what makes a price series defensible when somebody disputes it.
Related Mobile Proxy Guides
Price monitoring shares its collection layer with the scraping guides and its commercial questions with the rest of the business cluster.
Business use cases
Core mobile proxy guides
Monitor Prices From Inside the Market
Dedicated 4G/5G modems with unlimited bandwidth and unlimited rotations — real carrier IPs that see the price a local shopper is actually quoted.
Get a Mobile Proxy