elementor/update-experiment sets an Elementor experiment to active, inactive or default.
The three states are genuinely different and the third is the one people forget.
At a glance
| Ability | elementor/update-experiment |
| Toolset | Elementor — toolset/elementor |
| Group | Elementor › System & Maintenance |
| Requires | Elementor, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
Default is a state, not an absence
Setting an experiment to default does not mean “off”. It means “follow Elementor’s choice”, which changes when Elementor changes it — so a flag left at default can switch on during a routine update.
Setting it explicitly to active or inactive pins it, which is what you want on a site where the behaviour matters.
Turning an experiment off is the sharper direction. Content built with a feature does not un-build itself: a page of containers on a site where the container experiment has been switched off is a page of elements Elementor no longer renders properly.
So disabling an experiment is safe only on a site that has not used it. Checking first is elementor/find-elements looking for the element types in question.
Turning one on is comparatively safe — it adds capability rather than removing it — though performance-related experiments can change how assets load site-wide.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
experiment | string | Yes | The experiment name. |
state | string | Yes | active, inactive or default. |
What comes back
| Name | Type | What it is |
|---|---|---|
experiment | string | The experiment changed. |
state | string | Its state afterwards. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Turn on the nested elements experiment.
It resolves to one call:
{
"ability": "elementor/update-experiment",
"parameters": {
"experiment": "nested-elements",
"state": "active"
}
}Worth knowing
defaultfollows Elementor and can change on update. Pin it if it matters.- Disabling an experiment does not un-build content that used it.
- Check for existing usage before switching one off.
- Idempotent.
Related abilities
- List Elementor Experiments — read the names and states
- Find Elementor Elements — check for existing usage
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category