Brand Protection on Marketplaces: Profiles Against Counterfeits

GetAntik editorial team · October 26, 2026 · 9 min read

How brand teams use isolated browser profiles to spot counterfeits, MAP violations and content theft on marketplaces without a skewed, personalized view.

Why you can't spot counterfeits from your own account

A brand manager opens Amazon or a regional marketplace, searches for their own product, and sees exactly what the platform wants them to see: listings they've already interacted with, sellers they've already bought from, recommendations built on their own history. That's not what an ordinary shopper in Texas, Munich, or Manila sees. And it's the ordinary shopper who stumbles onto a counterfeit listing, a seller undercutting MAP (minimum advertised price) policy, or a knockoff listing built from stolen brand photos.

Personalized search results are normal algorithm behavior, but they turn brand monitoring into a blind spot. If the legal or IP protection team searches for violations from the same logged-in account, from the same office, every time, they see a cropped version of the market. The fix isn't "search harder" — it's viewing the marketplace through the eyes of different buyers in different regions, without shared history and without being logged into the brand's own seller account.

What you actually need to find

Brand monitoring on marketplaces usually comes down to four categories:

• Counterfeits and fakes — listings using the brand's logo, unlicensed copies, products sold without the rights holder's authorization.
• MAP violations — authorized dealers selling below the agreed minimum advertised price.
• Gray market and parallel imports — product sold in a region where the brand has an exclusive distributor.
• Listing content theft — photos, descriptions, and videos copied onto someone else's listing without a license.

Each case needs to be not just noticed but documented: a screenshot of the page, the date, the price, the seller, sometimes a test purchase to get a tracking number and a physical sample. This is the evidence base for a complaint to the marketplace's support team, a legal letter, or a lawsuit. The quality of that evidence depends heavily on how "clean" the view was — not skewed by your brand's own browsing history.

Why you need an antidetect browser, not a second account in regular Chrome

A second account in the same browser isn't a solution. Marketplaces and ad networks read the device fingerprint: screen resolution, fonts, WebGL and canvas parameters, timezone. If three accounts log in from the same Chrome on the same laptop, the platform sees the connection between them regardless of login state, and feeds back the same personalization — now tied to the browser instead of the login.

An antidetect browser solves this differently: each profile is an isolated environment with its own fingerprint parameters and its own proxy. For brand monitoring, this means a "buyer in Madrid" profile actually looks like a Madrid buyer to the platform: timezone, interface language, and geolocation are derived from the proxy's exit IP instead of staying random. In GetAntik this is configured in the profile editor — language, timezone, and locale sync automatically with the profile's proxy settings, with nothing to adjust manually.

How many profiles you actually need

There's no single number, but the math is straightforward: regions × platforms × profile role.

Example for a mid-size apparel brand sold through three authorized distributors in Europe, monitoring counterfeits across four marketplaces:

That's a fleet of 50–65 profiles just for brand protection, not counting accounts used for advertising or the brand's own sales on those same platforms. This is well past the Free plan's 3 profiles — this volume fits comfortably in the Base plan (100 profiles) or the Team plan (300 profiles) if brand protection isn't a one-person job but a small team of two or three specialists split by region.

Building the monitoring process

1. Group profiles by logic, not by chaos. Every profile gets a clear name: platform, country, role (monitoring / test purchase). If the brand already runs several stores or sub-brands on the same platforms, the profile structure overlaps with the approach described in multi-brand e-commerce management — same principle there: each brand gets its own profile group, not mixed with the rest.

2. Proxies with correct geo-binding. A "buyer in Warsaw" profile should connect through a Polish IP, not a random datacenter address — otherwise the platform either won't show localized results or will flag the session as suspicious. For regular monitoring, residential proxies tied to a city work best; for one-off checks, mobile or datacenter proxies are fine. With the built-in HollyProxy integration, proxies for the country you need are bought directly from the interface, without switching between services.

3. A monitoring schedule, not a one-time sweep. Counterfeit sellers appear and disappear fast — some live on a platform for a week, collect payment on a batch of orders, and vanish. A quarterly check won't catch that. A workable rhythm is every 1–2 weeks for priority regions and monthly for the rest. For profiles used infrequently, it's worth planning in advance when to rotate a proxy and when to leave it alone — rotating IPs too often on a "regular buyer" profile looks just as suspicious as never rotating at all.

