Something I wish would be included in the next release of NATS

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • fastfun
    Confirmed User
    • Jul 2006
    • 249

    #1

    Something I wish would be included in the next release of NATS

    NATS is a great script, but both as a webmaster and Admin I would like NATS to take a small step further in the direction of Data-intelligence in the next release. In general this goes not only for NATS, but for all the others as well - CCbill, mpa....... you name it.

    Code:
    Right now I can see this
    Referrer        Unq Hits         Signups        Ratio 
    Site.com               22                 2            11
    What would be nice, is if I click "Unq Hits" it would show me every Session the script registered. Something like

    Code:
    User             Sessions    Signups
    "user a"                            3             1
    "user b"                            2             0
    "user c"                            1             0
    "user d"                            1             1
    "user e"                            1             0
    Then when I click "sessions" it would show me the pages he browsed in the order he navigated through the site. Like

    PHP Code:
    Page                        signup
    Index.php                        0
    product1.php                        0
    shipping.php                        0
    checkout.php                        1 
    
    Or am I the only one that wants that?
    Since the sessions is registered anyways, I don't think it would be to much work to include that, maybe as a plugin/addon even. It shouldn't mean to much server-load either since its just passing the info to the Database
  • detoxed
    vip member
    • Jan 2003
    • 17798

    #2
    I have a big list :0

    Comment

    • fuzebox
      making it rain
      • Oct 2003
      • 22353

      #3
      I used to track all that on my old program... Most affiliate software now though pretty much send you through a script that tracks the hit and then sets a cookie, and the tour pages are completely seperate until you go back to the join page.

      Comment

      • Nathan
        Confirmed User
        • Jul 2003
        • 3108

        #4
        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.
        "Think about it a little more and you'll agree with me, because you're smart and I'm right."
        - Charlie Munger

        Comment

        • fastfun
          Confirmed User
          • Jul 2006
          • 249

          #5
          Originally posted by Nathan
          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.
          Thank you very much We will try that as soon as Kristoffer gets back to Europe

          Comment

          Working...