Workflow Settings

Introduction

Workflow Settings allow you to configure how your workflow is distributed and limit its execution. These settings help you:

Target specific countries for your workflow
Control the execution speed
Select target devices (desktop, mobile, tablet)
Prevent spam and protect your token budget

Workflow settings

{info} Access: Open Workflow Settings by clicking the "Settings" button on the workflow details page or when creating a new workflow.

Targeting & Distribution

Country Mode

Choose how the workflow is distributed by country:

Mode	Description	When to Use
All Countries	Workflow can be run from any country	Want diverse global traffic
Include Only	Only allow countries in the list	Only want traffic from specific countries (VN, US, UK...)
Exclude Only	Block countries in the list	Want global traffic EXCEPT for specific countries

Example:

Case 1: Vietnamese website
→ Mode: Include Only
→ Select: VN
→ Result: Only Vietnamese IPs run the workflow

Case 2: International website, avoid Chinese traffic
→ Mode: Exclude Only
→ Select: CN
→ Result: All countries EXCEPT China

{warning} Plan Requirement: This feature requires a Basic plan or higher. Free plans are restricted to "All Countries".

Select Countries

When "Include" or "Exclude" mode is selected, you need to choose the list of countries:

How to select:

Search: Type the country name or code (VN, US, UK...)
Check: Click the checkbox next to the country name
Select Group: Use quick group buttons (SE Asia, Europe, English Speaking...)
View Selected: Toggle "Selected Only" to show only chosen countries
Clear All: Click "Clear All" to deselect everything

Country Groups

Quick-select groups available:

Group	Countries	Count
SE Asia	VN, TH, MY, SG, ID, PH, MM, KH, LA, BN, TL	11
English Spk	US, GB, CA, AU, NZ, IE, ZA, IN, PK, NG	10
Europe	GB, DE, FR, IT, ES, NL, BE, AT, CH, SE, NO, DK, FI, PL, PT, GR, CZ, HU, RO	19
North America	US, CA, MX	3
East Asia	CN, JP, KR, TW, HK, MO	6

Tip: Click a group to select all countries in that group at once!

Execution Limits

These limits help control the speed and volume of workflow execution.

Views Per Hour

Description: The maximum number of views the workflow can run in 1 hour.

Value:

0 = Unlimited
> 0 = Specific limit (e.g., 100 views/hour)

How it works:

You set: views_per_hour = 50

Workflow starts running at 10:00 AM
→ 10:00 - 11:00: Max 50 runs
→ 11:00 - 12:00: Resets, max 50 runs again
→ 12:00 - 13:00: Resets, max 50 runs again

When to use:

Want steady traffic, avoid spikes
Prevent Google from detecting abnormal traffic
Control the growth rate of traffic

Example:

Case 1: New website, natural traffic
→ views_per_hour = 20
→ Reason: Avoid sudden jumps, simulate natural growth

Case 2: Large website, needs fast traffic
→ views_per_hour = 200
→ Reason: Can handle high traffic without suspicion

Views Per Day

Description: The maximum number of views the workflow can run in 1 day (24 hours).

Value:

0 = Unlimited
> 0 = Specific limit (e.g., 1000 views/day)

How it works:

You set: views_per_day = 500

Day 1 (00:00 - 23:59): Max 500 runs
Day 2 (00:00 - 23:59): Resets, max 500 runs again

When to use:

Control daily token budget
Limit traffic to mimic real users
Avoid spamming too many views

Example:

Case: Budget of 50,000 tokens/day
Workflow cost: ~100 tokens/run
→ views_per_day = 500 (500 x 100 = 50,000 tokens)

Maximum Views

Description: The total number of views for the entire workflow lifecycle.

Value:

0 = Unlimited (runs forever)
> 0 = Specific limit (e.g., 10,000 total views)

How it works:

You set: max_views = 10000

Workflow runs cumulatively:
→ Day 1: 500 views (total: 500)
→ Day 2: 800 views (total: 1,300)
→ ...
→ Day 20: 400 views (total: 10,000) → STOPS PERMANENTLY

When to use:

Campaigns with a deadline
Control total budget
Avoid workflows running more than necessary

Example:

Case: Boosting traffic for a new post
Goal: 5,000 views in 1 month
→ max_views = 5000
→ Result: After reaching 5,000 views, the workflow stops automatically

