Hello Again,
So cutting the sales presentation into pieces won't work. Now to the
more complicated solutions I mentioned. By the way, putting small
transparent images into your presentation won't work because the
browser will always download all of them when the page first loads,
whether the user scrolls down to their position on the page or not.
The images are not even necessarily requested by the browser in the
same order they appear in the HTML.
Since you are going to need to measure some activity performed by the
user, you've only got a couple options left:
If the page is longer than can be displayed in a typical browser, you
can try to get your metrics by detecting when and where the user
scolls the page. You'll need the user to be scrolling the entire page
or at least a frame. If the text is in a div tag then this won't work
since JavaScript cannot get the scroll coordinates from a <div> tag.
So approach it like this:
1) Create 11 blank web pages called scroll0.htm through scroll10.htm
2) In the page with the presentation, put a hidden iframe with
scroll0.htm as its source URL
3) Put an onScroll event on the page that calls a function ScrollPost()
4) The essence of ScrollPost() is that it gets the vertical scroll distance
and then determines what percentage of the total page height this is. For
example, say the page height is 900px and the scrolled distance from the top
of the page is 99px. The page is therefore 11% scrolled, divide the 11 by
ten and round or simply remove the digit from the one's position, append
"scroll" on the front and ".htm" on the back to get "scroll1.htm" and set
this as the iframe's source URL.
5) Get your metrics from the number of views of the pages created in step 1
Also: You could instead post the scroll data itself, capture it in a
database and then analyze this later, but such pages take longer to
fetch from the server and this could affect the performance of your
scripts. It's a more ideal solution if you have the resources to do
it.
Some things to keep in mind with the onScroll approach:
1) Some browsers make a (possibly annoying) tick when the user clicks
a link. Users with this sort of browser will hear the ticking sound
repeatedly everytime they scroll your page.
2) A given "session" may skip over some of the scroll pages, i.e.
request scroll0.htm then scroll3.htm, bypassing scroll1.htm and
scroll2.htm altogether.
3) Whether the user uses the PgUp/PgDn keys, the UpArrow/DnArrow and
Home/End keys will affect your metrics and each user may use more than
one method during a single viewing of your page.
4) Some people turn off JavaScript and in these cases you'll get no data.
5) If a user's browser is big enough that scrolling does not occur
while reading the sales copy, then you won't get any data from the
user, since the onScroll event will never fire.
And finally, if your presentation is small enough that it never
requires the user to scroll, your options are very limited. In such a
case, you'd need to make the user interact with your presentation
somehow, by mousing over portions or clicking somewhere and trapping
those events. Good luck with your project. |