GA4: Edit Events

EventCreateRule and EventEditRule live per data stream, not per property, so every command needs both --property and --stream.

Scope required: analytics.edit. If the user is on read-only auth, instruct them to run:

gcloud auth application-default login --scopes=https://www.googleapis.com/auth/analytics.edit,https://www.googleapis.com/auth/cloud-platform

Process

1. Verify auth: python scripts/ga4_auth.py --check
2. If the user does not pass --stream, list streams with python scripts/ga4_admin.py --property <id> --streams --json and ask them to pick.
3. For diagnostic-driven proposals, spawn the ga4-events-editor agent.
4. Print the resolved rule JSON to the user and ask y/n before any write.
5. Run the script.

Direct commands

Rule JSON shapes

EventEditRule (rewrite an existing event):

{
  "display_name": "Normalize signup events",
  "event_conditions": [
    {"field": "event_name", "comparison_type": "EQUAL", "value": "signed_up"}
  ],
  "parameter_mutations": [
    {"parameter": "event_name", "parameter_value": "sign_up"}
  ]
}

EventCreateRule (synthesize a new event from another):

{
  "destination_event": "engaged_view",
  "event_conditions": [
    {"field": "event_name", "comparison_type": "EQUAL", "value": "page_view"},
    {"field": "engagement_time_msec", "comparison_type": "GREATER_THAN", "value": "30000"}
  ],
  "source_copy_parameters": true,
  "parameter_mutations": []
}

Limits and constraints

• v1alpha API - schema may change; recheck on SDK bump.
• Web streams only (per current Admin docs).
• Edit rules run in a defined order; use reorder_event_edit_rules to rearrange.
• Edit rules cannot modify events produced by create rules.

Common mistakes to flag

• Renaming purchase - breaks every conversion report and Ads import. Refuse without explicit confirmation in the message.
• Mutating transaction_id - kills duplicate-purchase detection.
• Creating a synthesized event whose name collides with a real one - produces double-counting.

Every Admin write is gated inside ga4_admin.py: it prints a scrubbed proposal and asks y/N for that operation. Run it in an interactive terminal; piped input, EOF and cancellation refuse the write. There is no bypass flag. MCP stdio tools provide previews; confirm=true returns confirmation_required without terminal approval. Never chain writes.

MCP propose_admin_write saves one exact Admin proposal for an expiring, single-use terminal approval. The user must run its approval_command and answer the existing y/N prompt themselves; agents must not supply approval. admin_proposal_status only reads the outcome. There is no MCP execute tool, and confirm=true remains insufficient. Refused or failed proposals cannot be replayed; applied:null means the result is unknown. See docs/APPROVALS.md.