{danger} Warning: After reaching max_views, the workflow will STOP PERMANENTLY. You need to increase the value or set it back to 0 to continue running.

Unique Interval

Description: The minimum time (in seconds) between 2 executions from the same IP address.

Note: Each IP can run multiple different workflows simultaneously (up to 30 threads), but each specific workflow can only run once per unique_interval for that IP.

Default value: 1800 seconds (30 minutes)

How it works:

You set: unique_interval = 1800 (30 minutes)

IP Address 192.168.1.1:
→ 10:00 AM: Thread 1 runs workflow #100 → OK
→ 10:05 AM: Thread 2 tries to run workflow #100 → BLOCKED (same IP, not yet 30 mins)
→ 10:05 AM: Thread 2 runs workflow #101 → OK (different workflow)
→ 10:30 AM: Thread 1 runs workflow #100 for the 2nd time → OK (30 mins passed)

Explanation:

The same IP cannot run the same workflow twice within 30 minutes.
But it can run many DIFFERENT workflows simultaneously.

Purpose:

Track by IP address: Matches how Google Analytics tracks visitors.
Prevent spam: Same IP can't spam the same URL in a short period.
Support multi-threading: Each IP can run 30 threads, with each thread running a different workflow.
Realistic traffic: In 30 minutes, 1 IP can run ~180 different workflows (30 threads × 6 workflows/thread).
Rotating proxy: New IP = new visitor, no limit.

Recommendations:

Workflow Type	unique_interval	Reason
Homepage, landing page	3600s (1 hr)	Real people rarely return within 1 hr
Blog post	1800s (30 min)	Can be re-read after 30 mins
E-commerce product	7200s (2 hrs)	Buyers usually compare longer

Example:

Real-world case: 100 IP addresses, each with 30 threads
The system has 1000 different workflows
unique_interval = 1800 (30 minutes)

Each IP:

- 30 threads running simultaneously
- Each thread: 1 workflow/5 mins = 12 workflows/hr
- Total per IP: 30 × 12 = 360 workflows/hr
- In 30 mins: 30 × 6 = 180 different workflows

100 IPs:
→ Throughput: 100 × 360 = 36,000 workflows/hr
→ Diverse traffic: 100 IP × 180 workflows = 18,000 combinations per 30 mins
→ Each workflow is executed by many different IPs

Additional Settings

Devices

Description: Choose the types of devices that the workflow can run on.

Options:

🖥️ Desktop - Computers (Windows, Mac, Linux)
📱 Mobile - Mobile phones (iOS, Android)
📱 Tablet - Tablets (iPad, Android Tablet)

How it works:

When an app instance runs a workflow, the system will:

Randomly pick 1 device from your selected list.
Simulate that device (user agent, screen size, touch events...).
Run the workflow with the selected device.

Example:

You select: Desktop + Mobile

Run 1 → System picks Desktop
Run 2 → System picks Mobile
Run 3 → System picks Desktop
...
→ Diverse traffic between desktop and mobile

Recommendations:

Website Type	Recommended Devices	Reason
Blog, News	Desktop + Mobile	50/50 mixed traffic
E-commerce	Mobile (70%) + Desktop (30%)	Shopping trend on mobile
SaaS, Dashboard	Desktop	Users mostly use desktop
Mobile games	Mobile	100% mobile traffic

{warning} Plan Requirement: This feature requires a Basic plan or higher. Free plans default to running on all 3 devices.

{info} Note: At least 1 device must be selected. If none are chosen, the system defaults to Desktop + Mobile.

Plan Restrictions

Certain Settings features require higher plans:

Feature	Free	Basic	Pro	Enterprise
Country Mode	All	All/Include/Exclude	All/Include/Exclude	All/Include/Exclude
Device Selection	All	Customizable	Customizable	Customizable
Execution Limits	✅	✅	✅	✅

If using features not in your plan:

The system will apply default values.
A notification to upgrade your plan will be displayed.

Frequently Asked Questions

❓ What limits should I set for a new website?

Safe recommendation:

views_per_hour = 10-20
views_per_day = 100-200
unique_interval = 3600 (1 hour)

Reason: New websites should increase traffic gradually to avoid suspicion from Google.

❓ What is the difference between views_per_hour and views_per_day?

