Platform Actions Overview

​

What are platform actions

Platform actions are proposed changes Concord creates when you request campaign modifications. No changes are ever applied to your campaigns until you explicitly approve them.

​

How platform actions work

​

What a platform action actually contains

A platform action is a field-by-field diff, not a summary. For every object it touches you see:

• The field, its current value, and its proposed value
• The object it applies to — campaign, insertion order, ad set, line item, ad, creative
• The operation — create, update, or remove

Actions are grouped by submission and ordered by dependency: an insertion order is created before the line item that lives under it, a campaign before its ad sets. That ordering is why a partial failure stays readable — you can see exactly which action in the group succeeded and which did not. Because the diff is explicit, rejecting is clean. Nothing half-applies while you decide.

​

Everything created lands in a non-active state

Newly created campaign resources are created in a non-active state — paused, draft, or disabled depending on the platform. Activation is a separate operation with its own approval path. This is enforced below the agent: a create action that asks for an active status is overridden. See Testing without going live.

​

Types of platform actions

​

Budget and pacing

• Increase/decrease campaign budgets
• Reallocate spend between campaigns
• Adjust daily spending limits
• Extend or shorten campaign flight dates

​

Targeting optimization

• Refine audience parameters
• Add geographic or demographic exclusions
• Modify device or placement targeting
• Update bid strategies and goals

​

Campaign management

• Pause underperforming campaigns
• Resume paused campaigns
• Create new campaigns or duplicate successful ones
• End completed campaigns

​

Creative optimization

• Rotate or pause creative assets
• Launch A/B tests between creatives
• Adjust creative frequency and sequencing

​

Before you ever see an action

Every platform action runs through validation before you see it — required fields, budget and date coherence, platform formats and quotas, and the naming conventions carried by your Skills. See Validation checks.

​

Reviewing past submissions

Every platform action Concord submits stays on record. Open the History page in Settings to see a filterable log of all submitted actions across your workspace, with drill-down details and CSV export. → View Action History