Here is another way to look at this data:
It shows how many visitors it took to make the "next" conversion.
Basically, once a conversion occurs, it resets the counter. After that it counts each visitor. Once a conversion occurs, it records how many visitors the page received, stores the number and resets the counter.
It's not based on actual time, but on visitor identifier in cookes to establish the "timeline".
That can give you standard distribution and a few other properties to play with.
But I couldn't figure out a good way to use it.
Code:
K34.B,CC.A .13289 61/459 .10675 49/459
K34.B,CC.B .20487 84/410 .16829 69/410
Code:
CC.A
4
6
36
7
38
25
6
3
4
2
11
7
1
10
4
10
7
27
13
3
8
4
11
1
6
1
7
1
18
6
2
5
9
12
24
4
6
8
15
1
8
3
10
5
8
1
20
8
1
Code:
CC.B
3
3
4
9
7
4
1
7
12
10
20
5
3
3
2
6
5
7
12
1
4
6
14
4
1
16
3
15
7
4
14
15
9
6
4
2
1
11
7
2
4
25
4
1
10
5
5
3
1
3
6
2
4
2
4
8
1
3
1
2
3
3
3
2
2
6
5
3
13
It shows how many visitors it took to make the "next" conversion.
Basically, once a conversion occurs, it resets the counter. After that it counts each visitor. Once a conversion occurs, it records how many visitors the page received, stores the number and resets the counter.
It's not based on actual time, but on visitor identifier in cookes to establish the "timeline".
That can give you standard distribution and a few other properties to play with.
But I couldn't figure out a good way to use it.