Skip to main content

Google Analytics

Fancified

Google Analytics for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.

Runtime Package Install
Authoring surface (every host) @particle-academy/google-analytics-ui npm install @particle-academy/google-analytics-ui
Node @particle-academy/google-analytics-js npm install @particle-academy/google-analytics-js
PHP 8.4+ particle-academy/google-analytics-php composer require particle-academy/google-analytics-php
Python 3.11+ fancy-google-analytics pip install fancy-google-analytics

The ui package is the editor surface and is React on every host — a PHP or Python project installs it and its own runtime package, and never the js one.

What it costs you

One dependency: @particle-academy/fancy-connector-core (or particle-academy/fancy-connector-core on Composer), which the js and php packages pull in themselves. The Python package has zero runtime dependencies.

No Google Analytics SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.

Setting it up

Everything below is generated from provider/manifest.json, so it cannot disagree with what the packages do.

On Google Analytics's side

  1. Create (or reuse) the Google Cloud project for your app's name — Every Google connector shares ONE consent grant (oauth.grant "google"), so use one project and one OAuth client for all of them: one consent and one refresh token per person. (developers.google.com)
  2. Enable the Google Analytics Data API — Console: APIs & Services, Library; open the Google Analytics Data API and click Enable. (developers.google.com)
  3. Configure the consent screen — Console: Google Auth platform, Branding (app name your app's name, support email, contact email), then Audience: Internal for people inside your Google Workspace organisation only, or External (while it is in testing, add each tester under Test users). Then Data Access, Add or Remove Scopes, and add https://www.googleapis.com/auth/analytics.readonly beside the scopes of any other Google connector you use. You cannot remove the consent screen once it is configured. (developers.google.com)
  4. Create a Web application OAuth client — Console: Google Auth platform, Clients, Create Client; type Web application. Under Authorized redirect URIs click Add URI and paste your host's OAuth redirect URL, then Create. Copy the client ID and client secret when the client is created. (developers.google.com)
  5. Connect an account and check it works — Connect one Google account through your app's name's OAuth flow, then run the check below. (developers.google.com)

Every step in full — who does it, what to paste, which credentials it yields, and how you know it worked — is in SETUP.md.

Credentials

A Google Analytics connection holds 4 values.

Two kinds of value, and mixing them up matters. A provider credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An account credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.

Field Scope Secret Where it comes from
OAuth client ID per installation not secret From Google Cloud Console -> APIs & Services -> Credentials. ONE value for the whole installation, not per connected account.
OAuth client secret per installation secret The client secret for the same OAuth app. One value for the whole installation.
Access token per connected account secret Per connected Google account, and it expires after ONE HOUR. The host refreshes it with the refresh token.
Refresh token per connected account secret Per connected Google account. Google issues one only when the consent request asks for offline access.

Authorising

Google Analytics uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.

One consent grant, shared (grant: "google"). Every connector declaring the same grant can run on ONE OAuth client, with one consent and one refresh token per person.

  • Authorize with access_type=offline, include_granted_scopes=true. Ask for a feature's scopes when it is first used; the new token covers every scope granted before. A refresh token comes back only on the FIRST exchange, so keep the stored one when an exchange returns none.
  • Revoke — POST https://oauth2.googleapis.com/revoke with token. It removes the WHOLE grant: every connector sharing it, not only this one. A per-feature disconnect stops using that feature's scopes locally; only a full disconnect revokes.
  • Identify the account by sub: request openid, then verify the token response's id_token (issuer https://accounts.google.com or accounts.google.com, keys at https://www.googleapis.com/oauth2/v3/certs, audience = clientId). Never key a connection by email.
  • No restricted scopes in this connector.

The refresh tokens do not rotate: the same one is reusable, so a refresh may safely be retried and may run concurrently. Stated rather than assumed, because the opposite — a provider that spends the token and revokes the grant on a replay — looks identical until it happens.

The estate

Google Analytics has no test estate, and somebody checked. Everything this connector does is real. Use the faker to build against it.

Google Analytics has no sandbox. A report reads a real property's real data and spends real quota. The faker returns a plausibly-shaped report so a flow can be built without a Google account.

What it can do

Actions

report_run — Google Analytics report

Run a report against a Google Analytics 4 property.

POST /v1beta/{+property}:runReport · reads only — safe to replay

Input Required What it is
property yes The GA4 property, written as properties/1234567890. The numeric id alone is not accepted.
startDate yes YYYY-MM-DD, or a relative form Google accepts such as 28daysAgo, yesterday or today.
endDate yes YYYY-MM-DD, or a relative form such as today.
metrics yes Metric names, comma separated. For example activeUsers, sessions, screenPageViews.
dimensions no Dimension names, comma separated. For example date, country, pagePath. Leave empty for a single total row.

Run it before you have credentials

Every operation ships a faker, whether or not Google Analytics has a sandbox. Set a node's mode to fake and it returns the shape Google Analytics actually publishes — the same field names, deterministically — so you can wire the downstream nodes before touching an account, a key, or a network.

This repository is generated

provider/ is the source. Everything under packages/ is emitted from it and must not be hand-edited — CI regenerates and diffs on every push, and the next protocol sync destroys anything it finds. See AGENTS.md.

Two namespaces, which do not match on purpose

The repo is github.com/Fancy-Friends/google-analytics; the packages publish under particle-academy. Nothing derives one from the other — the names come from weaver's friends.json and nowhere else.

Licence

MIT.

Metadata

Release files for fancy-google-analytics 0.5.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fancy-google-analytics 0.5.2
File Size Uploaded Provenance Actions
fancy_google_analytics-0.5.2.tar.gz 25.6 kB Without provenance Details for fancy_google_analytics-0.5.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fancy-google-analytics 0.5.2
File Interpreter ABI Platform Actions
fancy_google_analytics-0.5.2-py3-none-any.whl Python 3 none any Details for fancy_google_analytics-0.5.2-py3-none-any.whl

Total release size: 48.8 kB

Release files / fancy_google_analytics-0.5.2.tar.gz

Download URL fancy_google_analytics-0.5.2.tar.gz
Size 25.6 kB
Tags Source
SHA-256 checksum
How to use checksums
9974b9722bd7f1916411d6379c58080728963c39b0fc2e991b2e87ba4e776eb6
BLAKE2b-256 checksum
How to use checksums
2d196f0192cd3eca72b398b5dc24c5402c2e681179166fda262d30ab6d63ab4e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Release files / fancy_google_analytics-0.5.2-py3-none-any.whl

Download URL fancy_google_analytics-0.5.2-py3-none-any.whl
Size 23.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e37bd1e53a392c74a7bb0ede0cfe1a6db6f4cf8a2b43ef269311f152f18dcf53
BLAKE2b-256 checksum
How to use checksums
b54574c611c58fb0bba48573e605a2ca33c7e418f54420aed42b5b940eceebfa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Security for fancy-google-analytics 0.5.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page