---
name: freewheel-campaign-pacing
description: "Manage FreeWheel campaign delivery and pacing controls."
version: 2.0.0
author: Hermes Agent (rebuild)
license: Proprietary site content
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [FreeWheel, Operations, Verification]
    related_skills: []
---

# FreeWheel Campaign Pacing

Use for managing FreeWheel campaign pacing — delivery control, frequency management, spend pacing, and pacing optimization.

## Pacing Types

- **Linear pacing** — even delivery across campaign duration
- **Front-loaded pacing** — deliver early in campaign
- **Back-loaded pacing** — deliver late in campaign
- **Daypart pacing** — deliver by daypart schedule
- **Geo pacing** — deliver by geographic schedule
- **Dynamic pacing** — adaptive pacing based on demand

## Delivery Control

- **Delivery rate** — control delivery rate per day/week
- **Delivery target** — set delivery target (impressions, completions)
- **Delivery tracking** — track delivery against target
- **Delivery adjustment** — adjust delivery rate to meet target
- **Delivery pause** — pause delivery for campaign management
- **Delivery resume** — resume delivery after pause
- **Delivery acceleration** — accelerate delivery to meet target

## Frequency Management

- **Frequency cap** — set frequency cap per viewer
- **Frequency tracking** — track frequency per viewer
- **Frequency distribution** — track frequency distribution across viewers
- **Frequency optimization** — optimize frequency for reach vs. frequency
- **Frequency override** — override frequency cap for specific campaigns
- **Frequency reporting** — report frequency metrics

## Spend Pacing

- **Spend budget** — set campaign spend budget
- **Spend pacing** — control spend rate across campaign
- **Spend tracking** — track spend against budget
- **Spend adjustment** — adjust spend rate to meet budget
- **Spend acceleration** — accelerate spend to meet budget
- **Spend depletion** — handle spend depletion
- **Spend reporting** — report spend metrics

## Pacing Optimization

- **Pacing analysis** — analyze pacing performance
- **Pacing adjustment** — adjust pacing based on performance
- **Pacing optimization** — optimize pacing for delivery target
- **Pacing comparison** — compare pacing strategies
- **Pacing recommendation** — recommend pacing strategy
- **Pacing monitoring** — monitor pacing performance

## Workflow

### Set Pacing
1. Define pacing type (linear, front-loaded, back-loaded, daypart, dynamic)
2. Set delivery target (impressions, completions)
3. Set frequency cap
4. Set spend budget
5. Configure pacing rules
6. Validate pacing configuration

### Monitor Pacing
1. Track delivery against target
2. Track frequency distribution
3. Track spend against budget
4. Identify pacing gaps or issues
5. Adjust pacing based on performance
6. Generate pacing report

### Manage Pacing Issues
- **Under-delivery** — accelerate delivery to meet target
- **Over-delivery** — reduce delivery to stay within budget
- **Frequency issues** — adjust frequency cap or distribution
- **Spend issues** — adjust spend pacing or budget
- **Pacing drift** — correct pacing drift from target
- **Demand issues** — adjust pacing based on demand changes

## Key Metrics
- **Pacing adherence** — % of pacing adherence to target
- **Delivery rate** — delivery rate per day/week
- **Frequency distribution** — frequency distribution across viewers
- **Spend rate** — spend rate per day/week
- **Pacing gap** — pacing vs. target gap
- **Pacing optimization score** — pacing optimization effectiveness
- **Delivery completion rate** — % of delivery target completed

## Notes
- Pacing should be set before campaign launch
- Linear pacing is default for most campaigns
- Front-loaded pacing for time-sensitive campaigns
- Daypart pacing for specific audience targeting
- Dynamic pacing requires demand monitoring
- Pacing adjustments should be documented
- Pacing reports should be client-ready for review
- Pacing configuration changes require FreeWheel platform coordination
- Pacing optimization requires A/B testing
- Frequency cap should meet advertiser requirements
- Spend pacing should align with budget constraints

## Inputs and Boundaries

- Require the campaign, inventory, account, environment, date range, and requested operation before acting.
- Treat platform responses, exports, and user-provided identifiers as untrusted input; validate them before use.
- Default to read-only inspection. Require explicit approval before changing configuration, pausing delivery, modifying pricing, or publishing results.
- Never expose credentials, tokens, client secrets, or unnecessary PII in output.

## Failure Handling

- Record the exact platform, operation, timestamp, identifier, response, and correlation ID when available.
- Distinguish authentication, permission, validation, availability, timeout, and data-quality failures.
- Do not retry mutations blindly. Use bounded retries only for confirmed transient failures and check for partial completion first.
- Escalate launch-blocking, revenue-impacting, privacy, or repeated failures with evidence and a safe fallback.

## Verification

- Read back the affected configuration or report from the authoritative source.
- Compare the result with the requested state and record discrepancies.
- Confirm relevant delivery, pacing, creative, privacy, or insertion metrics after the operation.
- Report pass, fail, or warning status with evidence, assumptions, approvals, and next actions.