consent/get-google-consent-mode-status reads the Google Consent Mode status as the consent service reports it.
This is the end-to-end check: not what the site is configured to send, but what is observed arriving.
At a glance
| Ability | consent/get-google-consent-mode-status |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Reporting |
| 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
The local configuration is readable without an account through consent/get-google-consent-mode. It tells you the switch is on. It cannot tell you the signal is reaching Google, and the ways that fails are all invisible from inside WordPress — a tag manager loading before the consent script, a caching layer serving the page without it, a container that never had the consent trigger wired.
The reported status is observed from the outside, which is why it needs a linked account and why it is worth reading separately from the configuration.
The two read together are the diagnosis: configuration on and status not reporting means the problem is in delivery, not in settings.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
google_consent_mode_status | object | The status as the consent service reports it. |
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:
Is Google Consent Mode actually working on this site?
It resolves to one call:
{
"ability": "consent/get-google-consent-mode-status",
"parameters": {}
}Worth knowing
- Needs a linked consent account.
- Read alongside the local configuration — the pair is the diagnosis.
- Caching layers are a common cause of configured-but-not-arriving.
Related abilities
- Get Google Consent Mode — the local configuration
- Get Consent Settings — check the account is linked
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category