consent/update-google-consent-mode switches Google Consent Mode on or off and sets its delivery options.
The value is read back after the write, and a mismatch is reported rather than assumed saved.
At a glance
| Ability | consent/update-google-consent-mode |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Configuration |
| Requires | CookieYes, 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 |
Written, then checked
This setting lives in the shared consent store, where other plugins and the consent plugin’s own screens also write. A write that is accepted and then overwritten, or filtered on save, looks identical to a write that worked — until somebody checks the front end days later.
So the ability reads the value back and compares. Reporting the mismatch is the useful behaviour here, because the alternative is a confident success message about a setting that did not change.
Turning the mode on is the consequential part. It changes how every Google tag on the site behaves before consent, and the defaults it applies in that window are configured elsewhere on the plugin’s screen — this ability sets the switch and the delivery options, not the per-type defaults.
wait_for_update is in milliseconds, and it is a genuine trade-off: too short and tags act on the defaults before the visitor’s choice arrives; too long and measurement is delayed on every page.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
status | boolean | No | Whether Google Consent Mode is active. |
wait_for_update | integer | No | Milliseconds Google tags wait for a consent update before acting on the defaults. |
url_passthrough | boolean | No | Whether to pass ad click information through URLs when consent is denied. |
ads_data_redaction | boolean | No | Whether to redact ads data when advertising consent is denied. |
What comes back
| Name | Type | What it is |
|---|---|---|
google_consent_mode | object | The configuration after the write, as read back. |
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 Google Consent Mode on with a 500ms wait.
It resolves to one call:
{
"ability": "consent/update-google-consent-mode",
"parameters": {
"status": true,
"wait_for_update": 500
}
}Worth knowing
- Idempotent.
- A reported mismatch means something else is writing the same store.
- The per-consent-type defaults are set on the plugin’s own screen, not here.
- Confirm it is reaching Google with the reported status ability, which needs a linked account.
Related abilities
- Get Google Consent Mode — read it first
- Get Reported Google Consent Mode Status — verify it end to end
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category