Traffic Campaigns
Build a session plan (mix, horizon, CTR-gap cap) instead of buying a daily click dump.
A campaign is a plan for one website and a set of keywords. SerpClix-style tools ask for clicks per day. We ask for a mix and a horizon, then cap daily sessions to the CTR gap.
The wizard
Campaigns → New. Five steps.
1. Query
Name the campaign, pick the website, pick keywords that already have a rank (or will after the first check).
Position chooses the situation:
| Position | Situation | What the planner does |
|---|---|---|
| None / >100 | New page | 180-day slow ramp, low floor |
| 11–100 | Climb | 90-day slow ramp |
| 4–10 | Close the gap | 90 days, compare allowed |
| 1–3 | Maintain | Light hold so the window does not age out |
You can override the label, not the math, on Review.
2. Location
- Country: 1× credits
- City: 1.4×, up to a handful of cities
- ZIP (US): 1.8×, neighborhood-level
Local queries lean 70% mobile. National stays 60% desktop / 40% mobile.
One campaign, one location story. Do not blend 33101 and 33139.
3. Session mix
Three outcomes. The worker gets sessionOutcome and dwellSeconds on each job.
| Outcome | Default climb | What happens |
|---|---|---|
| Satisfy | 85% | Land, stay (~180s mean), open ≥2 pages |
| Compare | 0% (10% on close-the-gap) | Competitor first, then you. Short on them, longer on you. |
| Soft miss | 15% | Short stay (~45s). Real streams are not 100% happy. |
Compare is a mix slice, not a separate “negative CTR” toggle with a 1.5× tax. Credits already follow geo × mix.
Long dwell is not 2×.
4. Horizon
Default 90 days. New pages 180. Ramp 21–35 days (14 on maintain). Pattern is slow ramp or natural-growth jitter, not a first-week spike.
The planner also computes:
- Expected CTR for current position
- Target CTR for the next sensible position
- Monthly session gap from volume
- A daily cap (gap, with a 15% volume ceiling)
You can move daily between min and max on Review. You cannot “set 5,000/day because the old tool did.”
5. Review
Credits for the whole horizon. Launch. Unused credits refund if you delete the campaign.
After launch
The campaign card shows status, daily cap, sessions delivered, keyword count.
Detail tabs: overview (mix, geo, horizon), keywords + rank, schedule, session rows (outcome, dwell, pages, geo).
Pause stops new jobs. Resume picks up the next slot. Delete drops history. Use that when you want the credit refund.
How traffic is spread
- Hours follow the campaign timezone
- Weekdays usually carry more volume
- Start times jitter; page dwell is not a fixed timer
- Multi-ZIP / multi-city splits across the list you named
Credits
| Input | Multiplier |
|---|---|
| Country | 1.0× |
| City | 1.4× |
| ZIP | 1.8× |
| Mix | Built into the session cost |
| Long dwell | No extra |
Trial 150. Starter 400 / $49. Pro 2,000 / $149. Agency 8,000 / $399.
What to watch
- Delivery vs daily cap (first)
- Mix actually logged (satisfy vs miss)
- Rank vs the CTR we expected for that position (SearchAPI)
Rank moving 1–4 places in the first two weeks is normal. No movement after 30 days: the query may be the wrong situation, or on-page is broken. Raising daily past the cap is the wrong first lever.
Do not
- Start a new domain at 200 sessions/day
- Turn compare up to 50% on a brand-new URL
- Call SearchAPI ranks “GSC-verified”
- Run spike / “launch week dump”. The planner will not offer it.