Loading…
Loading…
Choose the browser environments you want your campaign to run in, and set a minimum version where your experience depends on it. Browser criteria are explicit for each request group, so you buy the environments you actually want rather than an average of all of them.
Browser targeting describes the software a visit arrives in: which browser, and which version of it. Buyers use it to select the environments a campaign is built for — a particular ecosystem, a measurement stack that reports consistently, or a version floor the experience depends on.
If your campaign is designed around a particular browser environment, target it directly instead of averaging across all of them.
Choose the environments your analytics and attribution report consistently, so results stay comparable across the whole campaign.
Where your experience depends on a recent release, state the minimum version and buy above it.
Separate request groups per browser give you a clear read on each, rather than one blended number you cannot act on.
Identify the browsers your campaign is designed around, and whether any version floor applies.
Note which environments your analytics and attribution report consistently, so campaign results stay comparable.
List the browsers you want for each request group, along with any minimum version.
Our team reviews your criteria against your formats, markets, and destination, and confirms achievable volume, pricing, and timing.
Visits arrive in every mainstream browser and across current and older versions. What a request settles is how much is available for your exact combination, at what price, and when it can start.
A browser and version describe the software a visit arrives in. They are not a statement about a person’s identity, demographics, or purchase intent.
The environments you select live in the written brief and are reviewed alongside your other controls.
Usually because the campaign is built for a particular environment — an ecosystem the offer is designed around, a measurement stack that reports consistently, or a version floor the experience depends on.
Yes. Name the browsers you accept — Chrome, Safari, Edge, Firefox — for each request group, with an optional minimum version. Visits arrive in every mainstream browser, so review is about the volume available for your exact combination rather than whether the environment exists.
Yes. Where your page, form, or script depends on a recent release, state the version floor in the brief and it is applied alongside your other criteria.
Yes. Name the environments you want, or state the ones to leave out — either way it is a selection, applied per request group and reviewed the same way.
No. Device type and operating system describe the hardware and platform a visit comes from; browser targeting describes the software used to view the page. They are separate controls, and none is inferred from another.
Yes. Each request group carries its own browser and version criteria, alongside its own geography, device, network, and landing page.
That is what the review determines. Every mainstream browser is represented, but volume depends on the full combination you request — browser and version plus geography, device, network and format. We confirm achievable volume, pricing, and launch timing before anything goes live.
Tell us which browsers and versions your destination supports, which must be excluded, and how you measure the campaign.
Apply for Buyer Access