Send natural-looking events straight into your GA4 property — with country, city, device, and UTM control.
GA4 Traffic sends events directly to your Google Analytics 4 property using the official Measurement Protocol. Events are fired through residential IPs from the countries and cities you pick, so they appear in GA4 as genuine page views — with location, device, and UTM attribution.
This is the right service when your success metric lives inside Google Analytics (reports, acquisition, audiences). If you want traffic that hits your server and shows up in logs or other analytics tools, use Browser Simulation instead.
Measurement Protocol v2 with session identifiers, device, screen size and user-agent headers.
Residential proxies match your target location — GA4 reports the configured geo.
Full control over source, medium, campaign, and content parameters.
GA4 campaigns run on Google Analytics Credits. Each event sent to GA4 costs 1 credit. Credits are deducted at dispatch time.
Create your account at trafficbot.co/register and verify your email. Every new account gets 100 free GA4 credits — enough to run a real campaign and confirm events hit your property before you commit to a plan.
From the sidebar, go to Google Analytics Traffic → Buy Credits. Monthly plans:
| Plan | Credits / month | Price |
|---|---|---|
| Mini | 15,000 | $9 |
| Starter | 65,000 | $29 |
| Growth | 320,000 | $119 |
| Business | 650,000 | $189 |
Monthly recurring via PayPal. Credits never expire and roll over.
Click the plan, approve on PayPal, then you'll be redirected back. Your credit balance updates immediately and shows at the top of the dashboard as Google Analytics Credits.
Go to Google Analytics Traffic → Campaigns → New Campaign. You'll need your GA4 Tracker ID and at least one URL to start.
Before you start: find your GA4 Tracker ID in Google Analytics under Admin → Data Streams → Web → Measurement ID. It looks like G-XXXXXXXXXX.
| Field | What to enter |
|---|---|
| Name | Any label (e.g., "US organic campaign"). |
| Tracker ID | Your GA4 Measurement ID (G-XXXXXXXXXX). |
| Events Per Day | 1–5,000. Under 100/day can look unnatural on most properties. |
| Bounce Rate | 0–1. Share of visitors who see only one page. 0.25 = 25%. |
| Event Duration | 5–300 seconds. Max on-page time used for engagement. |
| Device Rate | 0 = all desktop, 1 = all mobile. |
| Countries & Cities | Add country (e.g., US) or country+city (US:New_York). Mix and match across your target regions. |
| URLs | One or more page URL + title pairs. Each URL becomes a page-view event. |
| Timezone | Events are evenly distributed across your timezone's day. Match your audience. |
| Enabled | Toggle on to start delivery. |
1–50. Caps how many pageviews a single visitor generates within one session. Default 10 is a safe middle ground.
Randomize daily event count and page duration by ± this percentage. 0.1 = 10% jitter.
Set Source, Medium, Campaign, Content — they show up in GA4 under Acquisition → Traffic acquisition. Useful for attribution testing (e.g. chatgpt.com / referral).
Scale volume per weekday (0–100%). Match natural traffic patterns — e.g. drop Sundays if B2B.
How credits are charged: 1 event = 1 credit, deducted when the event is dispatched. Your campaign auto-deactivates if your balance hits zero. Each visitor may generate multiple events depending on bounce rate and max events per visitor.
Events start firing within a few minutes. Dispatch runs every 10 minutes (6 waves per hour), with delays randomized inside each window.
To see events as they arrive, open GA4 and go to:
Standard (non-realtime) reports normally take 24–48 hours to finalize. Use Realtime to confirm the campaign is wired correctly right after launch.
From Google Analytics Traffic → Campaigns, click Report next to any campaign:
Note: our dashboard counts events dispatched. GA4 counts events accepted into your property. A small difference is normal.
Double-check the G-XXXXXXXXXX. A typo silently sends events to a different property (or nowhere). Run 100 free credits first to confirm.
GA4 happily accepts any URL in an event, but your reports will look strange if you send URLs that don't exist on your site. Use URLs from your real sitemap.
Very low volume can look artificial (e.g., exact hourly bursts). Add Fluctuate Event Rate of 10–20% to smooth the pattern, or set higher volume.
If events don't appear, confirm your GA4 property has no internal-traffic filter or bot exclusion that's catching our IPs. Realtime is the fastest way to debug.
Running two campaigns — one for US desktop, one for EU mobile — gives cleaner GA4 reports than one large mixed campaign.
Events arrive alongside your organic data. To keep analysis clean, tag campaigns with a recognizable UTM Campaign (e.g. test_ga_traffic) so you can segment or exclude them later.
Check: (1) Tracker ID is correct, (2) the campaign is Enabled, (3) you have credits, (4) first dispatch window has passed (up to 10 minutes). Still nothing? Open a support ticket.
Yes. In the country selector, type a country + colon + city (e.g. US:New_York). Availability depends on our residential proxy network for that location.
No. UA was sunset by Google in July 2023 and no longer accepts data. We only support GA4 (tracker IDs starting with G-).
Yes. Cancelling stops future top-ups. Any remaining balance stays until spent.
Create an account and run a real campaign before paying anything.