Skip to content

gog analytics admin conversion-events / key-events have no create subcommand #265

Closed

Description

@itsjeremyjohnson

Observed

Zeus installed /home/zeus/.local/bin/gog is v0.10.0 (e81e585).

gog analytics admin conversion-events --help
gog analytics admin key-events --help
# both are stub groups with no create/list/get
gog analytics admin conversion-events create --help
gog analytics admin key-events create --help
# unexpected argument create

Still missing on origin/main as a usable write path.

API methods

  • analyticsadmin.properties.keyEvents.create POST .../v1beta/properties/{id}/keyEvents
  • legacy conversionEvents.create still listed in some clients

GA4 renamed conversions to key events; CLI should create/list via keyEvents and keep conversion-events as alias if needed.

Workaround used

Direct REST: POST keyEvents {eventName: generate_lead} on properties/553945658 succeeded (Just Store It). REST is a workaround, not the product path.

Ask

Add gog analytics admin key-events create|list (and conversion-events alias) with --property and --event-name.

Activity

  1. itsjeremyjohnson commented on Sep 14, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Agent Brief

    Category: enhancement
    Summary: Implement GA4 key-events create/list (with conversion-events alias) as real CLI write/read paths.

    Current behavior:

    • gog analytics admin conversion-events and gog analytics admin key-events are stub groups with no create/list/get subcommands.
    • ... create is rejected as an unexpected argument on both groups.
    • Operators fall back to direct REST (analyticsadmin.properties.keyEvents.create) instead of a supported CLI write path.

    Desired behavior:

    • Prefer the modern GA4 naming: gog analytics admin key-events create|list as the primary path.
    • Keep conversion-events as an alias where needed for discoverability/legacy naming.
    • Support --property and --event-name (and any other minimal flags required by the Admin API) with structured output suitable for automation.
    • Wire create to analyticsadmin.properties.keyEvents.create; list against the corresponding keyEvents list API.

    Key interfaces:

    • CLI primary: gog analytics admin key-events create|list
    • CLI alias: gog analytics admin conversion-events ... (alias to key-events behavior)
    • API: analyticsadmin.properties.keyEvents.create (and list); legacy conversionEvents naming only as alias surface if useful
    • Flags: --property, --event-name (minimum for create/list as specified)

    Acceptance criteria:

    • key-events create and key-events list exist, are documented in --help, and are not stubs.
    • Create accepts --property and --event-name and calls the keyEvents Admin API successfully for a valid property.
    • List accepts --property and returns key events in structured/JSON-friendly form when requested.
    • conversion-events remains usable as an alias to the key-events path (create/list) without a second divergent implementation.
    • Invalid property / missing event name produce clear non-zero errors; successful create returns identifiable event data.

    Out of scope:

    • Full get/update/delete CRUD unless needed to keep create/list coherent.
    • Treating direct REST workarounds as the supported product path.
    • Unrelated analytics admin property lifecycle work (covered by sibling issues).
  2. itsjeremyjohnson commented on Oct 8, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    Reconfirmed 2026-10-08 on v0.10.0 while fixing Pinnacle Projects GA4 (properties/296679986): still no create/list. Direct REST POST keyEvents worked for phone_call and ads_conversion_Contact_Us_1 using the stored token (analytics.edit present). Also needed: countingMethod selection (ONCE_PER_EVENT/ONCE_PER_SESSION).

  3. itsjeremyjohnson commented on Oct 12, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    Closing as superseded (GitHub sweep 2026-10-12). This asks for a new gog CLI subcommand, but the CLI was removed from main in 91336b7 (#269) and only gog-mcp is built. The MCP equivalent is tracked in #271.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentFully specified and ready for an agent

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions