BPBrandPatrol
Methodology

Three steps on the surface, a repeatable seven-stage process underneath

This page documents exactly what happens between a branded search and a case landing in your workspace — every stage, what gets captured, and where the method's limits are, so your legal or compliance team can evaluate it properly rather than take our word for it.

1

Scope

Before anything runs, we agree your branded keywords and their common variations, which countries and cities to check, which devices to observe, and how often. What isn't listed isn't scanned — scope is fixed up front, not discovered as you go.

2

Scan

Search results are checked from the regions and devices your customers actually use, on the schedule you chose — a single one-time pass or continuous scheduled monitoring. Every check reads the same public page a real searcher would see.

3

Trace & report

Anything that looks unauthorized gets its redirect chain followed hop by hop, its tracking parameters extracted, and its partner or advertiser identified. It's checked against your roster, then packaged with timestamped screenshots into a case your team can open and act on.

Methodology

The method, stage by stage

Every case — hijacker or brand bidder — passes through the same seven stages before it reaches your workspace. This is the detail behind the three-step summary above, and behind every capability on the features page.

1

Scoping

You and BrandPatrol agree the branded keywords to monitor, including common misspellings and variations, which countries and cities to check from, which devices to observe — desktop and mobile — and how often scans run. Anything not on that list is explicitly out of scope: it isn't scanned, and it isn't billed.

2

Roster intake

Before a single scan runs, we import your list of authorized partners — the affiliates, agencies, or resellers you've actually approved to bid on your brand — along with what each one is permitted to do. Every later detection is checked against this list first, so an approved partner never turns into a case you have to dismiss.

3

Observation

For each agreed keyword, from each agreed location and device, we check what's actually showing in the public search results — the same results page a real searcher would see, reached with no login and no special access.

4

Capture

When an ad on a branded term is found, we take a timestamped screenshot of the search-results page showing it, then follow the ad through to wherever it lands and screenshot that page too, along with the display URL exactly as it was shown in the ad.

5

Tracing

The click isn't just followed to the final page — every redirect hop in between is recorded in order, and the tracking parameters attached to each hop are extracted, because that's usually where the identifying information lives.

6

Attribution

The tracking parameters are used to resolve which affiliate ID and which network the traffic is running through. Where the advertiser isn't one of your affiliates, we cross-reference the public ad-transparency record search engines already require, to identify who placed the ad.

7

Case filing

The result goes through the roster check one more time. If it matches an authorized partner doing something they're approved to do, no case is filed. Otherwise a case is opened with a status your team can act on: new, in progress, solved, or muted.

Detection scope

Two kinds of unauthorized traffic, tracked separately

Not every unwanted ad on your brand name is the same problem, so BrandPatrol keeps them in separate case types — and checks both against the same roster before either one becomes a case.

Ad hijackers

Advertisers with no relationship to your brand at all — no partner ID resolves in the redirect chain, no match on your roster — running paid search or shopping ads on your name. The landing page often sells a competing product or a knockoff, or simply captures traffic that should have reached your own site for free.

Brand bidders

Affiliates already inside your own program, bidding on your branded terms anyway. The redirect chain resolves to a tracking parameter carrying a partner ID and network — proof the click ran through your program, which is what makes this a commission problem rather than an outside trademark one.

Roster cross-check

Both hijacker and brand-bidder detections pass through the same check before a case is ever raised: does the resolved partner ID match someone on your approved list, doing what they're approved to do? If it does, nothing is filed — you only ever see the exceptions.

Boundaries

What we ask you for — and what we never ask for

Getting started takes four inputs from you. Getting access to your systems isn't one of them.

What we never ask for: access to your ad accounts, a login to your affiliate platform, API keys, analytics access, or any customer data. Everything BrandPatrol sees is what a shopper searching your brand would see, plus the public ad-transparency record — nothing that requires you to grant us access to anything you run.
Legal footing

Built on public information, nothing else

Monitoring reads what any shopper searching your brand would see, plus the ad-transparency record every advertiser is already required to publish. Full detail on data handling lives in our privacy policy.

Case files

Reading a case file

Every case carries the same fields, whether it's an ad hijacker or a brand bidder. Here's what each one proves.

Screenshots + timestamp
A capture of the search-results page showing the ad, and a capture of the landing page it led to, both taken at the same recorded moment — proof of what was publicly visible, and when.
Display URL
The URL shown in the ad itself, exactly as it appeared on the results page — separate from wherever the redirect chain actually sends the click.
Redirect chain
Every hop the click passed through between the ad and the final landing page, in order, not just the destination — this is where tracking parameters and partner identifiers usually surface.
Affiliate ID
The partner identifier extracted from the tracking parameters in the redirect chain, when the traffic is running through your affiliate program rather than an unrelated advertiser.
Network
The affiliate network the partner ID belongs to, so a case can be routed straight to the compliance team able to act on it.
Observed country & device
Where the ad was seen and on what device — results vary by both, so a case records exactly where the ad was visible, not just that it existed somewhere.
Status
Where the case stands in your workflow: new, in progress, solved, or muted — tracked per case so nothing gets chased twice or dropped silently.
Detection limits

Where detection has limits

No monitoring method sees everything. These are the honest constraints that follow from how it actually works.

Detection depends on an ad actually being visible when we look — everything below follows from that.

  • An ad has to be serving at scan time to be observed. If it's paused, outbid, or simply not showing on that particular search at that moment, there's nothing to capture.
  • Rotation, budget pacing, and geo-targeting mean no monitoring tool sees every impression. Advertisers don't show the same ad on every search, every time, in every place — coverage is a sample of what's live, not a complete record of everything that ever ran.
  • Higher scan frequency and broader location coverage raise the odds of catching a given ad. They improve coverage; they don't reach 100%, and no monitoring service can honestly promise that they do.
  • What happens after a case is filed depends on the network or platform it's sent to. BrandPatrol builds the evidence; enforcement — a suspended account, a pulled ad, a commission clawback — is a decision made by whoever receives the case, not by BrandPatrol.

Questions about a specific edge case? Check the FAQ, or ask when you get a quote.

Ready to see what's on your brand name?

Get a quote scoped to your keywords, regions, and roster — the same inputs this page just walked through.

Get a quote