1 / 13

In-page traffic distribution display

In-page traffic distribution display. Original idea Allow a website administrator to see the flow of users from current page to all available destinations Present information either in form of progress bars or semi-transparent overlays

jchess
Download Presentation

In-page traffic distribution display

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. In-page traffic distribution display • Original idea • Allow a website administrator to see the flow of users from current page to all available destinations • Present information either in form of progress bars or semi-transparent overlays • Throw in informations about sources from which users came to this page • Should be a “context” data source (providing simple background view of situation)

  2. Evil reality intrudes • Available data somewhat skimpy, and so pageA -> pageB visit statistics are quite meaningless • Largest sources of traffic – unknown, Google • Result: right now, backend offers only global link popularity data • Also, got tangled up with a nasty bug in Opera – had to change target browser in the middle of development

  3. Benefits • Administrator can compare usefulness of links without digging through reports • No modifications of source website needed • No diving into unmaintainable cruft! • Access logs are the only required data source • So simple that even a manager can use and understand it

  4. Building blocks • Client: Firefox with Greasemonkey extension (allows the user to run their own Javascript on pages they visit) • Web Server: just about anything • Statistics Server: Apache with a couple of Python scripts.

  5. Browser Request Web Page Web Server Statistics Server

  6. Browser (link extraction) Web Server Statistics Server

  7. Browser XMLHttpRequest asks for popularity of given URLs Number of visits for every requested URL Web Server Statistics Server (data served by Python script)

  8. Browser (process and display received data) Web Server Statistics Server

  9. Demo • Or static screenshots if statistics server (my home machine) is down for some reason.

More Related