4 ms·

The headline, the problem and the solutions are all different things. - Front end tracking did not lie, the people tracking it were not aware. If opendoor was

The headline, the problem and the solutions are all different things. - Front end tracking did not lie, the people tracking it were not aware. If opendoor was spending on Ads, the marketing team would be the first to see a disparity between the clicks on an ad network and pageviews on their end. - As such this is also a reason why you need to check your server hit logs with your Analytics. - Where is the author is right it Frontend numbers being incorrect largely due to blockers - His understanding of bounces is also incorrect. Bounce is when there is no second "interaction event", many marketing folks fake-fix the bounce rate, by sending a scroll event as an interaction event. - I always tell people that analytics numbers are "signals", not "metrics", they are not accurate enough to be called "metrics"

d0gbread 6y ago
If these numbers were significantly changed by a server side page view, I'd bet their page view wasn't firing any earlier than the top or bottom of the body tag, or maybe even on window ready. Anyone that's spent any real time outside of dropping in a snippet understands the implications of users navigating before hits fire, and it sounds like the team just didn't have that experience. Like you, I also work to make sure people understand that client side data is not necessarily accurate, but still refer to it as metrics and KPIs, just with the caviot that we should bank on consistancy over accuracy, keeping our analysis geared towards behavior and trends versus most business people's immediate desire to take it to an operational/business intelligence type place.