What a Website Views Campaign Brief Actually Needs to Work

The average website views campaign brief handed to a promotion operator is four lines: a URL, a target number, a budget, and a deadline. That is not a brief. That is a purchase order with missing fields, and every missing field becomes a judgment call made by someone who does not know your business.

The consequences are predictable. Delivery gets front-loaded because the operator defaulted to the fastest pace setting. The audience pool is too broad because no vertical or geo was specified. The reporting comes back showing raw view counts with no baseline, so you cannot tell whether the number is good or bad. Fix the brief first and the rest of the campaign becomes easier to manage.

The sections below map out what a complete brief contains, why each input matters operationally, and how to format it so a promotion dashboard can translate it into actionable delivery parameters without a second round of back-and-forth.

This sounds obvious until you have seen a campaign drive 80,000 sessions to a page that redirects, loads in six seconds on mobile, or sits behind a soft paywall. State the exact destination URL, including any UTM parameters you want pre-attached. Confirm the page resolves correctly in the geos you are targeting before the campaign goes live.

Also note whether the page is behind any authentication or consent gate. A campaign scaler set to push 50,000 views over 48 hours will burn through budget against a page that half the audience cannot actually load. If the page requires a cookie consent click before the view registers in your analytics, say so — it changes how delivery is validated against your own numbers versus platform-reported numbers.

If you are running multiple destination URLs as part of a split test, list each one separately with its own volume allocation. Do not bundle them into a single line item and expect the operator to divide traffic intuitively.

Volume is how many views you want. Velocity is the rate at which they arrive. These are two separate inputs and conflating them is the single most common briefing error. A request for '100,000 views' tells an operator nothing about whether you want them in 24 hours, 7 days, or spread across a month-long content calendar.

Velocity matters because it affects how the traffic looks in analytics, how it interacts with any organic amplification already in motion, and whether the delivery pace stays within the bounds your promotion dashboard flags as normal for your domain. A slow, steady campaign — say, 15,000 views per day over seven days — reads very differently to both algorithms and auditors than a single spike of 105,000 views delivered overnight.

When you write the brief, state both numbers explicitly: total volume and a daily or hourly cap. If you have a hard launch date where a spike is intentional — a product release, a press moment — say that too, and explain the reasoning. Operators can configure burst delivery, but they need to know it is deliberate, not a misconfiguration.

A brief that says 'US traffic' is underspecified. The United States contains audiences with radically different intent signals, device behaviors, and time-zone activity curves. If your page converts best with professionals in EST business hours, that constraint belongs in the brief. If you need traffic skewed toward a specific industry vertical because you are building social proof for a B2B SaaS tool, write that down.

Geo targeting also affects cost per view and delivery speed. Tier-1 English-language geos cost more and have more competition for inventory slots. If your campaign goal is pure volume for audience growth metrics and geo does not matter, say that explicitly — it gives the operator room to optimize distribution efficiently. If geo matters, rank your target markets by priority so the scaler can weight allocation accordingly.

Device type is worth specifying if your page has a meaningful performance gap between mobile and desktop. A page built primarily for desktop that receives 70 percent mobile traffic will show inflated bounce signals that corrupt your reporting baseline for future campaigns.

Campaign reporting is only useful if you defined what you were measuring before delivery started. The brief should name the specific metrics that constitute success: total views delivered, unique sessions, time-on-page if available, geo breakdown, and any secondary conversion events the page is instrumented to capture. If your analytics platform is not Google Analytics — if you are on a different tool or running a custom pixel — state that so the delivery team knows which signal to match against.

Set a baseline in the brief. If your page normally receives 2,000 organic sessions per week, note that. It gives the operator a reference point for isolating promoted traffic in the promotion dashboard data, and it gives you a clean before/after comparison when the campaign ends. Without a baseline, the final report is a number floating in a vacuum.

Specify your reporting cadence. A 7-day campaign with no interim check-in is a 7-day window where a misconfigured delivery parameter runs undetected. Request a mid-campaign delivery snapshot at the 48-hour mark so you can confirm pacing is on track before too much budget has moved.

Every input covered above should live in a single document with labeled fields, not scattered across a Slack thread, an email chain, and a shared note. A structured brief can be loaded directly into a campaign scaler as a reference document, handed off across teams without context loss, and versioned when parameters change. A message thread cannot.

A minimal brief template has eight fields: destination URL, UTM parameters, total volume target, daily delivery cap, start and end dates, geo priority list, audience notes, and reporting spec. Add a ninth field for escalation contact — who to reach if the campaign needs a mid-flight adjustment. That contact should be someone with authority to approve a scope change, not just a coordinator who will need to ask someone else.

When a brief is complete before the campaign is purchased, the time from approval to active delivery shortens significantly. Operators do not need to chase inputs, and the audience growth work starts on the scheduled date instead of two days late because a URL was still being finalized.