June 29, 201115 yr Hi all, I would really appreciate some tips or strategies on monitoring the complex traffic which will my site will start to see. I manage a website for a UK membership software company that generates low traffic 1-10 per day which I monitor in GA (very exciting when it's 10, before I realise half are from India/China ) I already filter out my office and home IPs. Our 150 or so clients are gyms/leisure centres and soon I'll be offering them a username and password to login to a secure admin page of my site I'm developing. I've also made a separate store of sorts to which our clients can link their prospective members, enabling them to signup to our clients' gyms online. So essentially a store which sells memberships, except no payments yet. The store consists of 4 main php pages (steps 1-4) which generate different content based on client preferences set in the client area and saved in mySQL tables. The link "mysite/store_step1.php?id=client" will then be issued out. Principally I obviously want to differentiate between general visitors, my clients logging in, and their clients being linked to the store. The rest isn't really important, I just don't want to render my analytics data useless moving forward. Secondly, could it be possibly to separate people visiting the same store pages by the client id in the URL (and php variable) who they are signing up for? Thirdly has anyone got any other smart ideas about what I could monitor here? Like I say I don't particularly need this data but it would be useful/interesting to start collecting it now Many thanks
June 30, 201115 yr Author Thanks alot Rallport, I'll read your blog as I should familiarise myself with manipulating GA reports with javascript. So far I've just copied in the tracking code and press refresh. Conversion rate is a great shout, also seeing if they get put off by the size of the questionnaires would be useful. Crucially I could do with a better way of differentiating which client's store they are visiting other than by the ?id=$client in the URL, and obviously if I ever change the way I carry these client/ID identifying variables it could balls up by data. Also, has anyone got any ideas on filtering out visitors to my store who I don't consider interested in our software/website, and similarly our clients who login from general / new browsing potential customers. Many thanks
Create an account or sign in to comment