Everything you need to go from signup to real browser traffic hitting your site — in about 10 minutes.
Browser Simulation sends real Chromium browsers to your website. Each visit fully loads your pages, runs your JavaScript, moves the mouse, scrolls, dwells, and clicks internal links — just like a real visitor would.
It's the right fit when you want traffic that shows up in your server logs and general-purpose analytics tools (like Plausible, Matomo, or server-side logs). If you specifically want events inside Google Analytics 4, see the GA4 Traffic Guide instead.
Pages fully render, JavaScript executes, interactions look authentic.
You provide one base URL — we discover and visit internal pages automatically.
Pick countries and desktop/mobile split per campaign.
Every browser simulation campaign runs on Browser Simulation Credits. Each delivered pageview costs 1 credit. Failed visits are free.
Create your account at trafficbot.co/register and verify your email. You'll receive 100 free GA4 credits on signup — browser simulation credits require a plan.
From the dashboard sidebar, go to Browser Simulation → Buy Credits. You'll see four plans:
| Plan | Credits / month | Price |
|---|---|---|
| Mini | 65,000 | $9 |
| Starter | 250,000 | $29 |
| Growth | 650,000 | $59 |
| Business | 1,690,000 | $119 |
All plans are monthly recurring via PayPal. Credits never expire and roll over each month.
Click the plan, you'll be redirected to PayPal to approve the subscription. Once approved, your credits are added to Browser Simulation Credits at the top of the dashboard. You can stack multiple plans on the same account for volume.
Go to Browser Simulation → Campaigns → New Campaign. The form is split into Basic and Advanced sections. Defaults are sensible — you only need to fill in URL, sessions, and countries to get started.
| Field | What to enter |
|---|---|
| Name | Any label you'll recognize (e.g., "Blog homepage test"). |
| Base URL | The single starting URL (e.g., https://example.com). We discover internal links from this page. |
| Sessions Per Day | 1–5,000. One session = one browser that may view 1 or more pages. |
| Bounce Rate | 0–1. Portion of sessions that view only the landing page. 0.25 = 25% bounces. |
| Max Pageviews Per Session | 1–5. Upper bound on sub-pages per non-bounce session. |
| Dwell Time Min / Max (sec) | 1–60 each. Random dwell per page within this range. |
| Device Rate | 0 = all desktop, 1 = all mobile, 0.5 = 50/50. |
| Countries | Select one or more. Only countries with available proxies appear in the list. |
| Timezone | Traffic is evenly distributed across your timezone's day. Pick the one that matches your audience. |
| Referrer URLs (optional) | If set, the first pageview's referrer is picked from this list (e.g., https://google.com). |
| Enabled | Toggle on to start delivery once created. |
Randomizes daily session count by ± this percentage so numbers don't look identical each day. Good default: 0.1 (10%).
Scale traffic per weekday. Default is 100% every day. Drop weekends to 60% if your audience is B2B, for example.
How credits are charged: 1 credit = 1 delivered pageview. A session visiting 3 pages costs 3 credits. If a visit fails (proxy error, site down, etc.), you're not charged. Your campaign auto-pauses if your balance runs out.
Traffic starts arriving within about 15 minutes. Dispatch happens every 15 minutes in 4 waves per hour, spread randomly across the window so bursts look natural.
From Browser Simulation → Campaigns, click Report next to any campaign. You'll see:
All times shown are in the campaign's configured timezone.
To confirm traffic is landing where you expect, check any of:
Note: our browsers block heavy media (images, video, fonts) to keep delivery fast. Pageviews and script execution are preserved.
Under 100 sessions/day spreads very thinly. If you want noticeable volume within the first hour, aim for 500+ sessions/day.
Setting max pageviews = 5 on a site with few internal links wastes browser time. Match it to your typical sitemap depth.
Check if your site blocks data-center or residential IP ranges, has Cloudflare "Under Attack" mode on, or requires a cookie banner click. Failed visits aren't charged, but they reduce your effective throughput.
Set bounce rate to 1. Every session then visits exactly 1 page.
Sometimes — the browser runs your GA4 JavaScript. But GA4 bot filtering may exclude it. If GA4 visibility is your goal, use our GA4 service instead.
Yes. Edit the campaign and toggle Enabled off. Credits stay in your account.
Our workers block ad scripts and heavy media by default specifically to avoid ad-impression generation. You should not see traffic counted as ad views.
No hard limit. All active campaigns share your credit balance. If you want strict per-campaign budgeting, set Sessions Per Day explicitly and monitor the report.
Cancelling stops future monthly top-ups. Any credits remaining in your balance stay usable until spent.
Create an account, pick a plan, and send your first visits in under 10 minutes.