Skip to content

feat: per-tenant tag_id + anonymize_ip surface (closes #4)#5

Merged
intel352 merged 1 commit into
mainfrom
feat/per-tenant-1779248985
May 20, 2026
Merged

feat: per-tenant tag_id + anonymize_ip surface (closes #4)#5
intel352 merged 1 commit into
mainfrom
feat/per-tenant-1779248985

Conversation

@intel352
Copy link
Copy Markdown
Contributor

Adds anonymize_ip (build-time + per-call) and per-call tag_id documentation. Multi-tenant hosts now have full parity with the CMS plugin's TenantConfig surface. 4 new tests; all existing tests pass.

The injection step already accepted `tag_id` at execute time, which
covers per-tenant usage. This commit adds:

1. `anonymize_ip` (bool) — emits `{'anonymize_ip': true}` inside the
   GA4 `gtag('config', ...)` call. Configurable at module-build time
   AND at execute time; per-call wins.
2. CLI flag `--anonymize-ip` for the `wfctl analytics inject` form.
3. README "Per-tenant (multi-app) usage" section showing the
   `gocodealone-multisite` invocation pattern.

The full per-tenant story for the multisite host lives at:
  - gocodealone-multisite SPEC.md V25
  - workflow-plugin-cms `analytics` package (host-side gating)

This plugin's role is just to render the snippet correctly when given
a per-tenant config. The host owns tenant resolution + dispatch.

4 new tests cover anonymize_ip on/off, per-call tag_id, per-call
anonymize_ip; the original 12+ tests still pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@intel352 intel352 merged commit 4f412af into main May 20, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant