GET /api/v2/buyer/campaign-suggestion-sets/:campaignSuggestionSetId
Returns one campaign suggestion set with the full per-media-buy breakdown — which
media buys give up budget, which receive it, and how much. This is the view to
read before deciding, because the breakdown is what makes the transfer legible.
See campaign suggestion sets for the
lifecycle and what each status means.
Request
Parameters
Response
Reading the numbers
Every allocation figure is an exact count ofbudgetCurrency’s minor unit, sent
as a string. "-400000" on a USD campaign is $4,000 leaving that media buy.
A member’s netAllocationDelta is deliberately not zero — it is that media
buy’s side of the transfer, and it is always present. The set’s own
netAllocationDelta is what must be zero, and it is the sum of its members; it is
null until the set is complete, because there is nothing balanced to report yet.
If you add the members up and get anything other than zero, the set will not be
actionable.
The values are strings because they are int64 counts surfaced as decimal strings,
not because they are large. Do not route them through a float.
applyMode tells you who decides: MANUAL means this set is waiting on you,
AUTO means optimizations apply without review and the set was approved on
arrival. It is read from the campaign, falling back to the advertiser’s default,
and fixed when the run is first seen.
Reading an applying or applied set
Once a set is approved, these fields describe how the transfer is going. See what happens after you approve for the behaviour behind them.
A member with an
appliedAt on a set that later reads COMPENSATED was changed
and then changed back, so the value on the media buy is its pre-approval budget
— unless statusReason names it as one the reversal could not reach, in which
case it may still be sitting at the suggested one.
Whether an approved set applies automatically at all depends on rollout — see
availability.