Brand Protection 2026: Documenting Counterfeit Listings Across Markets

A storefront can look completely legitimate from one location and different from another. An authorised-dealer badge, careful product photography and descriptions that match the manufacturer's catalogue may appear in one market while another market shows different packaging, different prices and no badge at all.

Brand-protection teams run into this constantly. Marketplaces localise content by region, language and currency. Some sellers also vary what they show by visitor. The practical consequence for a case is simple: the evidence you collect has to come from the place where customers are buying, and it has to be reproducible.

That is why brand-protection teams use a multi-account browser for investigation work. Not for the usual multi-store management use cases, but to keep each market and each case in its own clean, documented browser, and to let several team members work from the same configured profile.

The Problem: One Browser Cannot Represent Every Market

A reviewer sitting in one country, logged into their own accounts, with one language and one currency, sees one version of a marketplace. A counterfeit listing aimed at customers in another country may simply not appear for them.

Several things can change what a listing shows:

• Region and IP geolocation
• Language, currency and locale settings
• Logged-in state and account history
• Browser characteristics such as screen size and device class
• Time of day and inventory changes

A case can stall when the screenshots in a file do not match what a seller's public storefront shows later, and nobody can say exactly how the screenshots were taken. The fix is not cleverness. It is method: capture from the right market, record the configuration, and keep every capture separate and traceable.

Why Ordinary Setups Fall Short

A single everyday browser. Cookies, saved logins, extensions and history from other work all follow you into every visit. Captures are hard to reproduce and hard to defend.

A VPN alone. A VPN changes your IP address and nothing else. Language, timezone, cookies and storage stay the same from one connection to the next, so a capture from "Germany" may still carry your home locale.

Incognito mode. A private window clears cookies and local storage when it closes, but it keeps your browser's identity settings. It also gives you no way to save the exact configuration, so a teammate cannot reopen it.

Separate physical devices. This works, but it does not scale. A team monitoring many sellers across many marketplaces cannot dedicate a device to every thread.

What the work needs is several independent browsers on one machine, each with its own proxy, locale and storage, that can be saved, named and handed to a colleague.

The Workflow

Profile Architecture

Base profiles by target market:

• US East (US proxy, US timezone, English)
• US West (same, Pacific timezone)
• EU major markets (UK, DE, FR, each with the appropriate locale)
• APAC where relevant (JP, AU, SG)

Each base profile gets its own consistent identity: fonts, screen, timezone and language that agree with the proxy location. In JustBrowser these are profile settings, so you decide them once per market and reuse the same settings for every case profile in that market.

Case profiles:

For each seller or case, create a new profile with the matching market's settings and dedicate it to that case. Keep cookies and storage for one case inside its own profile so captures from different cases never mix.

Naming convention matters once you manage dozens of profiles. Something like CASE-[MARKET]-[SELLER-ID]-[DATE], for example CASE-US-EAST-AMZN-3847592-JUN26, keeps everything searchable.

Proxy Configuration

Each profile needs a proxy whose location matches its market. A capture whose IP, language and timezone disagree is hard to rely on.

For marketplaces specifically:

• Amazon, eBay and similar large marketplaces: a proxy in the target country, matched to that market's locale
• Alibaba and AliExpress: match both the country and the currency the page shows
• Independent e-commerce sites: behaviour varies, so test each target and record what you see

Use a sticky session so the IP stays the same throughout a capture. An IP that changes mid-session makes the record harder to interpret. Proxy pricing varies by provider and plan; check your provider's current rates, and budget for the bandwidth of screenshots and page loads on each session.

The Documentation Session

1. Open the case profile.

Start the profile, confirm the proxy is connected, and check the exit IP and location against what you expect. JustBrowser's profile panel includes a consistency check you can run first, so you know the profile's locale, timezone and proxy agree before you capture anything. (Our JA4 and TLS fingerprints explainer covers what a site can read from a browser below the page.)

2. Browse the way a customer would.

Start from the marketplace home page, search for the product category, and open the listings from search results. View the seller profile, shipping information, returns policy and reviews. Seeing the listing in the context a customer arrives from gives a more faithful record than opening one URL directly.

3. Document everything.

Screenshot every page with timestamps: product listings, seller profile, shipping information, return policy, customer reviews.

For evidence that holds up:

• Record the profile configuration (JustBrowser can validate it through the profile panel or GET /profiles/{id}/fingerprint/validate, and the full profile can be exported encrypted)
• Record the proxy IP and geolocation
• Save cookies and local storage, which show session continuity
• Note the browser version and OS the profile reports

