How to create a targeted website traffic campaign in Serplify

A website traffic campaign in Serplify sends automated visits to a page you choose. Each visit runs in a real Chrome browser on a residential or mobile IP. It loads the page, runs your GA4 tag, scrolls and can open more pages.

That makes it a tool for tests. You can check that GA4 records a landing page, watch a server under steady visits, or check a funnel before you buy ads. It is not a source of customers. The visits will not read, sign up or buy, so keep them out of revenue reports.

The steps below follow the project form in order and end with a safe first campaign.

Start with a test goal

Pick one goal before you open the form. Good first goals:

• confirm that GA4 records a landing page and its events;
• check that a country and device split shows up as expected;
• test page speed and server load under steady visits;
• check UTM tags, referrer attribution or an internal page path;
• make sure a new funnel page works before ads go live.

“Get more traffic” is too broad. A useful goal says what you will look at and what result passes.

For example:

Send 100 mobile visits from the United States to the new pricing page over six hours. Pass if the page view, scroll event and signup button event all show in GA4 with no errors.

Step 1: get the target page ready

Open the page on a phone and on a desktop first. Fix obvious errors before you send anything.

Check that:

• the page loads over HTTPS;
• the final URL is right after redirects;
• the cookie banner does not block the page;
• GA4 or Google Tag Manager loads;
• key buttons and forms work;
• internal links go to real, public pages;
• your hosting can handle the planned pace.

Use a dedicated landing page when you can. It gives the test a clear edge and makes the visits easy to find in GA4.

Only send visits to a site you own or have permission to test. The acceptable use policy lists the rules.

Step 2: create the project

Sign in at app.serplify.io and open Projects.

1. Select New Project.
2. Choose Website Traffic.
3. Give it a clear name, such as Pricing page, US mobile QA.
4. Enter the target domain or full URL.
5. Set the daily visit target.
6. Choose the country.
7. Select Create project.

A domain target lets visits land on pages across the site. A full URL keeps the test on one page. For a first test, use the exact page you plan to check.

Traffic projects run on your prepaid balance. They start after your first top-up, from $25. The $1 signup credit works for the SERP API only.

Each delivered visit costs $0.002, or $2 per 1,000. Visits that hit a captcha, a block or an error are not charged.

Step 3: choose the referrer source

Open the project and select Configuration. Website Traffic projects have a Traffic source section.

The referrer is the page a browser says it came from. Serplify sends it on the first page load only. If the visit opens another page on your site, that page gets a normal same-site referrer.

For a custom URL, enter the full address with https://. Serplify shows a preview of the Referer value before you save.

Pick the label that matches your test, not the one that looks best in GA4. A source label in GA4 is a measurement field. It does not mean a person came from that site. Our guide to website traffic sources shows how GA4 turns a referrer into a channel.

Step 4: set location, device and daily volume

The country sets the IP location of each visit. In the United States you can narrow it to one state. Some countries also offer a short list of major cities. The app shows only the ones the network can reach right now.

The device can be desktop, mobile or both. Match it to the page you are testing. A mobile checkout test should not run on desktop.

Start small. A test of 100 visits teaches you more than a big batch you cannot explain. Check the page and GA4 first, then raise the target.

Step 5: choose immediate or distributed delivery

Projects have two execution modes:

• Immediate starts now and runs inside a short window.
• Distributed spreads visits across your schedule and peak hours.

Use Immediate for a quick check, such as making sure a page loads and an event fires. Use Distributed for a steady pattern over a day, for example to watch server load.

You can also set:

• a daily start and end time;
• primary and secondary peak hours;
• a minimum gap between visits;
• a warm-up of 1 to 14 days;
• fewer visits on weekends;
• the time zone.

These settings shape delivery. They do not turn test visits into customer demand.

Step 6: set visit behavior

You set ranges, so not every visit looks the same. The main controls:

• shortest and longest visit, in seconds;
• fewest and most pages per visit;
• scroll depth range;
• scrolling on or off;
• internal links on or off;
• bounce rate.

Use the simplest setup that fits the test. To confirm one page view, one page and a short visit are enough. To test a two-page funnel, turn on internal links and set at least two pages per visit. Visits skip login, signup, cart and checkout links.

Bounce rate here is a setting, not a quality score. A one-page article can satisfy a reader and still count as a bounce. Our guide on how to reduce bounce rate explains what GA4 counts.

Step 7: plan how to keep the test separate in GA4

Test visits should be easy to find and easy to leave out of business reports. Use at least two of these:

1. a dedicated landing page;
2. a clear project and campaign name;
3. a separate GA4 property for pure QA;
4. a saved comparison or segment that leaves out the test;
5. a note in your analytics or test log.

Add UTM tags to the target URL with lowercase, consistent values:

?utm_source=serplify_test
&utm_medium=qa_traffic
&utm_campaign=pricing_page_mobile

Google’s campaign URL guide shows where these values appear.

Do not turn on a GA4 data filter until you have tested it. Google’s internal traffic guide warns that an active filter drops matching data for good.

Automated test visits are a kind of bot traffic. Label them clearly so nobody mistakes them for customers later.

Step 8: launch and watch delivery

Save the settings, go back to the project overview and start the project. The project card and detail page show:

• delivered visits;
• the daily target;
• visits left for the day;
• average visit length;
• a delivery timeline;
• whether it is running, paused, idle or stopped.

The Tasks tab lists delivered visits and work in progress. Failed tries are retried inside the system and do not count as delivered.

You can pause a project, change settings and resume. Changes apply to the next visits. Stop ends delivery. If your balance runs out, delivery pauses so you never spend past it.

Step 9: check the result in GA4

Open Reports, then Realtime, in GA4. It shows users, pages, sources and events from the last 30 minutes. Google notes that attribution in Realtime is limited, so check the source later in Traffic acquisition. See Google’s Realtime report guide.

Check:

• Does the target page appear?
• Do the expected events fire?
• Does the device category match?
• Is the country within your tolerance?
• Does your campaign label show up later in Traffic acquisition?
• Are there script, consent or tag errors on the page?

Serplify’s delivered count and GA4’s count will rarely match exactly. Consent, blockers, time zones, delays and filters all change what GA4 records. Our guide on how to check website traffic in GA4 walks through each check and the math.

Common setup mistakes

• Sending a big batch before a small test. Check the plumbing first.
• Using the homepage for every test. A dedicated page is easier to read.
• Reading a source label as intent. It only describes attribution.
• Changing the page during the test. Pause first, or write down the change.
• Setting a browse path the site cannot support. Match pages and time to the real site.
• Mixing test visits into customer numbers. Keep the two apart.

A safe first campaign

For a simple GA4 page test, try:

• the exact landing page URL;
• 100 visits;
• one country;
• mobile or desktop, not both;
• distributed delivery over a few hours;
• one or two pages per visit;
• a short visit length range;
• a clear project name and UTM label.

Check that small run. Save a screenshot or export of the project and of GA4. Then decide whether more volume answers a real testing question.

If you are still comparing providers, run each one through the website traffic quality checklist first. The website traffic page lists every setting and price, and the API docs cover one-time campaigns.