Website traffic quality checklist (10 checks before you pay for visits)

A website traffic quality checklist is a set of questions you answer before you pay for visits. It makes a provider say what it sells, how the visits are made and how you will prove they arrived. Quality is not one score. It is a match between the traffic, your goal and evidence you can check.

For a GA4 test, quality means each visit reaches the right page and fires the right events. For a load test, it means your server gets a known, steady pattern. For sales, it means a person with a reason to care lands on the page.

Use these ten checks on any provider, including us.

1. Write down the goal

Finish this sentence:

We are paying for traffic to ________, and we will know it worked when ________.

Good answers look like this:

• test whether GA4 records the new signup event;
• confirm that a page stays fast during 1,000 visits over four hours;
• check country and device reporting;
• test a landing page path before ads go live.

If the answer is “get sales”, a traffic tool is the wrong choice. Use ads, partners, email or organic search to reach people who might buy.

2. Define the unit you pay for

Traffic pages mix up these words:

• Hit: one request for a file.
• Credit: a unit of payment. One visit can use several.
• Impression: a chance to see an ad or a result.
• Page view: one recorded page load.
• Visit or session: a group of activity in one time window.
• User or visitor: an analytics ID, which may not equal one person.
• Click: a tap on a link or a result.

They are not equal. SparkTraffic’s pricing page says a credit “is a unit of payment, not a visit”. Traffic Masters sells its plans in impressions. We checked both on October 9, 2026.

Ask which unit sets the bill, which unit the dashboard shows and which unit you should see in GA4. Get the answer in writing.

3. Ask how the visits are made

Common methods:

• people who click an ad on another site, such as a banner, native ad or pop-under;
• automated browsers on residential, mobile or datacenter IPs;
• traffic exchanges, where sites trade visits;
• simple HTTP requests that never run a browser;
• analytics events sent from a server.

Each one suits a different test. Trouble starts when a provider calls one method another.

“Real browser” describes software. It does not mean a person used the browser. “Residential IP” describes the network. It does not prove interest. “Shows in GA4” describes measurement. It does not prove a sale.

A good provider explains its method in plain words and says what the traffic is not. For example, Serplify states that each visit is an automated session in a real Chrome browser on a residential or mobile IP. It also says the visits are for testing and are not customers.

4. Check the source label against the real source

GA4 can label a session as direct, referral, social or organic. That label helps you test attribution. It does not tell you the path a customer took.

Ask:

• What referrer is sent on the first page?
• Can I set a full custom referrer URL?
• Do UTM tags survive redirects?
• Do inner pages use a same-site referrer?
• Does “organic” mean a real search and click, or only a label?

Missing UTM tags and redirects can make sessions show as (direct) / (none). Google explains why in its guide to direct traffic in GA4. Our guide to website traffic sources shows how GA4 groups them into channels.

5. Check the targeting limits

Do not settle for “worldwide”. Write down the country, region, city, device and schedule you need.

Then ask how each one works:

• Is the country based on the exit IP?
• Is city targeting a promise or a best effort?
• Does “mobile” mean a phone-sized screen, a mobile browser or a mobile network?
• Which time zone sets the delivery day?
• What happens when a target runs out of supply?

Run your pilot in one country on one device. A mixed global test hides targeting errors.

6. Look at the behavior settings

Behavior should match the page and the test. Useful settings:

• visit length range;
• pages per visit;
• scrolling;
• internal links;
• bounce rate;
• delivery pace;
• schedule and minimum gap.

More settings do not mean better traffic. A five-page, three-minute visit makes no sense on a one-page tool. Start from how your real site is built.

Be wary of any provider that promises perfect numbers. Real data has gaps, bounces, short visits and differences between tools. Our guide on how to reduce bounce rate shows what GA4 treats as a bounce.

7. Ask for two kinds of proof

The provider’s logs and your analytics answer different questions.

Provider proof shows what the service tried and delivered: target, time, country, device, length, pages and status.

Your own proof shows what your site recorded: page views, events, source labels, device, location, errors and server load.

Neither one replaces the other. Use the method in our GA4 traffic check guide to compare both sides.

Remember what a GA4 session proves. It shows that a browser ran your tag. Automated browsers run tags too, so read our page on bot traffic before you treat sessions as people.

8. Read the controls, refund terms and rules

Before you pay, find answers to these:

• Can I pause, resume or stop delivery?
• Can I slow the pace after launch?
• What happens if my page blocks a visit?
• What happens when my balance or plan runs out?
• Am I charged for visits that did not arrive?
• Is a refund based on the provider’s count or on GA4?
• Are ad-funded or third-party sites allowed?
• Must I own the site, or have permission to test it?

Read the acceptable use and refund policies, as well as the pricing page. Some services ban the very use their ads seem to suggest.

9. Compare the full cost, not the biggest discount

Turn every offer into the same unit:

cost per 1,000 = total price / units sold x 1,000

Then add:

• a monthly plan you must keep;
• the smallest pack you can buy;
• extra fees for targeting;
• credits that expire or reset;
• visits that fail or get filtered;
• staff time to set up and check the test.

A $0.30 per 1,000 offer is not cheaper if it sells hits and you need full browser visits. A $20 test is expensive if it teaches you nothing.

10. Run a pilot with a stop rule

Use the smallest test that can answer your goal. Save the page, GA4 and provider numbers before launch.

Write stop rules like these:

• stop if more than 5 percent of visits hit the wrong page;
• stop if expected events are missing after the first 25 visits;
• stop if country or device data is far outside your range;
• stop if the page error rate rises above normal;
• stop if support cannot explain the gap between ordered and delivered units.

A stop rule protects your data and budget. It also turns a hunch like “this looks wrong” into a decision someone else can check.

A one-page provider scorecard

If a provider fails the method, unit, proof or control checks, a low price should not save the deal.

To see this scorecard used on real vendors, read our Traffic Creator alternatives compared on price, unit and method. The shorter SparkTraffic alternatives list shows how to compare a credit price with a visit price.

What a good test report looks like

A strong report is short. It names:

• the goal;
• the target page;
• the exact settings;
• units ordered and delivered;
• the test window and time zone;
• the GA4 pages and events you saw;
• the gaps and likely reasons;
• the decision to stop, fix or scale.

It does not claim that sessions prove rankings, popularity, customers or revenue.

You can run these checks on us too. Our page on test traffic for page and GA4 checks lists the method, the unit and the price in one place.