Starting Marketing API v2.4, we simplified how the optimization is specified in the data model by decoupling the bid fields into 3 separate fields. With this simplification, we should be able to significantly reduce the confusion around optimization specification in both the API and our UIs.
Bid type to billing_event and optimization_goal
The table below illustrates the mapping between bid type, billing_event and optimization_goal. Do not use this table as a reverse mapping.
|bid type (deprecated)||billing_event||optimization_goal||rtb_flag|
billing_event=NONE is only available on read paths for certain campaigns created in pre-v2.2 where Facebook is unable to determine the
billing_event. New ad sets cannot be created with a NONE
optimization_goal=NONE is only available on read paths for certain campaigns created in pre-v2.4 where Facebook is unable to determine the
optimization_goal. New ad sets cannot be created with a NONE
billing_event to bid type
The table below illustrates what to set in
billing_event which maps to the now older (now deprecated feature) bid type`.
For ad sets in campaigns with a
|billing_event||rtb_flag||bid type (deprecated)|
LINK_CLICKS (all other objectives)