Writing a Website Views Campaign Brief That Actually Gets Delivered Right

The single most common reason a website views campaign underperforms is not the channel or the creative — it is an incomplete brief handed off to the operator running the promotion. Missing fields get filled in by whoever processes the order, and their defaults are rarely yours. A campaign targeting a SaaS pricing page will be treated identically to one targeting a blog post unless you say otherwise.

A working brief is not a creative document. It is a logistics document. It answers five questions before money moves: what URL receives traffic, what volume is required, over what time window, from what geography, and what reporting signal confirms the delivery. Every field left blank becomes a decision made without you.

Start with the destination. Write the exact URL including any UTM parameters you need preserved. If you are running a 50,000-view package to a product landing page, the brief should specify whether direct traffic, referral traffic, or a specific source label is required in your analytics. Operators cannot infer this from the URL alone.

If you have URL variants — for example, a canonical page that redirects to a localized version — flag them explicitly. Redirects can strip UTM parameters depending on the implementation, which breaks attribution downstream. Clarifying this in the brief takes thirty seconds and saves a support ticket a week later.

Also note whether the target page has any access restrictions: password gates, geo-blocks, age verification layers, or bot-detection scripts that may interfere with delivery. A brief that omits this invites a partial fill with no clean explanation in the dashboard.

Volume and pacing are not the same instruction. Ordering 100,000 views is a volume decision. Specifying that those views should arrive over seven days at roughly 14,000 per day is a pacing decision. Conflating the two — writing only '100k views' — defaults to whatever the platform's standard delivery curve looks like, which is often front-loaded.

Front-loaded delivery is sometimes correct: a product launch on day one benefits from a spike. A content SEO play, however, wants a gradual ramp that mimics organic discovery patterns. Be explicit. In the brief, write something like '50,000 views over 72 hours, even distribution preferred' or '200,000 views over 30 days, accelerate in week three to coincide with paid media push.' The scaler surface lets you adjust volume targets mid-campaign, but pacing corrections after delivery starts are harder to execute cleanly.

If you have hard stops — a campaign that must complete before an earnings call or a product sunset date — write that deadline into the brief as a constraint, not a preference. Constraints get actioned; preferences get deprioritized under load.

Geography is the most under-specified field in the average website views campaign brief. Writing 'US traffic' is not a geo spec. It tells an operator nothing about whether Tier 1 cities are required, whether Puerto Rico counts, or whether Canada can be used as overflow if US inventory is constrained. Write the ISO country codes and, where relevant, the state or metro level.

If your campaign has audience-quality requirements — returning visitors excluded, mobile-only, desktop-only, a specific referral category — those belong in the brief as hard requirements, not in a post-launch email. The promotion dashboard will show you the delivery breakdown by device and source after the fact, but adjustments made after delivery has started often affect only the remainder of the order.

For B2B campaigns targeting a specific vertical, include the intended audience descriptor even if the platform cannot guarantee it. It creates an audit trail. If delivery underperforms against your KPI, you have documented what was requested versus what was delivered.

Reporting is not an afterthought. If you need a screenshot of the promotion dashboard at 50% delivery and again at completion, write that into the brief. If you need a CSV export tagged to your client's campaign ID, specify the format. Operators running volume at scale cannot customize reporting retroactively for every order unless it was agreed upfront.

Specify your analytics source of record. If your client measures traffic in their own analytics platform and expects numbers to reconcile within a defined tolerance — say, within 15% of the ordered volume — that threshold needs to be in the brief. Discrepancies between platform-reported views and client-side analytics are normal due to ad blockers, JavaScript failures, and sampling; what matters is that both parties agreed on the acceptable range before the campaign ran.

Audience growth metrics — session duration, pages per visit, bounce rate on the landing page — are useful signals to include even if they are not the primary KPI. They help diagnose delivery quality issues faster than raw view counts alone.

Standardizing your brief format across every website views campaign brief your team produces has a compounding return. The first brief you write from scratch takes forty minutes. The tenth brief written from a template takes eight. More importantly, a template enforces completeness — every required field is present, even if some answers are 'not applicable.'

A minimal working template contains: target URL with UTM string, ordered volume, delivery window with start and end dates, pacing preference, geo spec at country level minimum, device split if relevant, reporting cadence and format, analytics source of record, and any hard constraints. That is nine fields. Any brief missing more than two of them should be sent back before it is submitted.

Teams managing multiple clients benefit from keeping brief versions in a shared document with a change log. When a campaign is queried weeks later — by a client, an auditor, or a new team member — the brief is the primary record of what was intended. Delivery data from the dashboard tells you what happened; the brief tells you what was asked for.