What brand protection monitoring covers
Brand protection teams watch for anything selling or impersonating a brand without permission: counterfeit products on marketplaces, unauthorized resellers and grey-market imports, sellers breaking minimum advertised price (MAP) agreements, lookalike domains and phishing pages, and fake social profiles. The work is mostly finding — searching marketplaces, search engines and the open web on a schedule — then documenting what was found for takedown requests.
That finding has to happen continuously and in every market the brand sells in, because listings appear and disappear daily and many sellers only list in certain regions.
Why proxies are needed
Marketplaces and storefronts show different results by location: different sellers, prices, stock and sometimes different products. A monitor that searches from one office sees one market. Large platforms also limit and challenge automated traffic from datacenter ranges, so a monitoring crawler on cloud IPs gets blocked before it finishes a sweep.
Residential proxies solve both. Each request goes out from a real household connection in the market you choose, so you see what local shoppers see, and rotating addresses spreads a large sweep across many visitors instead of one.
Which proxy for which job
Rotating residential is the default for marketplace and search-engine sweeps: a fresh IP per listing or query, targeted to the country or city of the storefront. Static ISP addresses suit monitoring that runs as one identity over a long period, such as following a specific seller's storefront, because the IP never changes for the term you rent it.
For daily full-catalogue sweeps, bandwidth becomes the bill. Unlimited proxies are priced per day with no gigabyte meter and unmetered concurrency, so the cost doesn't grow with the size of the crawl. Datacenter proxies are the cheapest option for sites that don't block datacenter ranges, such as checking lookalike domains and phishing pages.
Keeping evidence usable
Log the exit country, city and timestamp with every capture, so a finding can be shown to have been visible to shoppers in that market at that time — marketplaces' takedown processes ask for exactly that. Keep request rates modest per platform, and use sticky sessions when a check has to page through a seller's listings as one visitor.
Our acceptable use policy sets out what the network may and may not be used for.