How to Create a Targeted Website Traffic Campaign with Serplify

A website traffic campaign is useful when you give it a clear job. It can help you check whether GA4 sees a landing page, test how a site behaves under steady visits, inspect geo and device reporting, or validate a multi-page path before you buy ads.

It cannot prove customer demand. It should never be mixed into revenue reporting as if every visit came from an interested buyer.

This guide shows how to create a targeted Serplify Website Traffic project in the app, tune the important settings, and verify the delivery without confusing test visits with real growth.

Start with a test goal

Pick one goal before you open the campaign form.

Good first goals include:

• confirm that GA4 records a landing page and its events;
• check whether a country and device mix appears as expected;
• test page speed and server stability under steady visits;
• validate UTM tags, referral attribution, or an internal page path;
• make sure a new funnel page works before paid advertising begins.

“Get more traffic” is too broad. A useful goal says what you will inspect and what result passes the test.

For example:

Send a small, distributed mobile campaign to our new pricing page from the United States. Confirm that the landing page, scroll event, and signup-button event appear in GA4 without errors.

Step 1: prepare the target page

Open the page on a phone and a desktop before sending traffic. Fix obvious errors first.

Check that:

• the page loads over HTTPS;
• the final URL is correct after redirects;
• the consent banner does not block the page;
• GA4 or Google Tag Manager loads as intended;
• important buttons and forms work;
• internal links lead to real, public pages;
• your hosting can handle the planned pace.

Use a dedicated landing page when possible. It gives the test a clear boundary and makes the traffic easier to find in analytics.

Step 2: create the project

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

1. Select New Project.
2. Choose Website Traffic.
3. Add a clear project 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. Create the project.

A domain target allows visits to pages across the domain. A full URL creates a tighter page-level test. For most first campaigns, use the exact page you plan to inspect.

Traffic projects spend your prepaid balance and require one completed top-up. The Website Traffic rate is $0.002 per delivered visit, or $2 per 1,000 delivered visits. Serplify bills delivered results, not the number you hoped to receive.

Step 3: choose the traffic source

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

You can choose direct, organic, social, or a custom referral URL. The source controls the referrer on the first navigation. If the visit opens another page on your site, that page uses a normal same-site referrer.

Choose the source based on the report you need to test:

For a custom source, enter the full HTTP or HTTPS URL, including the protocol. Serplify previews the Referer value before you save.

Do not choose a label just because it looks good in GA4. The label should match the test you are running. Analytics categories are measurement fields, not proof that an interested person came from that platform.

Step 4: set country, device, and daily volume

The country controls the IP location used for delivery. The device can be desktop, mobile, or mixed.

Match these settings to the real audience and page design you want to test. A mobile checkout QA test should not use a desktop-only plan. A country-specific landing page should use that country’s traffic and timezone.

Start small. A short test of 100 visits teaches you more than a large campaign you cannot explain. Check the page and analytics first, then raise the target if the setup is correct.

Step 5: choose immediate or distributed delivery

Continuous projects support two execution modes:

• Immediate starts now and works inside a bounded execution window.
• Distributed spreads visits through the selected schedule and peak hours.

Use Immediate for a short technical check, such as confirming that a page loads and an event fires. Use Distributed when you want a steadier traffic pattern or need to watch performance over a day.

You can also set:

• a daily schedule;
• primary and secondary peak windows;
• a minimum gap between visits;
• a warm-up period;
• a weekend reduction;
• the target timezone.

These controls shape delivery. They do not make test traffic equal to customer demand. Keep that difference clear in every report.

Step 6: set visit behavior for the page

Serplify lets you configure ranges instead of one identical session pattern.

Important controls include:

• minimum and maximum visit duration;
• minimum and maximum pages per visit;
• scroll depth range;
• scrolling on or off;
• internal navigation on or off;
• bounce rate.

Use the simplest behavior that matches the test.

If you only need to confirm a landing-page view, one page and a short duration may be enough. If you need to test a two-page funnel, enable internal navigation and use at least two pages per visit. Do not configure five-page sessions when the site has no natural five-page path.

Bounce rate is a planning control, not a quality score. A single-page article can satisfy a reader and still count as a bounce under some measurement definitions. Judge the session against the page’s purpose.

Step 7: keep the GA4 data separate

Test traffic should be easy to find and easy to exclude from business reports.

Use at least two of these layers:

1. a dedicated landing-page path;
2. a clear project and campaign naming rule;
3. a separate GA4 property for pure QA;
4. report comparisons or explorations that isolate the test period and page;
5. notes in your analytics or experiment log.

If you add UTM parameters to a target URL, use consistent values such as:

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

Google explains how UTM parameters appear in the Traffic acquisition report in its campaign URL guide. Keep the names lowercase and predictable so small spelling changes do not split one campaign into several rows.

Do not turn on a permanent GA4 exclusion filter until you have tested it. Google’s internal-traffic filter documentation warns that active exclusions permanently remove matching data from processing. A report-level comparison or separate test property is safer when the traffic cannot be marked by a fixed office IP.

Step 8: launch and watch delivery

Save the configuration, return to the project overview, and start the project.

The project card and detail page show:

• delivered visits;
• the daily target;
• remaining visits;
• average duration;
• a delivery timeline;
• the current running, paused, idle, or stopped state.

The Tasks tab shows delivered work and work still in progress. Failed attempts are handled inside the delivery system and are not counted as successful visits.

You can pause a project, change future settings, and resume. Stop ends delivery. If the balance runs out, delivery pauses instead of spending past the available credit.

Step 9: verify the result in GA4

Open Reports → Realtime in Google Analytics. The Realtime report can show active users, pages, sources, and event counts from the last 30 minutes. Google notes that attribution is limited in Realtime, so use Acquisition reports later for the most accurate source analysis. See Google’s Realtime report guide.

Check these items:

• Does the target page appear?
• Do the expected events fire?
• Does the device category match?
• Does the country appear within a reasonable tolerance?
• Does the source or campaign label appear later in Traffic acquisition?
• Are there JavaScript, consent, or tag errors on the page?

Serplify delivery totals and GA4 totals may not match exactly. Consent settings, blockers, timezones, reporting delays, filters, and analytics rules can all change what GA4 processes. Use delivery logs to confirm the visit work and GA4 to confirm your measurement setup.

Our full GA4 website traffic verification guide walks through this audit in more detail.

Common setup mistakes

• Sending a large campaign before a small QA run. Test the plumbing first.
• Using the homepage for every test. A dedicated page is easier to inspect.
• Treating an analytics source label as proof of user intent. It only describes attribution.
• Changing the page during the test. Record changes or pause first.
• Using an impossible browse path. Match pages and duration to the real site.
• Mixing test visits with customer KPIs. Keep QA and growth evidence separate.

A safe first campaign

For a simple GA4 page test, try:

• exact landing-page URL;
• 100 visits;
• one country;
• mobile or desktop, not mixed;
• distributed delivery over several hours;
• one to two pages per visit;
• a short, realistic duration range;
• a clear project name and UTM campaign label.

Verify that small run. Save screenshots or exports of the Serplify project and GA4 report. Only then decide whether more volume serves a real testing goal.

That is the useful way to buy targeted website traffic: begin with a question, control the variables, inspect the evidence, and keep the result in the right reporting box.