Hi Mark,
Just discussing this with a collogue and we came up with another idea,
still using asynch AJAX, but place it in the receiving page, then all
the calling page has to do is place the appropriate click event into a
cookie that is persisted across the page transfer. The new page then
Don't see why not though it'd slow down the user experience a bit (not
necessarily a good thing).
Have the onclick block, send data to server, server responds, then in
the Ajax callback send user to the destination via window.location
Note: I haven't done this, it's just an off the top of my
@DJ Mangus: That would have been my simple solution too. Capture the
click event, do my ajax mojo, and then forward them. But like you
mentioned, it will most likely affect the user experience.
@manfmnantucket: Have you ever thought about using google analytics?
It offers the generic visitor info
Thanks for the thoughtful suggestions...
@djmangus - I already have this working synchronously, but I'm trying to do
a/b testing on things like pricing and conversion rates, and the extra delay
does affect abandonment rates, especially over slow/dialup connections.
Jeff C - I've looked at
