User login

MetaTraffic 2.0 Boxshot

Won't Track anyone!

Posted by Ckudrna [June 22, 2003]

I am using the JS method to track users. I had it working fine until i upgraded, now it doesnt track anything.

Yes i have the Include track.js on all pages, the config file is pointing to the correct DB and path. It was working just fine before i attempted to upgrade, now it wont show anything??!!

Thanks

Won't Track anyone!

Good day,

When you upgraded, what was you base version ?

Perhaps you needed to apply intermediate upgrades priod to the final one. If I recall well, the upgrade was going from 0.993 to 1.200 Beta 3.

We'll find what is going wrong, don't worry. ;)

Regards

Won't Track anyone!

I can manually enter in values in the database and then view it with the reports, but it will not track users.

I have a feeling it has to do with track.asp or track.js (i use the javascript tracking)

any ideas let me know

THANKS!

Won't Track anyone!

I am going to assume that the tracking problems are on the same installation of MetaTraffic as the other post you made regarding the referrer reports producing the asp error.

You need to upgrade your database schema, as done in step 1 of the upgrade. This will solve both the tracking and reporting issues you are experiencing.

Regards,
~Chad

Won't Track anyone!

If you can add data manually to your database and then see the results from the reports page, the only thing that comes to my mind is the path specified in your "track.js" file via the "scriptlocation" variable that could be wrong.

Also, on my installation, although this might be related to some other things proper to my site, I noticed that the "track.js" script would not do the tracking with ASP pages, therefore I would suggest you to use it with HTM or HTML only.

So for the HTM/HTML pages consider to use the following :

Note: Double-check the "scriptlocation" variable for proper specification.

For the ASP pages consider using the following :

The specifications above are based on the fact that the "metatraffic" directory is at the root level, like your HTML or PICS or IMAGES directories for instance, so adjust accordingly.

If the above still doesn't work, please post your site structure so that we can have an idea where the metatraffic facility is located in your site.

Hope that helps.

Won't Track anyone!

quote:I noticed that the "track.js" script would not do the tracking with ASP pages, therefore I would suggest you to use it with HTM or HTML only.

So for the HTM/HTML pages consider to use the following :

For the ASP pages consider using the following :
I use the javascript tracking method for all the pages on my site and it works fine.
If I used track.js for html pages and track.asp for asp pages then I'd only get the screen resolution data for the html pages.

Mark Voss - Small Business Websites
http://www.small-business-websites.co.uk

Won't Track anyone!

metaraffic folder is in root

i use HTML pages, the location to the track pages (track.js) is the same as it was from my previous installation of metatraffic.

I followed the readme for the upgrade, tried to upgrade the database, and it spit out an error when updating the schema and an error when trying to fill data (because the schema could not be upgraded due to an error, obviously the data cannot be filled into fields that do not exist.

Again, with th .993 version of metatraffic it worked fine, recorded the data for all the pages with the tag to include the track file. Since upgrading, the database schema is all out of whack, tracking does not take place, (although all the paths are correct) and many reports do not work.

Should i just replace my existing database with a new version (that comes with the new metatraffic install) and go from there?

If the database schema is what is causing everything, maybe replacing it with a fresh compy is the only answer?

THANKS

Won't Track anyone!

As I have said before, the problem here is that your database schema is out of date. If you got an error when trying to update the schema in step 1 of the upgrade process, please post it so we can see what happened.

Regards,
~Chad

Won't Track anyone!

quote:Originally posted by MarkVoss
quote:I noticed that the "track.js" script would not do the tracking with ASP pages, therefore I would suggest you to use it with HTM or HTML only.

So for the HTM/HTML pages consider to use the following :

For the ASP pages consider using the following :
I use the javascript tracking method for all the pages on my site and it works fine.
If I used track.js for html pages and track.asp for asp pages then I'd only get the screen resolution data for the html pages.

Mark Voss - Small Business Websites
http://www.small-business-websites.co.uk

Mark,

I've never been able to get the screen resolution when tracking ASP pages. I tried the "track.js" approach on an ASP page, yet to no success.

If you were successfull at getting screen resolutions when tracking ASP pages, please post a sample here. I'd appreciate to take a peek at it.

Regards.

Won't Track anyone!

If you can't get screen resolution working, why don't you post a new topic including the version you are running, logging method, etc. It does work; I haven't had any issues with it with several implementations of the software.

Regards,
~Chad

Won't Track anyone!

Daniel - what reports do you want to see?
ASP pages seem to work fine with the track.js method for me.

Mark Voss - Small Business Websites
http://www.small-business-websites.co.uk

Won't Track anyone!

quote:Originally posted by MarkVoss
Daniel - what reports do you want to see?
ASP pages seem to work fine with the track.js method for me.

Mark Voss - Small Business Websites
http://www.small-business-websites.co.uk

Mark, Chad,

Sorry for the false alarm, I found the culprit.

I ran a mass change on my site, and got a couple of variables renamed by errors. :(

The good thing, I guess, is that I'm having the screen resolution tracked properly.

1) asp page using "asp method" -> Screen resolution not tracked
2) asp page using "js method" -> Screen resolution tracked properly
3) htm page using "js method" -> Screen resolution tracked properly.

Thanks for your help though... :)

Bye for now...