consent/get-google-consent-mode reads the Google Consent Mode configuration: whether it is active, what each consent type defaults to before a visitor has chosen, and the delivery options around it.
This is what tells Google tags on the site whether they may measure or advertise.
At a glance
| Ability | consent/get-google-consent-mode |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Configuration |
| Requires | CookieYes, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Google Consent Mode works by having the tags load in a restricted state and then receive an update once a visitor decides. The defaults are what applies in the gap — between the page loading and the visitor clicking — and on most visits that gap is where a meaningful share of the traffic lives, because plenty of people never click anything.
So the defaults are not a fallback detail. They are the effective setting for every visitor who ignores the banner, which makes reading them the point of this ability.
The delivery options matter for the same reason. wait_for_update is how long tags hold before acting on the defaults; URL passthrough and ads data redaction decide what still flows when consent is denied.
This is the local configuration. Whether it is actually reaching Google is a separate question, answered by consent/get-google-consent-mode-status, which needs a linked account.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
google_consent_mode | object | Active flag, the default state of each consent type, and the delivery options. |
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:
How is Google Consent Mode configured here?
It resolves to one call:
{
"ability": "consent/get-google-consent-mode",
"parameters": {}
}Worth knowing
- The defaults govern every visitor who never interacts with the banner.
- Readable without a linked account. The reported status is not.
Related abilities
- Update Google Consent Mode — change it
- Get Reported Google Consent Mode Status — whether it is reaching Google
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category