Tracking Code Problem - Statcounter

This is a wrinkle that seems unique to XDP6 which I'm taking on a test drive at the moment doing up a small website.

As per usual I added my Statcounter tracking code into the appropriate spot just as I did many times with XXP5 and which worked flawlessly.

So I added the code in and found that I'm not getting my tracking details. Contacted Statcounter who looked at the page and the only thing they could suggest was to move the statcounter code above a line that says
"<!--[if lt IE 7]><script type="text/javascript" src="artiles_html_files/png.js"></script><![endif]-->"

I can't see a way to accomplish that unless I manually edit the HTML in a text editor every time I re-save a page.

Any thoughts or suggestions from all the great minds hereabouts??

Thanks
Paul

Thread moved out of the 'Site Design and Publishing (non-Xara') forum to the 'Web Designer / Xtreme / Designer Pro' forum.

I used Statcounter on one of my sites created with DP6 with the code placed in the 'Replace with HTML code' placeholder.
Tracking works fine.

Based on this thread, I added Statcounter to several of my sites using WD6. I discovered that if I added their code to the placeholder of any existing element already on the page, that element would not render. So I created a tiny rectangle with the background color of my page, line size=none, (rendering it invisible) and pasted the Statcounter code in its placeholder.

Seems to work fine. I checked the counter stats and they appear valid.

Thanks for that. Haven't used WD6. In XXP5 and in XDP6 I've been using the built-in area under the website/webpage properties for inserting tracking code.

Worked great in XXP5 ... not so in XDP6. Even StatCounter's tech's suggestion didn't work. Weird thing is that I'm seeing (in StatCounter) the accumulation of page loads ... but not getting the detailed stats I need.

I've told them their "fix" didn't do it and that the same line they thought was offending existed in HTML generated by XXP5 and those sites work fine with StatCounter.

Cheers & thanks
Paul

Quote:

---

Originally Posted by hardot

I discovered that if I added their code to the placeholder of any existing element already on the page, that element would not render.

---

No of course not, because you have told the html export filter that this object is a placeholder for the code you have entered in the 'Placeholder' properties. Therefore the filter ignores the object and replaces it with the html code.
This is exactly how it is designed to work :)

Quote:

---

Originally Posted by taccom

Thanks for that. Haven't used WD6. In XXP5 and in XDP6 I've been using the built-in area under the website/webpage properties for inserting tracking code.

Worked great in XXP5 ... not so in XDP6. Even StatCounter's tech's suggestion didn't work. Weird thing is that I'm seeing (in StatCounter) the accumulation of page loads ... but not getting the detailed stats I need.

I've told them their "fix" didn't do it and that the same line they thought was offending existed in HTML generated by XXP5 and those sites work fine with StatCounter.

Cheers & thanks
Paul

---

I will tell you what I can say from my own experience with tracking severals sites with StatsCounter now: When I did use the code which was generated by the browser (means in the configuration) it did not work! Only the code which StatsCounter did send by email to me did work.

I did generate my pages with Xtreme or WD6 an then opened the html-files with editor an did integrade code. Of course this is manualy and uncomfortable buut did work. Test if your code from browser and the code via email are different.

TomTom

Quote:

---

Originally Posted by taccom

Weird thing is that I'm seeing (in StatCounter) the accumulation of page loads ... but not getting the detailed stats I need.


Cheers & thanks
Paul

---

im having the same problem no detailed stats just the page loads

Hi TomTom

Thanks for the post ... unfortunately it didn't make a change in the situation. StatCounter is trying to figure it out but so far no success. I suggested their techies contact Xara techies and put heads together because it isn't a small issue for those of us designing performance oriented websites.

Sorry to hear you're having the same issue Dreamer ... but at least I know now it isn't just me!

I'm going to submit a ticket to Xara Support ... since I'm using the trial version they may not reply.

I love the new features in XDP6 ... but this situation is a deal-breaker that would have me sticking with XXP5!

Cheers
Paul

Funny how these things cause problems for some and not for others.

I use Statcounter. And it works fine, full stats and so on.

What I did was the following.

I set up the counter on the Statcounter site.
I copied the resulting code.
In XWD6 I selected 'Paste placeholder html'

After a couple of seconds thinking, it produced the actual counter on the page.
I then dragged it to where it was needed.
That's it.

Hi Staggers

Thanks for taking time to reply. My Statcounter code works fine in my copy of web designer and Xtreme Pro 5 ... its just the new XDP 6 that seems to conflict with Statcounter's code ... techs at Statcounter are buffaloed on this one.

