Google Analytics vs Trello

The Google Analytics 4 Data API (`analyticsdata.googleapis.com/v1beta`) lets applications pull custom reports of metrics, dimensions, and audience segments out of a GA4 property, complementing a separate Admin API used to manage properties, streams, and access. It requires a Google OAuth 2.0 bearer token, confirmed live via a `WWW-Authenticate: Bearer realm="https://accounts.google.com/"` challenge on an unauthenticated `runReport` call, and the same request repeated with an Origin header echoed `access-control-allow-origin` back, resolving CORS support from unknown to yes. The core Data API is free to call within Google's standard quotas, with Google Analytics 360 offered as a paid enterprise tier for higher limits and additional features.

Trello turns Kanban-style boards, lists, and cards into a scriptable project-management primitive, letting integrations create, move, and archive cards or attach webhooks that fire on board activity. Every account gets a free API key, and requests carry that key plus a short-lived member token as query parameters rather than a full OAuth redirect — a live unauthenticated call to `/1/members/me` confirms this by returning 401 'invalid key' rather than a bearer-token challenge (auth corrected OAuth -> API Key; OAuth1.0a exists only as an alternate authorization flow for third-party apps). Trello's Power-Ups marketplace and countless third-party integrations run on this same public API, available on every pricing tier including the free plan, and CORS is wide open — both the GET and an OPTIONS preflight echo `access-control-allow-origin: *`, resolving the stored 'unknown' value to yes.