The Operator's Guide to Briefing a Website Views Campaign

Most website views campaigns underperform not because the traffic was low quality but because the person buying it never specified what good looked like. Volume targets, delivery windows, geographic filters, and acceptable bounce thresholds are all negotiable — but only if you state them upfront. Leave them blank and you get defaults, and defaults are set for the median buyer, not your funnel.

The brief is also your audit trail. When you pull campaign reporting at the end of a flight and something looks off — a spike on day one, a geo skew you didn't ask for — you need a written record of what was ordered to diagnose whether the problem is delivery or expectation. Without a brief, every post-campaign conversation becomes a he-said-she-said.

These three inputs drive every downstream decision. Volume is your total view target: a 50,000-view package is a fundamentally different operational object than a 500,000-view package. Window is how many calendar days the delivery should span. Velocity is the shape of delivery within that window — flat, front-loaded, or ramped. A product launch wants front-loading; an evergreen SEO page wants a flat drip over 14 to 21 days so engagement signals look organic to analytics tools.

A concrete example: a SaaS founder running a paid social retargeting test might brief 75,000 website views over 10 days with a flat velocity, capped at 8,000 per day, targeting US and CA only. That single paragraph eliminates four of the most common delivery disputes before the campaign starts.

When you use the scaler surface to configure volume, the daily cap field enforces velocity automatically. Set it. If you leave it uncapped, the system will deliver to time-of-day demand curves, which may not match your server capacity or your analytics baseline.

Geo, device type, and traffic source category should be treated as hard constraints in your brief, not suggestions. If your landing page converts only on desktop because of a form UX issue, briefing mobile traffic is actively harmful. If your attribution model only trusts direct and referral sources, say so. These are operational facts about your funnel, and the campaign should be configured to match them.

Audience growth goals and traffic quality goals are different things. If you are trying to grow a new audience segment — say, expanding from US-only to DACH markets — your brief needs to specify that the new geo is intentional and that your reporting baseline will reflect a mixed audience for the duration. That context prevents your analytics team from flagging the geo diversification as an anomaly and pausing spend mid-flight.

Specify which metrics constitute success before the campaign runs. For a website views campaign, the primary metric is delivered views against target. Secondary metrics typically include session duration floor (e.g., no credit for sessions under 8 seconds), bounce rate ceiling, and geo compliance percentage. If you need third-party verification — a screenshot from your own analytics, a UTM-tagged segment export — state that in the brief so tracking can be set up before day one.

The promotion dashboard surfaces delivered volume, daily pacing, and geo breakdown in real time. Brief your team on which of those numbers they are responsible for monitoring and at what frequency. A 10-day campaign should have a human check at day 3 and day 7 at minimum. Catching a pacing error on day 3 means you still have 70% of the flight to correct it; catching it on day 9 means you are writing a refund request.

Document your UTM structure in the brief. The standard format — source, medium, campaign, content, term — should be pre-filled before any link is shared with a traffic partner. Retroactive UTM cleanup is painful and often incomplete, especially if sessions have already been attributed to direct.

A brief without a sign-off process is a suggestion. Assign one internal owner who can approve mid-campaign changes, and define what constitutes a change that requires re-approval versus a minor adjustment a campaign manager can make unilaterally. Pausing delivery for 12 hours because of a site incident is a unilateral call. Shifting 30% of volume to a new geo mid-flight is not.

Build a version number into your brief document. When you brief a 50,000-view campaign and then expand it to 80,000 views after seeing early results, that is brief v2, not an update to v1. Version control prevents the most common billing disputes: mismatched volume between what was invoiced and what the buyer remembers ordering.

A workable website views campaign brief needs seven fields: (1) total view target, (2) campaign start and end date, (3) maximum daily delivery cap, (4) accepted geographies ranked by priority, (5) accepted device types, (6) UTM parameters pre-built, and (7) success metrics with explicit thresholds. Everything else — creative context, brand safety notes, escalation contacts — is useful but not blocking.

For agencies running multiple client campaigns simultaneously, this template should live in a shared system that connects to your promotion dashboard so delivery data and brief data are co-located. When a client asks 'are we on pace?', the answer should come from a dashboard view, not a mental calculation. Brief structure and reporting infrastructure are the same problem viewed from opposite ends of the campaign timeline.