views_per_hour: Limits SPEED (avoids sudden spikes in 1 hour). views_per_day: Limits TOTAL VOLUME (controls daily budget).

Example:

views_per_hour = 50
views_per_day = 500

→ Max 50 runs per hour
→ Max 500 runs per day
→ If running steadily: 50 runs/hr x 10 hours = 500 runs/day

❓ What if I set views_per_hour = 100 but views_per_day = 500?

The system will prioritize whichever limit is reached first:

Hour 1: 100 runs (total: 100)
Hour 2: 100 runs (total: 200)
Hour 3: 100 runs (total: 300)
Hour 4: 100 runs (total: 400)
Hour 5: 100 runs (total: 500) → DAILY LIMIT REACHED
Hours 6-24: STOPPED (daily limit reached)

❓ Can I change settings while a workflow is running?

YES! You can change settings at any time:

Changes apply IMMEDIATELY to subsequent runs.
Runs already in progress are NOT affected.

❓ When does unique_interval reset?

unique_interval is calculated from the last run of each IP address:

IP Address 192.168.1.1:
→ Runs workflow #100 1st time: 10:00 AM
→ unique_interval = 1800s (30 minutes)
→ Can run workflow #100 again: 10:30 AM

Note: This IP can still run OTHER workflows (101, 102, ...) during the wait.

It DOES NOT RESET by day/time like views_per_hour or views_per_day.

❓ Does unique_interval track by instance or IP? How does it affect multi-threading?

It tracks by IP ADDRESS, not instance ID.

Multi-threading:

1 IP can open up to 30 threads simultaneously.
Each thread can run a DIFFERENT workflow.
But it CANNOT run the same workflow twice within the unique_interval.

Example:

IP 192.168.1.1 with 30 threads (10:00 AM):
Thread 1: Runs workflow #100 → OK
Thread 2: Runs workflow #101 → OK
Thread 3: Runs workflow #102 → OK
... (30 threads running 30 different workflows)

Thread 5: Tries to run workflow #100 (already run by Thread 1) → BLOCKED
→ Reason: Same IP, workflow #100 hasn't cleared unique_interval.
Thread 5: Runs workflow #131 → OK (workflow not yet run)

10:35 AM (after 35 mins):
Thread 10: Runs workflow #100 again → OK (30 mins passed)

❓ What does views_per_hour = 0 mean?

0 = UNLIMITED

views_per_hour = 0 → Unlimited runs per hour
views_per_day = 0 → Unlimited runs per day
max_views = 0 → Runs forever

❓ Does selecting more countries cost more tokens?

NO. The number of countries does not affects token cost.

Cost only depends on:

Number of nodes in the workflow
Wait time
Priority multiplier

❓ A workflow reached max_views, how do I continue?

Method 1: Increase the max_views value. Method 2: Set it to 0 (unlimited). Method 3: Reset total_views to 0 (contact admin).

❓ Why is my workflow not running even though it hasn't reached its limits?

Check these conditions:

Workflow Status: Must be "Active".
Tokens: Account must have enough tokens.
Hourly/Daily Limits: Might have reached the limit.
App instances: Are any app instances online?
Countries: Do online app instances match the country_mode?

Summary:

Workflow Settings help control distribution and speed of execution.
Reasonable limits make traffic more natural and save tokens.
You can change settings at any time without stopping the workflow.
Some features require a Basic plan or higher.

⚠️ System Update

Getting Started

Features

Workflow

Traffic4SEO App (Executor)

CLI (Command Line Interface)

About Traffic4SEO

Legal Information

Workflow Settings

Introduction

Targeting & Distribution

Country Mode

Select Countries

Country Groups

Execution Limits

Views Per Hour

Views Per Day

Maximum Views

Unique Interval

Additional Settings

Devices

Plan Restrictions

Frequently Asked Questions

❓ What limits should I set for a new website?

❓ What is the difference between views_per_hour and views_per_day?

❓ What if I set views_per_hour = 100 but views_per_day = 500?

❓ Can I change settings while a workflow is running?

❓ When does unique_interval reset?

❓ Does unique_interval track by instance or IP? How does it affect multi-threading?

❓ What does views_per_hour = 0 mean?

❓ Does selecting more countries cost more tokens?

❓ A workflow reached max_views, how do I continue?

❓ Why is my workflow not running even though it hasn't reached its limits?

Next Steps