No problems here using DP6 and the Statcounter code.

Try using a placeholder as suggested by myself in post#2 and by staggers.
Works fine.

Thanks Sledger ... I'll give that a try. However I am concerned that the Xara include isn't working properly. Great to have work-arounds though!

Cheers
Paul

Quote:

---

Originally Posted by taccom

the Xara include isn't working properly.

---

q1: What is "Xara include"?
q2: What is not working properly?

Hi John

Q1 The 'include' is where you go to the website/webpage properties ... there is the space for page name, title, description, keywords and then tracking code ... puts the code right before the </body> tag where Statcounter advises to place it for best results.

Q2 When I log into Statcounter I can see that I have had page loads ... but just the number of loads. Usually I can then go to 'Veiw Recent Pageload Activity' where I can see the details of each visitor including location, referring link and so on. That's the part that isn't working. Same code is working fine in all my other sites ... ones built with XPP5, WebDesigner, FrontPage and Expression web ... its just a problem with the new Xara release (XDP 6)

Thanks!!
Paul

Quote:

---

Originally Posted by taccom

Q1 The 'include' is where you go to the website/webpage properties ...

---

Ok. But don't call it this way to avoid any possible confusion.

Quote:

---

Q2 When I log into Statcounter I can see that I have had page loads ... but just the number of loads.

---

Please tell me why do you think that: "Xara include isn't working properly."? The recommended code placing is right before the </body> tag, isn't it? Are you expecting it to be placed somewhere else? Is it placed in the wrong place? As far as I can see all works exactly as it is supposed to. The Statcounter code is placed exactly where they advice, where you expect it to, and where it is documented. So the tracker code field works perfectly in XDP6.
If the Statcounter snippet is not compatible with the pages exported by DP6, that is an obvious flaw in the Statcounter code. After all it is supposed to work with any page, isn't it?

Hi Again John

My terminology was a bit off there regarding the 'include'.

The Xara module places the code just fine and right where it ought to be. I've been back & forth with Statcounter on this a couple of times. Their first suggestion was to:

"My apologies for the inconvenience and confusion. Please try moving our
code up to just before the <!--[if lt IE 7]> to see if that helps."

That didn't work, so next they suggested:

"Thanks for the reply. Please try moving this code below our tracking
code, right now it's directly before our code :

<script type="text/javascript">xr_aeh()</script>"

That didn't work either and I'm awaiting further input from them. In both cases their suggestion involved what they thought could be a conflict with Xara-generated code and their code. Not being a 'code writer' I can't identify what that Xara-generated code is there to do.

Yes its supposed to work with any page and has for the 10 years I've been using it.

Thanks & cheers
Paul

At the risk of repeating myself Paul.

Try using a placeholder as suggested by myself in post#2 and by staggers.
Works fine.

"No problems here using DP6 and the Statcounter code."

I'm doing that placeholder change as that will get it working and appreciate the tip.

I am curious though as to why a placeholder works and the built-in method seems not to.

Quote:

---

Originally Posted by taccom

I am curious though as to why a placeholder works and the built-in method seems not to.

---

The only difference is where your code is placed within the HTML.

That is true ... Statcounder advises the code to be right before the </body> tag ... where the built-in method places it.

An update on my situation.

As suggested I placed the Statcounter Code into a placeholder and located it at the end of each page.

Unfortunately the situation did not change ... I can still see how many hits have occurred but the detailed data is non existent.

I suggest you go back to your statcounter account and redo your settings then grab new install code.
I have no problems with all details from a code added via a placeholder and placed anywhere on a WD6 or DP6 created page.
The instructions from SC don't appear to specify that the code must be right before the closing </body> tag.

Quote:

---

Congratulations - Here is your Code!

You can configure many options relating to your counter again using the Configure Counter page. If you need to change something that is not available on that page, you can come back to the Install Code page to generate new code for your pages.

What follows is your StatCounter code - simply copy & paste it exactly as it is into your pages to start tracking your visitor data! Make sure you insert it after the <body> tag and before the </body> tag.

---

These instructions simple mean that the code should be placed *somewhere* between <body> and </body> - in other words inside the body section.

Thanks Sledger

I discovered the source of the problem ... although I cannot explain the reason(s) for it.

As an experiment I changed the size of the Statcounter log file (from 500 to 250) and bingo ... the code started logging the details right away.

I've advised them as it seems to be a bug.

Thanks to all for the time and suggestions!