This metadata is your chain of custody. When legal asks how a screenshot was made, you can show the configuration and time.

4. Compare across markets.

Open a second profile configured for a different market and visit the same seller. Compare what each shows. If listings, prices or badges differ, document both versions and record why you think they differ. The difference between two markets is often the most useful part of the file.

5. Archive.

Save the documentation, mark the case profile as complete, and create a new profile for follow-up visits so later captures stay cleanly separate from earlier ones.

Scaling the Workflow

For teams monitoring many sellers, manual capture does not scale, but the method does if you automate the repetitive parts.

JustBrowser's REST API lets you start profiles programmatically. Call the API to launch a profile, receive a CDP WebSocket endpoint, connect Playwright or Puppeteer, run an evidence-collection script, and stop the profile. It is the same workflow as manual capture, but scriptable. Only automate collection from sites whose terms allow it, and keep volumes modest.

For data-collection architecture, see our web scraping at scale guide. The structure is similar, applied to documentation instead of extraction.

Teams doing this at scale typically:

• Keep a pool of market profiles, reviewed periodically
• Run scheduled collection on known problem listings
• Flag differences for human review
• Escalate confirmed cases for deeper investigation

Automation handles volume. Humans handle judgment calls.

A Worked Example

Take a hypothetical sportswear brand that suspects a seller on a marketplace of listing counterfeit jerseys. The listings look legitimate, with proper photos, reasonable prices and a respectable rating. Customer complaints about quality are coming in, and some units have been tested as fakes.

Week 1: Capture with a US-East market profile on Windows. Browse the seller's store, document listings, prices, descriptions and images.

Week 2: Repeat with a US-West profile on macOS (Apple Silicon). Compare against Week 1.

Week 3: Expand to profiles for the other markets where the brand sells, and add profiles that represent a first-time visitor and a returning shopper. Record any difference in listings, prices or packaging photos between them.

Document each version with full technical metadata and pass the file to legal. Differences between versions, captured with matching configuration records, are far stronger than a single set of screenshots.

Integration Points

Click-fraud crossover. Teams protecting a brand often also deal with fake clicks on their ads. ClickzProtect covers the click fraud prevention side for affiliates and traffic operators.

Tracking investigation metrics. Tracking dozens of cases in spreadsheets gets messy, usually right when you need history for a legal filing. If you build an internal case tracker instead, JustAnalytics offers cookieless analytics and error tracking for it.

Ad verification crossover. Publishers and ad networks can serve different content to different audiences. We covered that workflow in the ad verification guide. The profile structure transfers directly.

Use every profile within each marketplace's terms of service and your legal team's guidance.

Frequently Asked Questions

Why can a marketplace listing look different from one visitor to the next?

Storefronts can vary content by region, language, currency, logged-in state and sometimes by visit history. A listing a customer in one market sees may not match what a reviewer in another market sees. For a brand-protection case, that means evidence should be captured from the market where customers are buying, and each capture should record where and how it was taken.

Can I use a VPN instead of separate browser profiles for brand protection?

A VPN changes your IP address but not the rest of the browser: cookies, storage, language, timezone and identity parameters stay the same across connections. For documentation work you usually want each market to have its own profile with its own proxy, locale and storage, so captures from different markets are clearly separate and reproducible.

How should brand-protection teams organise browser profiles?

One profile per market and per case works well. Name profiles consistently, keep each case's cookies and storage inside its own profile, and share profiles with teammates instead of passing screenshots around. A profile that is dedicated to one case also makes it easy to show later exactly what configuration produced the evidence.

What evidence should I capture during counterfeit investigations?

Screenshot everything with timestamps: product listings, seller information, shipping details, customer reviews, and the checkout flow. Record the profile configuration you used (proxy location, locale, browser version). Export cookies and local storage. For legal proceedings, this metadata shows the evidence came from a specific configuration at a specific time, which makes it harder to argue the screenshots were fabricated.

---

Try JustBrowser

A multi-account browser for teams, built on a custom Chromium engine with native C++ integration, not an extension. Each profile is its own browser with its own cookies, storage, proxy and 40+ identity parameters, and teammates can share profiles. Local REST API and CDP for Playwright, Puppeteer, Selenium. Windows x64 and macOS (Apple Silicon). $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles.

Get started → · How it differs from Multilogin / GoLogin / AdsPower