<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dminor</author><text>I did something similar on our site a couple years ago. One nice thing about tying it into Google Analytics is you can analyze the effect of each type of error on your conversion rate, which helps prioritize your fixes.</text><parent_chain></parent_chain></comment><story><title>You should be using Google Analytics to log your startup&apos;s client-side errors</title><url>http://www.thetaboard.com/blog/client-side-error-logging-with-google-analytics?r=378</url><text></text></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dmethvin</author><text>Google Analytics works for summary-level error reporting (file, line, error message) but not very well if you want to know the details like a stack trace which can change on each occurrence. That&apos;s where the other solutions are much better. GA is certainly better than closing your eyes though.</text><parent_chain></parent_chain></comment><story><title>You should be using Google Analytics to log your startup&apos;s client-side errors</title><url>http://www.thetaboard.com/blog/client-side-error-logging-with-google-analytics?r=378</url><text></text></story>