Google Analytics Configuration

General groups

Leads

• Anyone who has given us their info via a Salesforce landing page (an `inquiry_submission` key event)

Potential Donors

• People who clicked a "Give Now" CTA somewhere on the site

Youth Programs Interested

• Users who visit any of the YP collection of pages
  • /academics/pre-college/
  • /academics/young-artist-studio-program/
  • /academics/atelier/
  • /academics/cca-and-you/
  • 2 SEO newsroom YP-related stories

Lead Generation

Events related to Salesforce and gathering customer information are primarily focused on social ads and cca.edu.

inquiry_started

• info.cca.edu landing page view

inquiry_submission

• Salesforce form submission

inquiry_abandoned

• Salesforce form started but not completed?
• Does this need to be a tracking point, or is it ok to calculate inquiry submission/start instead?

Application Processes

All about the student journey from Workday forward.

application_started

• Based on the Apply page views (we currently only have one page)
• How should we get granular with the academic level, with an event property like application_level?

application_completed

• Don't think we have this, and don't think we can track this
• Actually, we should have GA set up on our Workday instance...

deposit_started

• Right now, this is actually defined as `application_deposit_cta`, which should probably change when we set all this into stone.

deposit_completed

• Don't think we have this, and don't think we can track this
• Actually, we should have GA set up on our Workday instance...

portfolio_started

• not sure best way to track this, maybe need a few tags (UG slideroom vs Grad slideroom general app)

portfolio_completed

• Don't think we can track this either since it's not within our GA property

Virtual Tour

Explore our campus by taking a virtual tour.

virtual_tour_started

• Link clicks that contain our current virtual tour URL (visittour.io)

virtual_tour_completed

• I don't think we can do this either, right?

virtual_tour_inquiries

• I don't think we can capture this, but even if we could, this doesn't seem right. I guess we would actually fire an `inquiry_submission` instead?

Newsroom

Editorial, media redirects, press, alumni stories, newsletters, and more.

story_started | story_viewed

• Is this a key event that's worth having? I guess I'm curious if there's a benefit from having some editorial content data at the key event level. Like is it helpful to say "three stories were viewed in a session where a lead was generated" without needing to do that with a filter? I guess if we wanted an editorial funnel chart made from key events this would be at the top right?

story_finished

• Track using scroll depth? Footer class into view? Re-implement the author footnote and target that?

share_your_news

• we have an asana submission form "Share your news" ~ I think it'd be great to capture this, but that's just a hunch

subscription_started

• currently tracking page views for /keep-in-touch/
• will need to account for embedded forms when we implement these

subscription_submission

• currently only tracking submission clicks from the /keep-in-touch/ page form, regardless of form validation

Events

Currently tracking our virtual Admissions events using an Eventbrite-hosted RSVP form that is embedded within our site. We should ideally also track other, non-admissions-related events and exhibitions.

event_listing

• Eventbrite embed button clicks?

event_register

• Eventbrite embed button click & register?

Giving

Donations and fundraising. May be limited in tracking based on what checkouts are used and what we are utilizing within our GA instance.

donation_started

• "Give Now" CTAs used throughout the site, mainly on the giving page
• The checkout site is not within our GA instance
• Currently tracking the click link url containing our checkout site

donation_submission

• We can't track this right?

Other events

click_link

• One of the first events I created...
• Seems...wrong... that I need to make something like this...
• Am I understanding this correctly? The default click event applies to non-link actions, while the link event is reserved for external links only.
• Our questions for implementation were “What links are people clicking on while on the x page?”
• ...wait, while organizing these, I'm realizing I don't use this like I thought I did...

storyConfig

• Me trying to get template info through the dataLayer so we can associate pages with their CMS tags
• I'm seeing some data come through, but not always
• This probably doesn't need to be a custom event either, right?

header_cta

• Our old configuration seemed to focus on the header cta's, I guess I'm understanding this as "we would like to have a chart with the dimension as Page Path and the metric as KeyEvent:header_cta"