Re: Wicket 1.5 and Google Analytics

2011-09-20 Thread Attila Király
If nothing else helps I think you can exclude query parameters in Google Analytics: http://www.google.com/support/analytics/bin/answer.py?answer=55499 http://www.google.com/support/analytics/bin/answer.py?answer=55461 Attila 2011/9/20 Bruno Borges bruno.bor...@gmail.com With Wicket, versioned

Re: Wicket 1.5 and Google Analytics

2011-09-20 Thread Don Ferguson
Using the async analytics apis, you can pass a parameter to trackPageView, as in: _gaq.push(['_trackPageview', 'Home']); which gives you explicit control over the URL being tracked by analytics. -Don On Sep 20, 2011, at 11:38 AM, Bruno Borges wrote: With Wicket, versioned pages are

Re: Wicket 1.5 and Google Analytics

2011-09-20 Thread Diego Fincatto
I agree with Bruno and there's more related problems, such the redirecting it does: for SEO is a bad practice! Google may even penalize our sites. We have to think in a different way to retrieve the state of webpages. Otherwise, the Wicket becomes unusable for most seriously site. On Tue, Sep

Re: Wicket 1.5 and Google Analytics

2011-09-20 Thread Martin Grigorov
On Tue, Sep 20, 2011 at 10:51 PM, Diego Fincatto diego.finca...@gmail.com wrote: I agree with Bruno and there's more related problems, such the redirecting it does: for SEO is a bad practice! Google may even penalize our sites. We have to think in a different way to retrieve the state of

RE: Wicket 1.5 and Google Analytics

2011-09-20 Thread Chris Colman
@wicket.apache.org Subject: Re: Wicket 1.5 and Google Analytics I agree with Bruno and there's more related problems, such the redirecting it does: for SEO is a bad practice! Google may even penalize our sites. We have to think in a different way to retrieve the state of webpages. Otherwise, the Wicket