![]() ![]() You head over to Google Analytics (GA) to configure your goals using events, you then realize that it would be “awesome-sauce” if you could see how people navigated through that really cool ajax form you just tagged, and if there were any resulting conversions. Google Analytics Configuration Limitations That’s not always the case, and there are other reasons why you might need a Virtual Pageview. When it's all said and done, we assume that all pageviews will be captured organically, and that our events will house everything that we need. We start down a path that involves extensively tagging interactions with the appropriate event category, action, and label using Google Tag Manager (GTM), or another data collection tool. ![]() If we’re working with a traditional website, many times pageviews get overlooked in favor of events during our complex and time-intensive Analytics implementations. Anything that dynamically updates content on the page without actually pushing a refresh to the entire page has the potential to be missed in tracking.Įnter Virtual Pageviews: a data collection strategy within Google Analytics that enables you to send a pageview hit, even when the page doesn’t reload. Sometimes, however, the configuration of our site (i.e.: ajax, or single-page applications) can limit what Google counts as a pageview, resulting in missed data collection opportunities. Pageviews are usually determined when the browser loads, or reloads a page. ![]() With pageviews, you can see unique pageviews, average time on page, entrances, bounce rate, and much more. Pageviews let you know how important a page is to your users. The pageview-one of the most important, or at least most commonly reported on, metrics in Google Analytics. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |