Skip to content
LightningBytes
Back to Blog

Residential Proxies for Brand Protection

Detecting counterfeit listings, unauthorised resellers and MAP violations across marketplaces and regions, with evidence that stands up to a takedown request.

by LightningBytes Team
  • brand-protection
  • residential-proxies
  • ecommerce

Brand protection work has an unusual requirement that distinguishes it from ordinary collection: the output is evidence. You are not just gathering data for analysis, you are building a case that a marketplace, a platform or a legal team will act on.

That raises the bar for both the collection method and the record keeping.

What you are usually looking for

  • Counterfeit goods presented as genuine, which is the highest-priority case.
  • Unauthorised resellers offering products outside an agreed channel.
  • Price violations where a reseller undercuts a minimum advertised price policy.
  • Trademark misuse in listings, titles or imagery.
  • Bundle and compatibility abuse, such as claiming compatibility that does not exist.
  • Grey market imports diverted from another region.

Why local vantage points are required

Marketplaces localise everything. Listings, sellers, prices and even the products shown vary by market, and some violations only exist in one region. A takedown request needs the observation to have been made as a buyer in that market would see it.

That means per-market egress. Country targeting is usually sufficient; city targeting matters when the marketplace localises to metro level. Verify the exit location rather than assuming, which is the habit described in Country, State, and City Targeting.

Evidence quality

An observation is only useful if it can be relied on. Capture:

  • The URL, including any search parameters that produced the result.
  • A timestamp in a fixed timezone.
  • A screenshot of the listing as displayed, which is the artefact most reviewers expect.
  • The structured fields: title, seller, price, currency, shipping origin, listing date.
  • The observed location, meaning the market you checked from and ideally the exit IP.
  • A content hash of the listing page, so you can demonstrate that the captured version is the one you saw.

That last item is often skipped and is the one that makes a dispute about "it looked different when we checked" resolvable.

Building the watchlist

A useful process has three layers:

Known infringers. Specific sellers or storefronts identified previously. Monitor them at a higher cadence.

Brand and product terms. Queries that surface new listings, including common misspellings and transliterations that counterfeiters use to evade filters.

Marketplace sweeps. Periodic broad checks by category and market to catch anything the targeted queries miss.

Deduplicate aggressively. The same counterfeit listing often appears under multiple seller names and slight title variations, and reporting twenty duplicates as twenty cases wastes reviewer attention.

Collection practice

Marketplaces are heavily defended, so residential IPs are usually required. Beyond that:

  • Hold a session per market so a sweep looks like one buyer browsing, not a distributed crawl.
  • Pace requests and honour rate-limit responses, as described in Rate Limiting vs Blocking.
  • Expect dynamic rendering. Many marketplaces build listings client-side, so a browser engine may be necessary. Options are compared in Picking a Browser Automation Tool.
  • Capture screenshots deliberately. They are expensive in bandwidth and time, so capture them for candidate violations rather than every listing.

From evidence to action

Collection is the input. The output is typically a report per case, containing the identified listing, the evidence bundle and a summary of the violation type. Keep each case self-contained, because the reviewer has no context beyond what you send.

Track outcomes. Which violation types get actioned, which marketplaces respond, and which sellers reappear after removal. That data improves your watchlist over time and tells you where enforcement effort pays.

Compliance boundaries

Brand protection is a legitimate use of proxy infrastructure, but it still has limits. Do not collect personal data beyond what is necessary, do not misrepresent yourself in communications, and keep collection within a marketplace's terms where possible. Our framework is in Data Collection Ethics for Engineering Teams, with the legal background in Is Web Scraping Legal.

A starting pilot

Pick one market and one marketplace. Build a small watchlist, run a sweep, and produce one case report end to end. That exercise surfaces the parts that need work, usually screenshot capture and deduplication, before you scale to many markets.

Verify your exit locations with the proxy checker and IP lookup. The broader commercial view is at brand protection, the monitoring pattern in Brand Protection Monitoring at Scale, and coverage on the residential page.

Start working with cleaner IPs

Clean, pre-filtered residential and mobile proxies, sign up and send your first request in minutes.

We use cookies for authentication and security. With your consent we also enable optional marketing & analytics cookies. See our privacy policy.