Hi,<\/p>\n
Because the calendar’s search and filtering is based on AJAX (vs full page reloads), submitting search queries via the Tribe Events Bar and the Filter Bar do not trigger page views in Google Analytics. Same goes for the page navigation in calendar (“Previous Events” and “Next Events”). Thus, we need to track these as Virtual Pageviews in Google Analytics to account for the pageviews that occur when users perform searches for events as well as when the navigate through the pages of search results.<\/p>\n
In researching Virtual Pageviews, it appears the syntax is: For example: We want to generate a Virtual Pageview whenever a user clicks the Find Events button in the Tribe Events bar, as well as when a user navigates the search results via the “Previous Events” or “Next Events” links at the bottom of the calendar views. My understanding is that we’ll need to add Thank you, PS – If anyone else has added this type of tracking on their calendar via another method that does not require editing a core file, I would love to hear how you achieved that (I do not have experience with Virtual Pageviews and am not sure which alternative methods might work with this other than editing the files that contain the button and pagination link elements).<\/p>\n","protected":false},"template":"","class_list":["post-1085739","topic","type-topic","status-closed","hentry"],"yoast_head":"\n
\nga(\u2018send\u2019, \u2018pageview\u2019, \u2018name of virtual page\u2019);<\/code><\/p>\n
\n<a href=\u201dhttps:\/\/www.example.com\/some-file.pdf\u201d onClick=\u201dga(\u2018send\u2019, \u2018pageview\u2019, \u2018\/virtual\/some-file.pdf\u2019);\u201c> An Example Title<\/a><\/code><\/p>\nga(\u2018send\u2019, \u2018pageview\u2019, \u2018name of virtual page\u2019);<\/code> to those respective elements. Which core Events Calendar files contain the code for these?<\/p>\n
\nKarly<\/p>\n