Forum Moderators: DixonJones

Message Too Old, No Replies

Problems with Google analytics

Data crossover between customers

         

wheel

8:54 pm on Jun 22, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I've got a calculator I provide as a plugin to a fair number of customers. Basically I give the users a custom link to a calculator on my site, where I generate individual pages for each customer. Visitors to my client's sites click through from the site to my site to run this calculator (though each client's pages on my site are unique).

Now the mixup. A number of my clients use Google analytics and install it on their pages on my site. In some cases when a lead is generated for a client, they're seeing Google analytics variables from other clients being submitted as part of the form/lead.

As near as I can figure, a consumer visits site A, clicks through to my domain and uses the calculator. Then they somehow hit site B (likely back through the SERPS) and click through to my domain to run the calculator for site B. I think the browser is then autofilling/remembering the variables from the first calculator....and site B now sees some junk from site A. (there's no other connection to the calculator's on site A or B, the pages are all orphaned on my site and only linked to from my client's site).

The end result is that I get the odd client complaining that they're receiving leads from other customers, and occassionally my clients are even calling each other. Makes me look bad, but as far as I can tell it's just Google analytics combined with overzeolous browser's autofill function.

Anyway to prevent this? I really don't know Google analytics so I don't even know where to start. Flush the browser using some javascript or something?

Metaphorically

6:51 pm on Jul 6, 2007 (gmt 0)

10+ Year Member



I think the autofill has to be based on the name of the field and the name of the site it's on. Though there are plugins and third-party autofill programs out there...

I'd try adding some salt to the names of the fields so the browser doesn't think they're the same. Maybe on site A's calculator you have id="field1-siteA" and on site B's you have id="field1-siteB" if you get my drift.