That's essentially what I did, don't need to know the browser or device or where they are from (the product is UK only, so it's largely irrelevant) - so as I co

That's essentially what I did, don't need to know the browser or device or where they are from (the product is UK only, so it's largely irrelevant) - so as I control the server side, just log page visits and certain CTA's, and can see a rough journey of where people have been and if they placed an order or not. That's far more useful than hoping that people have JS enabled or tracking stuff blocked. (I.e. Can see that they visited an order page, then back to FAQ's, then clicked on a "whats is x" link - so should probably update the content on the order page to explain what X is) Obviously it depends on what data you actually need, but that gets me most of the way there without gathering a load of data that isn't needed