4. Documenting evidence. Every finding needs a screenshot with a date and URL, sometimes an export of the session's cookies to confirm the view was made from the right region without manual manipulation. Keeping raw profile sessions is also useful if a complaint needs to be refiled weeks later with updated data — that way there's no need to log in again and wait for the account to "warm up."

5. Test purchases on a separate track. If a complaint requires a physical product sample, the purchase should be made from a profile separate from the monitoring profile — with a real shipping address (often the legal department's or the investigating agency's address), its own card, and its own phone number. Mixing "browsing" and "buying" roles in one profile is a bad habit: an account with an order history looks different to the algorithm than a fresh browsing profile, and personalized results creep back in.

What not to do

Don't automate scraping against the marketplace's rules. Most platforms explicitly prohibit automated data collection without an official API in their terms of service. An antidetect profile with a real person manually browsing listings and taking screenshots is legitimate monitoring. A script that scrapes thousands of pages at scale, bypassing bot protection, violates the platform's terms — and that has nothing to do with using multiple profiles; it's a question of collection method, not profile count.

Don't pretend to be an authorized distributor if you're not. Creating a seller account under a brand name that isn't yours isn't brand protection — it's fraud. Monitoring as a buyer means viewing public search results available to anyone; impersonating a seller is an entirely different matter, and no legitimate brand protection process goes through it.

Don't ignore the activity log if a team handles the monitoring. When a lawyer prepares a complaint but an analyst made the finding a week earlier, you need traceability: who flagged a violation, when, and from which profile. This isn't about watching employees — it's about not wasting time re-finding the same listing or losing context when the analyst is on vacation. More on why this kind of log helps rather than hinders a team's work is covered in the piece on activity logging and audit for team profiles.

Don't skimp on regional coverage. Counterfeits almost always surface first in regions with weaker moderation before spreading elsewhere. If you only monitor the brand's home market, customers will notice a violation in a neighboring country before the brand protection team does — and that hits reputation as much as sales.

Splitting the work across a team

For a mid-size brand, monitoring rarely works as a one-person job — there are too many regions and platforms to cover thoroughly alone. The practical model is assigning each specialist a set of regions or platforms, giving access to a shared pool of profiles with limits so nobody accidentally closes a teammate's active session. In GetAntik's team section, this is set up with roles and per-member profile limits: an analyst sees only their slice of the pool, while a manager sees the whole fleet and its activity log.

A separate benefit of team setup is handing off a found case — complete with a live session — to a lawyer for drafting a complaint: no need to forward screenshots and logins, just pass along the profile itself with its full browsing history.

Monthly cost estimate

Using the example above — 50–65 monitoring profiles plus 10–15 for test purchases, roughly 70–80 profiles total — this volume fits the Base plan (100 profiles, $44/month) with room to grow. For a larger brand covering a dozen markets with a standing team of 3–5 specialists, the Team plan (300 profiles, $79) makes more sense: it covers monitoring plus parallel tasks like checking the brand's own ad campaigns or competitor pricing. The main cost beyond the plan itself is proxies for the needed geographies — pricing depends on the number of countries and the proxy type. Current plan limits and pricing are on the pricing page.

FAQ

Do I need to buy proxies for every country where the brand sells, or do broad regions suffice? It depends on how localized the counterfeiting is. If violations are usually tied to a specific country (say, parallel imports through one intermediary), you need a proxy there. For general monitoring of major platforms like Amazon, covering the main regional domains (.com, .de, .co.uk, .fr) already reveals most of the localized results.

Can the same profile be used for monitoring over several months? Yes, and it's actually better: an account with a browsing history looks like a regular returning buyer to the algorithm, rather than a freshly created account. Don't suddenly change that profile's proxy or fingerprint without reason — this is a case where stability matters more than frequent rotation.

What if the marketplace requires identity verification to create a monitoring account? Use real employee or company details, no fake documents — verification requirements usually target sellers or large purchases, not ordinary browsing. If a platform asks for verification even for a buyer account, that's a standard KYC procedure, and it shouldn't be bypassed with fake data — set the account up as an official brand representative with transparent information.

How should I store evidence so it holds up for a legal complaint months later? Save more than just a screenshot: export the session cookies, the timestamp, and the listing URL — covered in more detail in the piece on exporting and backing up profile sessions. When you need to re-contact marketplace support later, that archive saves hours of rebuilding the evidence chain.

brand protectionantidetect browsermarketplace monitoringcounterfeit detectionmulti-accounting