2025 Week 19

Grammar for constructing a conversion attribute.

Name Spaced and Hyphened approved by Carol
ga-{{ EVENT }}

Questions to Carol

  • Should we name space by domain? JACC, ACC, CARIOSMART? or is generic ACC Enough? ✅ 2025-05-14
    • Answer was No: this wouldn't be needed and we can go with the generic name space of 'ga-'

Event List

All of these attributes are capturing that the page has convinces a user to start the journey for doing the event/action outlined.

To streamline our analytics tagging and reduce the chance of typos when adding event classes to our HTML, we’ve standardized and shortened our attribute names for key user interactions. These classes will be applied to CTA buttons and other interactive elements to help us track and move the needle on our core UX goals.

Event Label Event Concept Attribute Label
Hero CTA Click on the primary call‑to‑action in the hero/above‑the‑fold section, signaling engagement with the page’s main message. ga-hero
Primary Audience Action The core action you want your main audience to take (e.g. “Access Guidelines,” “Start Self‑Assessment”), reflecting the page’s primary goal if there isn't a more specific event below like register or purchase. ga-primary
Secondary Audience Action Actions targeted at secondary segments (e.g. returning members, affiliates) rather than the page’s primary audience, driven by tailored content or CTAs. ga-secondary
Follow Up Action Engagement steps for users who have already taken an initial action (e.g. “Sign up for updates,” “Complete your profile”), designed to drive re‑engagement. ga-followup
External Action Content that persuades the user to engage with or hand off to an external service (e.g. YouTube, partner education portal), triggering a tracked third‑party handoff. ga-external
Login Page messaging or CTA that drives an authentication flow—when a user is prompted to sign in from within content or a module. ga-login
Purchase When a user clicks through to add to cart or begin checkout from page content (e.g. “Buy now,” “Add to cart”). ga-purchase
Launch Activation of a learning product or interactive SPA directly from page copy or UI (e.g. “Start Course,” “Open Simulator”). ga-launch
Register When content motivates a user to enroll in a program or sign up for an event (e.g. “Register for CMP,” “Save my seat”). ga-register
Apply When users begin a formal application process (e.g. membership application, grant/funding request) that requires review. ga-apply
Donate When a user clicks a donation CTA (e.g. “Give now,” “Make a gift”), initiating the donation workflow. ga-donate
Help When a user clicks the customer service links within the design. ga-help

Building on our discussion around GA4 360 event‑costs, here’s a turnkey way to spot‑track every key interaction on our refactor projects by scoping on URLs and time windows—no need to enumerate every tag in the ticket. We’ll still capture all our predefined event classes, but only for a limited period on the pages that matter.

Revised Spot‑Tracking Process

  1. Target Scope

    • URLs: List all legacy paths and any newly introduced pages or vanity URLs.

  2. Pre‑Launch (Baseline)

    • Through editorial we tag legacy pages today with our standard event classes.
    • Create the Jira Ticket for
    • Capture all event hits on those URLs for 8 weeks before the refactor launch.

  3. Launch + Redesign

    • Deploy the redesigned section—this may include new page paths and any freshly minted vanity URLs.
    • Immediately upon launch, update the Jira ticket’s URL list to reflect:
      • Legacy → redesigned paths
      • Any new/vanity URLs
    • Capture all class events on that complete URL set for 8 weeks after launch.

  4. Analysis & Iteration

    • Compare equivalent pre‑ vs. post‑launch windows on the same URL set.
    • If further tweaks are needed, open a new ticket starting at Step 2.
    • Once goals are met, retire that scoped capture to preserve event volume.

Sample Jira Ticket (Turnkey)

Summary:
Spot‑track all GA events on ACHD SAP page refactor

Description:

Scope:

  • URL List:
    • /Education-and-Meetings/Products-and-Resources/ACHDSAP`
    • [plus any new/vanity URLs]

Data Windows:

  • Pre‑launch: 2025‑03‑25 → 2025‑05‑19
  • Launch date: 2025‑05‑20
  • Post‑launch: 2025‑05‑20 → 2025‑07‑15

Tracking:

  • Capture all our GA event classes fired on these URLs during each window.

Acceptance Criteria:

  1. Events fire on legacy pages during the pre‑launch window.
  2. Events fire on redesigned & new/vanity pages during the post‑launch window.
  3. Pre vs. post counts are available for apples‑to‑apples comparison.
  4. Ticket closes when analysis is complete or next iteration is opened.

Labels:
UX‑Analytics, GA4‑360, Refactor, ACHD‑SAP

Let me know if you’d like to tweak the window length (e.g. 6 weeks vs. 8 weeks) or any other detail—otherwise I’ll spin up a Jira template and we can roll this out on our next refactor kickoff.

Thanks!
—Matt