← Windsor.ai Google Analytics 4CONTENT HISTORY
WHAT CHANGED
Update to Windsor.ai Google Analytics 4
Snapshot Oct 26, 2026 · 18:06 UTC · version 1.0.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Windsor.ai Google Analytics 4 and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Connect, reconnect, or add Google Analytics 4 (GA4) properties to Windsor.ai and resolve which connected property a request means. Use when the user wants to connect a property, asks what is connected, or hits a permission error. Do not use for analysis or exports.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 451
}
],
"name": "ga4-connect",
"skill_md_contents": "---\nname: ga4-connect\ndescription: Connect, reconnect, or add Google Analytics 4 (GA4) properties to Windsor.ai and resolve which connected property a request means. Use when the user wants to connect a property, asks what is connected, or hits a permission error. Do not use for analysis or exports.\n---\n\n# Connect GA4 properties\n\nHelp the user connect, reconnect, or add a Google Analytics 4 property to Windsor.ai (connector id `googleanalytics4`), and resolve which connected property a request refers to.\n\n## Stay in scope\n- Use this skill when the user wants to connect a property, add another one, reconnect after a permission error, or asks which properties are connected.\n- For analysis use $ga4-insights; for recurring exports use $ga4-export.\n\n## Workflow\n1. Call get_connectors with include_not_yet_connected=True to see whether `googleanalytics4` has connected properties.\n2. For a connection, call get_connector_authorization_url for a ready-to-open setup link (Google sign-in), or get_connector_connect_info for the auth details. Hand the user the link and tell them to authorize with the Google account that has access to the property.\n3. Never ask the user to paste tokens or passwords into the chat, and never describe manual dashboard navigation instead of giving the link.\n4. After they finish, call get_connectors again and confirm the new property by name.\n\n## Property resolution\n- If a request names a property or site, match it to a connected account id. If several properties could match, ask which one before any read.\n- A permission error on a read usually means the Google account lacks access to that property; reconnect through the same setup link with the right account.\n\n## Support\n- get_windsor_login_url gives an auto-login link into the Windsor.ai dashboard; get_current_user shows who is signed in; contact_windsor files a support or feature request. Never discuss plans or pricing.\n\n## Answer with evidence\nState which properties are connected, which are not, and the exact next step with its link.\n"
}SHA-256 of public snapshot: 1003b3131139635b1158a43f586fff6aec5d0e6ff0cfdc81d8c3863116b473c7