Every listener of this show is keenly aware that they are enabling the collection of various forms of hyper-specific data. Smartphones are movement and light biometric data collection machines. Many of us augment this data with a smartwatch, a smart ring, or both. A connected scale? Sure! Maybe even a continuous glucose monitor (CGM)! But… why? And what are the ramifications both for changing the ways we move through life for the better (Live healthier! Proactive wellness!) and for the worse (privacy risks and bad actors)? We had a wide-ranging discussion with Michael Tiffany, co-founder and CEO of Fulcra Dynamics, that took a run at these topics and more. Why, it's possible you'll get so excited by the content that one of your devices will record a temporary spike in your heart rate! For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.

While we don't often call it out explicitly, the driving force behind much of what and how much data we collect is driven by a "just in case" mentality: we don't know exactly HOW that next piece of data will be put to use, but we better collect it to minimize the potential for future regret about NOT collecting it. Data collection is an optionality play—we strive to capture "all the data" so that we have as many potential options as possible for how it gets crunched somewhere down the road. On this episode, we explored the many ways this deeply ingrained and longstanding mindset is problematic, and we were joined by the inimitable Matt Gershoff from Conductrics for the discussion! For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.

Once upon a time, website behavioral data was extracted from the log files of web servers. That data was messy to work with and missing some information that analysts really wanted. This was the OG "server-side" data collection. Then, the JavaScript page tag arrived on the scene, and the data became richer and cleaner and easier to implement. That data was collected by tags firing in the user's browser (which was called "client-side" data collection). But then ad blockers and browser quirks and cross-device behavior turned out to introduce pockets of unreliability into THAT data. And now here we are. What was old is now somewhat new again, and there is a lot to be unpacked with the ins and outs and tradeoffs of client-side vs. server-side data collection. On this episode, Mike Robins from Poplin Data joined the gang to explore the topic from various angles. For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.

Have you ever had stakeholders complain that they're not getting the glorious insights they expect from your analytics program? Have you ever had to deliver the news that the specific data they're looking for isn't actually available with the current platforms you have implemented? Have you ever wondered if things might just be a whole lot easier if you threw your current platform out the window and started over with a new one? If you answered "yes" to any of these questions, then this might be just the episode for you. Adam "Omniman" Greco -- a co-worker at Analytics Demystified of the Kiss sister who is not a co-host of this podcast -- joined the gang to chat about the perils of unmaintained analytics tools, the unpleasant taste of stale business requirements, and the human-based factors that can contribute to keeping a tool that should be jettisoned or jettisoning a tool that, objectively, should really be kept! For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.