-
One thing that jumps out from your post is that you built the spreadsheet by clicking through the site as a normal user, and that is exactly where the gap lives. A tracking plan really needs to be built from what the DOM actually does, not from what the happy path looks like. Next time you sit down to do this, try opening DevTools and looking at the Event Listeners tab before you write a single row. That will show you every click handler, modal trigger, and form submit listener on the page, including the ones that fire on validation failures. You will also see that for hash routes which do not trigger a full page reload, standard page view tracking based on URL changes will not work, and you will need to figure out how the site is pushing history states instead. Those are not things you would ever catch by just browsing the site like a regular user, but they are the first things a developer or a tag implementation tool will trip over.
