There may be better ways to do this but my approach would be to get a FIXED registration date (using Unix Timestamp) added to your data layer, which is available on all visits post registration, such as: registrationTime = 1593172370551 You could set this in Launch, but personally I would use the da...

Hi there, Firstly you need to be careful if you capturing this information because of GDPR. It's worth checking your legal team is happy but providing they are, I would actually go with the simple solution of using javascript datediff and a getdate(), so no updating is required. https://www.w3resour...

Hi asheeshp - that is correct! Not sure if that should be called a bug or a feature

Hi there, that video shows it working exactly how I would expect it to work, however as you can see from my screenshot, my work space is not totally 100% per row.

At the moment we can analyze the users in our data lake using the feeds if needed, so A count will do. We assign an evar for the purchaseID an evar so i will give that a try. Thanks

Thanks garym3332907​, that was a nice chuckle on a Friday afternoon.

I have heard (from Adobe product development) that Adobe are working on this for a future release. Always nice to hear.

Forgot to mention - I am keeping a close eye on this. At the moment our main defence to legal was that there are no large eCommerce companies doing it and that will should follow their lead for the moment.

Hi Stefanie,This was raised by our legal team this week.ThanksDave

Hopefully bumping this thread up a little. Having had to do this today it is a real pain not having all the information in one place.