Campaign governance
Connect the brief, approval, audience and measurement into a repeatable process.
On this page
Start with an actionable brief
Capture the audience, objective, owner, offer, channel, key dates and measure of success. Record dependencies such as landing pages, data requests and creative review. A brief should make the next action clear rather than collect fields without a purpose.
Use approval gates deliberately
Different changes need different reviewers. Define which content, legal, audience and budget decisions require approval. Preserve the reviewed version so approval does not silently apply to a later change.
Keep the taxonomy consistent
A campaign identifier and shared naming rules connect planning to activation and reporting. UTM rules should define allowed source, medium and campaign values, ownership and how exceptions are handled.
Check before activation
Validate audience eligibility, suppression, consent, links, personalization fallbacks, tracking and the planned schedule. Include rendering and form tests where relevant. Assign a person who can pause the campaign when a problem is found.
Close the operational loop
Compare the actual campaign setup to the brief and record what changed. Separate delivery metrics, engagement and commercial outcomes. Preserve the assets, audience logic and lessons needed for the next campaign.
Bind approval to the release package
An approval should identify the creative version, audience definition and action under review. When any material part changes, determine which decision needs to be renewed. The policy example keeps brand and audience review distinct while requiring both for release. Binding each decision to a version prevents an approval for one campaign package from authorizing a later, materially different release.
{
"campaign_reference": "campaign_208",
"asset_version": "creative_v4",
"audience_version": "segment_v2",
"required_reviews": ["brand", "audience"],
"release_checks": ["links", "suppression", "tracking", "schedule"],
"invalidate_on_change": ["asset_version", "audience_version"],
"release_owner": "channel_operations"
}Make launch checks inspectable
A launch checklist is stronger when each check links to evidence rather than only a checked box. Preserve the test destination, evaluated audience version and generated tracking parameters. For scheduled campaigns, decide how close to activation eligibility must be checked because permission or suppression may change after initial review.
| Gate | Evidence | Failure behavior |
|---|---|---|
| Creative | Approved version and rendition | Return the changed asset for review |
| Audience | Eligibility and suppression result | Block activation while permission is uncertain |
| Destination | Working links and form verification | Keep the affected channel unreleased |
| Measurement | Campaign code and validated parameters | Correct the tracking package before launch |
Record a partial launch honestly
A campaign can launch in one channel while another remains blocked. Store channel level status and actual activation references instead of marking the whole campaign complete. During review, compare the released package with the brief and note any changes to timing, audience or creative. These differences help explain performance and prevent the next campaign from repeating an operational mistake.
Standards and documentation
Explore the protocol specifications and platform guidance for this topic.
Bring the contract into your operating environment.
Discuss an implementation