Traffic Generator: Real Browser Visits, Billed per Session

Traffic Generator delivers automated browser sessions to a site you control, shaped to a behavior profile you define. What changes is measurable: session count, the source mix in your acquisition report, bounce rate, pages per session, average duration and the share of returning visitors.

What does not change is equally definite. These sessions belong to nobody, so they produce no leads, no signups and no sales. They carry no ranking guarantee either: behavioral data is one input among many, search engines discount signals they judge to be artificial, and the effect varies by site, query and engine.

Because a real browser opens the page, executes its JavaScript and downloads its assets, the visit is written to your server access log and your CDN reporting, not only to your analytics property. You can reconcile the three against each other for the same time window.

That reconciliation is worth doing whichever service you use. If a traffic service can only demonstrate delivery inside one analytics property, you are trusting a single number that a vendor is in a position to write to directly. Your own access logs are the check that does not depend on the vendor.

Direct sessions arrive with no referrer, as though the address was typed or opened from a bookmark. Referral sessions carry the referrer of a page you nominate. Social sessions are attributed to a social platform. The choice determines which channel report the sessions land in, so pick the one that matches what you are testing or measuring.

Two sources are deliberately not on this list. Clicks from a search results page for a keyword are SERP Clicks, at $0.09 per click, because a browser has to run the search and find your listing first. Clicks on your existing backlinks are Link Clicker, at $0.003 per click. Traffic Generator does not produce search traffic, and no configuration of it will.

Read your current numbers before you set targets. Open your analytics, note the bounce rate, average session duration and pages per session your site actually records, and configure the campaign near those figures rather than at the values you would prefer to see.

Targets far above the baseline are self-defeating. A site whose real sessions average forty seconds does not become more credible with six-minute sessions; it produces a distribution with two unrelated peaks in it, visible to anyone reading the report, starting with you.

The rate starts at $0.0015 per session and rises with the session duration you configure, because a longer session occupies a real browser for longer. Duration is therefore a cost decision as well as a behavioral one: set it from what your site actually records rather than from what reads well, and the spend follows.

Start at roughly 30 to 50 percent of the traffic the site already receives and increase in steps, checking after each one what moved in your reporting and what did not. A campaign that doubles a site's traffic in a day tells you nothing, because you cannot separate its effect from anything else. Billing runs from an account balance: a $5 minimum deposit, no subscription, and a balance that does not expire and can be refunded. Nothing is charged while a campaign is paused, and both figures that determine the cost, the rate and the volume, are ones you set before it starts.

There is no claim here that the traffic is undetectable, and you should treat that claim with suspicion wherever it is made. Volume and pacing are under your control, which means conspicuous patterns are too: a sudden multiple of your normal traffic is obvious in your own reporting before it is obvious anywhere else.

Point campaigns only at sites you own or are authorised to work on. Do not use the resulting figures to represent audience size to advertisers, partners or investors, who are entitled to numbers that describe real people. And treat the tool as one input beside content, links and technical work rather than as a replacement for any of them.