Skip to main content

Overview

You can attach structured targeting intent to a campaign when creating or updating it through the V3 MCP surface (save_campaign on /mcp/v3). Targeting records what the campaign intends to reach — geography, language, device type, daypart, and demographic dimensions — and persists that intent with the campaign object.
Targeting intent is stored and returned on the campaign workspace but is not yet enforced at delivery. Delivery enforcement is tracked separately and will be announced when active.

Passing targeting to save_campaign

The targeting parameter is optional. Omit it to leave targeting unset; include it to attach one or more dimensions:
Each dimension is an array of requirement entries. A requirement entry has:

Supported dimensions

Reading targeting back

After save, targeting appears on the campaign workspace returned by save_campaign and by get(kind: "campaign"). Existing campaigns with no targeting set omit the field entirely.

Updating targeting

Pass targeting in a save_campaign update to replace the stored targeting intent. Partial dimension updates replace the entire targeting object — each call is the full desired state, not a patch.

Backward compatibility

The targeting parameter is optional. Existing calls that do not include it continue to work without change. Existing campaigns are not affected.