fastfun,
for the admin in NATS, we can store all that info and report it via our surfer stats system, but you would have to understand that you should get one BIG database server farm to collect and store the information!
Lets say a program that has 100 joins a day does this, then with today's average ratios of around 1:500 you would have to store 50000 user surfing patterns EACH DAY. Probably around 10 pages hit, thats 500000 database entries EACH DAY.
Not so sure if you REALLY want to do this... But:
1) change all links on your tours to push through the /ptrack/ script, ie if you link to tour2.php you would link to
http://linkdomain/ptrack/natscode/tour2.php instead.
2) $config['LIMIT_SURFER_STATS'] = FALSE; in nats/includes/config.php
Once thats done, all surfer actions are stored in surfer stats, if you view a member via the members admin you see the full path from unique/raw clicks to the tour, through all clicks around the tour, down to join page hits, errors and submits, sales, cascades, declines, rebills, credits, chargebacks....
I just really would not suggest you turn this on unless you REALLY know what you are doing and know your database setup very well.
This is of course a nice thing to turn on for maybe 2 hours to see how your traffic behaves.