Staging integration progress

[RMunschie92]

GA events implemented

• Site-wide
  • Events
  • page_view
• Global search bar
  • Events
    • search
• FilterButtonOrLink
  • Events
    • search
  • Screenshot
  • Example page
• InlineSubscribeForm
  • Events
    • form_submit
    • form_start
    • generate_lead
    • subscribe
  • Screenshot
  • Example page
• LightboxAccessOrNotifyForm
  • Events
  • form_view
  • form_submit
  • form_start
  • generate_lead
  • Screenshot
  • Example page (click one of the whitepaper links)
• ResultsDisplay
  • Events
  • view_search_results
  • Screenshot
  • Example 1
  • Example 2
• ShareWidget
  • Events
  • share
  • Screenshot
  • Example
• SubscribeBanner
  • Events
  • form_submit
  • form_start
  • generate_lead
  • subscribe
  • Screenshot
  • Example page (is found sitewide for reference)
• FilterWidget
  • Events
  • search
  • Screenshot
  • Example page

[RMunschie92]

Hey @SeeWatson, here's the progress I've made on the GA implementation. I think this should cover all of the events that we discussed in our initial call with Dan and Sean a few weeks back. Any feedback is welcome! Thank ya.

[SeeWatson]

@RMunschie92 I'm running through this with Dan later today, but for now only these couple of feedback items:

page_view

• I'm going to run the page_id by Dan. The purpose of it is to stay consistent when URL's/navigation change, but it looks like it's currently somewhat dependent on site structure. Is there a numerical ID associated with each page, or are you using something like next.js under the hood where each page has a generated/variable string id?

FilterButtonOrLink/FilterWidget

• I don't think a search event is needed here as no search term is being used. I'm going to check with Dan about whether he wants something like a _searchrefine event to cover this case, but as all the facets show up in _view_searchresults, we may be fine removing this entirely.

ResultsDisplay

• This appears to always show _number_ofitems as 0 when a global search is performed.
• I may want to update the facet concatenation to combine multiple values for the same facet to save us characters since we're limited to 100. E.g. - instead of facets: "topic_facet:Water & Sanitation~topic_facet:Climate & Environment" change it to facets: "topic_facet:Water & Sanitation|Climate & Environment" or something similar. Will check with Dan.

[SeeWatson]

@RMunschie92 after chatting with Dan, can you provide a list of all of the page_category values coming through on page_view events and the logic of how they're applied. Just want to make sure we have all the dimensions we need to provide accurate traffic reporting.

[RMunschie92]

Sure thing, @SeeWatson. Here's a list of the possible page_category values:

• '404',
• 'about',
• 'accountability',
• 'contact',
• 'copyright',
• 'donate',
• 'homepage',
• 'humanitarian-training',
• 'landing-pages'
• 'media-room',
• 'news',
• 'newsletter-sign-up',
• 'privacy-policy',
• 'project-profiles',
• 'research',
• 'search-results',
• 'take-action',
• 'terms-of-use',
• 'what-we-do',
• 'where-we-work'

Of course let me know if this needs updating.

I'm working through the other items from your first comment, but just as a note the page_id is indeed currently based on the site structure. We have unique identifiers for nearly all pages, so I'll go through to make sure they're added for any that don't have them.

[RMunschie92]

Hey again, @SeeWatson. I took care of all of the items in your first comment. Please let me know if there's any changes needed!