So, a unique string for each visitor is passed to the user defined value. This is checked against the cookie to make sure the user defined value is not overwritten. Now, when the database reports a new web customer with an order for say $5515.49, I segment by the unique user defined value revenue that matches that order total. This creates a segment for the customer and I can see every historical move made up to the purchase instead of only the current visit.

A Primer On Web Analytics Visitor Tracking Cookies

In the article I attempt to provide clarity about this issue (including cookie deletion).

-Avinash.

This behaviour may affect result no?

We ran into this recently with an ecommerce client who was looking for instant purchases.

Question: I thought that the GA cookies were re-written based on latest visit? So if their first exposure was PPC, they're 2nd & 3rd visits may have been organic. If this is the case, then would that visitor still show up in my PPC segment for the second and third visits?

Thanks for your help!

We're starting to develop a Member Centre area for our Intranet at the British Parliament. Of course we'll get a whole surge of traffic to it the week we launch because we'll make a big splash about it on the corporate newsletter etc (and I'm sure we'll bathe in the warm rays of those early numbers)… but you're bang right about watching what happens to all those visitors down the line. It won't be much of a Member Centre if no one bothers to use it after a month. I know that is a little different to the idea of latent conversions for individual campaigns but it's the same principle.

The good news for us is we actually know the number of Members we have in our organisation so we can actually see what percentage are actually using the Member Centre on a regular and ongoing basis. I feel a KPI coming on!

Ok, better stop commenting and actually get on with building the damn thing or there will be nothing to measure! :-)

Thanks again and keep them coming,

Liam