A Ben Heath video from this week has a comment section that reads like a support queue. Someone built a campaign last night and the AI-asset and enhancement options were simply missing. Someone else keeps switching the website-links enhancement off and Meta keeps switching it back on. A wedding videographer says Meta changes the contrast and colour of images that are, in his words, the product. The question under all three is the same: is this now forced, or is the switch just somewhere else?
Enhancements are stored per creative, not per account or per campaign, which is why switching one off does not keep it off for the next ad. In the API the field is enroll_status, adapt_to_placement is the only enhancement that defaults to OPT_IN, and nothing counts as off until a GET says it is.
Where the switch actually is
It is per creative, and it lives in the Marketing API on the ad creative object, under degrees_of_freedom_spec → creative_features_spec. Each enhancement is a named feature with one field, enroll_status, which is either OPT_IN or OPT_OUT. That is the whole mechanism. There is no account-level master switch in the API, and there is no campaign-level one; the decision is attached to the creative you are creating, and a new creative is a new decision.
Meta's developer documentation lists the features you can set. Grouped, they are:
- Image: image_brightness_and_contrast, image_touchups, image_uncrop, image_templates, image_background_gen, image_animation, image_text_translation.
- Video: video_auto_crop, video_uncrop, video_filtering, translate_voiceover, reveal_details_over_time.
- Text: text_optimizations, add_text_overlay, description_automation, text_translation, enhance_cta, inline_comment.
- Format and placement: adapt_to_placement, media_type_automation, creative_stickers, product_extensions, pac_relaxation.
The videographer's problem has a name on that list: image_brightness_and_contrast, with image_touchups next to it. The website-links complaint is different: that enhancement does not appear in the documented creative_features_spec list as of this writing, and Ads Manager surfaces it as a destination option, so for that one the switch is in the interface and there is no key to send — worth knowing before you go looking for one.
The one that is on by default
This is the part that explains the "forced" feeling. In the API, omitting a feature means you are not enrolled in it — the documentation is explicit that features need an explicit OPT_IN — with one exception: adapt_to_placement defaults to opt-in. So a creative created through the API with nothing specified has exactly one enhancement active. Ads Manager is a different surface with its own defaults, and its defaults are what most advertisers are fighting. Every ad you create or duplicate there is a new creative, and a new creative comes with the interface's defaults, not with the choices you made on the last one.
That is why it keeps coming back. Nothing is being switched on behind your back on an existing ad; the next ad simply does not inherit anything.
The recipe, and the part people skip
- When you create the creative (or the ad, which creates one), send degrees_of_freedom_spec with creative_features_spec listing every feature you care about and enroll_status: OPT_OUT on each. Listing them explicitly is cheap and it is the only version that survives someone changing the defaults later.
- Music is the odd one out. It is not in creative_features_spec; you opt out by passing an empty array in asset_feed_spec.audios.
- Then read it back. GET the creative and retrieve creative_features_spec. Meta's documentation says features that are opted in but ineligible for the ad setup are removed automatically, which is a polite way of saying what you sent is not necessarily what got stored. The read-back is the only statement of what is actually on.
- Compare the read-back to your policy, feature by feature, and treat any mismatch as a failure of the creation step, not as a warning.
If you keep one thing: enroll_status is stored per creative, adapt_to_placement is the only default OPT_IN in the API, and nothing counts as off until a GET says it is.
What this means if an agent is making the ads
An AI that creates ads through the API is in a better position than a person clicking through Ads Manager, for one reason: it can be told the policy once and made to send it every time. The failure mode is the same as the human one — forgetting on the tenth ad — except that a script does not forget. What it can still do is trust its own write. "I set OPT_OUT" is a claim about the request; the enhancement being off is a claim about Meta's stored object, and only the read-back proves the second. A tool that creates creatives and does not read creative_features_spec back is reporting its intentions.
Where we sit
Everix builds and runs Meta campaigns from a conversation. We do not generate creative for you, so the enhancements question never turns into a question about who changed your image — the creative is yours, and what Meta may do to it is a setting you decide. Cuts and pauses happen on their own; anything that spends more waits for a human.
If you are reading this because an ad went out with enhancements you did not choose, pull the creative with fields=degrees_of_freedom_spec before you change anything. You will find out in one call whether the problem was the default, the duplication, or the tool that said it had turned them off.