Viewer problems with Google tracking codes

Hi Paul,

For single section viewers, you can just remove this line:
'where' => whereRecordNumberInUrl(1),

For multi record viewers such as: portfolio.php?project-123 do you think we should just strip out utm_* values from the url when determining the record num? Are there any other utm_ fields that are commonly used that we'd need to look for?

Hi Dave,

Looking around, Google use five parameters in their tracking URLs, you can see them listed here http://www.google.com/support/googleanalytics/bin/answer.py?answer=55578

I guess ignoring these in the query string wouldn't be a bad idea in any case, but there's always scope for other variables to be added to the URL, if for example they're from Yahoo Pay Per Click or anywhere else that appends tracking data. I don't think they all use utm_ as a prefix but at least by ignoring these you've probably covered 95% of situtations.

The other option I had thought of was possibly adding an additional parameter to the getRecords() function to always return a record. Say 'neverBlank' => '1', so even if a record number is extracted from the URL but no records match that number, then the first one is returned anyway.

The situation I have is the page portfolio.php can be called without any parameters in which case it returns the first record as per the sorting defined, or can be called with a record number a loads the specific record. I know that it's never going to be called with an invalid record number and if it is, either because somebody manually types the URL, or because the URL has some tracking code appended, then showing the first record would be better than showing no record.

Thanks, Paul.

Hi Paul,

>The other option I had thought of was possibly adding an
>additional parameter to the getRecords() function to
>always return a record.

That's actually what the argument in this line does:
'where' => whereRecordNumberInUrl(1),

So if there's no number on the end of the url it uses that value as the where. So you get "WHERE 1", which is always "true" and should return everything. I'd be curious why that didn't work on that page.

Another option for numbered pages would be to remove the where line and use ?num=123, as that will filter on the record number and adding extra values to the url won't change anything.

Hmm, I'll give this one some more thought.

Good Morning,

Did anything more come of this? I too am having the same issue. My page link is services.php but as soon as you come through from a mail campaign the URL changes to:

services.php?utm_medium=email&utm_source=Emailmarketingsoftware&utm_content=588672023&utm_campaign=Issue2-May2010

I tried the code mentioned above, however, as services is a section, removing that line means you can't view the sub pages.

I hope that makes sense? I've therefore put that line back in and de-activated Google Analytics from the mail campaign until I can resolve it.

I also found this thread:
http://www.interactivetools.com/iforum/Products_C2/CMS_Builder_F35/gforum.cgi?post=73021;search_string=analytics;t=search_engine#73021 Unfortunately, this won't work for me either as my services page doesn't go to services details, mine works like so:
services.php?Media-Training-14

Any feedback/ thoughts on this would be great.

Many thanks,

jarvis

Hi Jarvis,

From the url you posted, it looks like all of the variables in the query string are related to a mail campaign.

In services.php, are you trying to do any sort of search? Is the table for services.php a single or a multi-record section?

Let me know and we'll find a solution.

Thanks

Hi Jason,
Thanks for the reply, I believe Damon is looking into this for me now as he has the details. If he finds a solution, I'll update this thread unless Damon does in order to help others.

Many thanks,

Jarvis

Hi Jarvis,

Are you running the latest version? If not, upgrading may fix it.

Hope that helps!

Hi Dave,

It's version 2.01 if that helps?

Thanks

This was added in 2.03:

- Viewers: whereRecordNumberInUrl() now ignore campaign tracking utm_* values when determining record number