Error Console(EC) is a firefox only feature so i suggest you to download firefox it you dont have firefox. Lets get straight to the point. Example our external js source looks like this [quote]alert("hello"); alert("hello + pagviewerFName);[/quote] So we expect the above code to show two message boxes, the first one will say "hello", the second one "hello YourName" Let see what will happen if we test it. Oops... not even one showed up... Now this is where EC is good at. Here's a screenshot of what EC, btw to open EC click Tools>Error Console [img]http://h1.ripway.com/mumbhaki/Tracker%20Tutorial%20%20by/error.jpg[/img] The screeny shows two error, ignore the urchin tracker errors, those are google ads' error, they doesnt affect anything in your profile. The first error tells us which line of code messed up, notice the encircled link, that's our js link(this is always the link we need to look for incase there are many errors), click it. And the link will pop up our js code. Notice again that the source highlighted the line of error. [img]http://h1.ripway.com/mumbhaki/Tracker%20Tutorial%20%20by/src.jpg[/img] Now this is the difficult step. How will we fix that line of code? What if the line look so cryptic we cant even understand what the hell that line's for. This is what we call DEBUGGING . It is already beyond the scope of this topic because debugging requires you to have atleast basic knowledge in javascript, to learn more about js goto www.w3schools.com/js So what now? How will we fix it? For the sake of this tutorial, we will move on, atleast for this example only. Now we go back to ripway and edit our js there. And we fix the error. [quote]alert("hello"); [b]alert("hello + pagviewerFName);[/b][/quote] the above error is actually caused by a missing quotation. So after fixing, the code should look like this [quote]alert("hello"); alert("hello[b]"[/b] + pagviewerFName);[/quote] Then we test it again, im sure it will work.