Skip to main content
Commonmark migration
Source Link

To me, it looks like the clicks/day on a stats page like this is calculated as the clicks, divided by the days from the "Created" timestamp. However, is that correct? "Created" refers to the date the ad was added, not to the day the ad reached the threshold of 6 votes.

###Example

Example

Consider an ad that was added at January 1, and reached the threshold of 6 votes at February 1. Since then, people clicked on it 60 times. It is now March 1.

The current system would say the clicks per day has to be calculated over January and February, therefore the clicks/day rate is ~1, 60/59. However, that isn't fair! In January, the ad couldn't be clicked. The clicks/day rate should be ~2, 60/28.

###Note

Note

Please note that with this change, you'd have to track if community ads don't get below the threshold as well: for example, when an ad reaches 6 votes, than gets below the 6, and then above the 6 again - the system should only count the periods it had 6 votes.

To me, it looks like the clicks/day on a stats page like this is calculated as the clicks, divided by the days from the "Created" timestamp. However, is that correct? "Created" refers to the date the ad was added, not to the day the ad reached the threshold of 6 votes.

###Example

Consider an ad that was added at January 1, and reached the threshold of 6 votes at February 1. Since then, people clicked on it 60 times. It is now March 1.

The current system would say the clicks per day has to be calculated over January and February, therefore the clicks/day rate is ~1, 60/59. However, that isn't fair! In January, the ad couldn't be clicked. The clicks/day rate should be ~2, 60/28.

###Note

Please note that with this change, you'd have to track if community ads don't get below the threshold as well: for example, when an ad reaches 6 votes, than gets below the 6, and then above the 6 again - the system should only count the periods it had 6 votes.

To me, it looks like the clicks/day on a stats page like this is calculated as the clicks, divided by the days from the "Created" timestamp. However, is that correct? "Created" refers to the date the ad was added, not to the day the ad reached the threshold of 6 votes.

Example

Consider an ad that was added at January 1, and reached the threshold of 6 votes at February 1. Since then, people clicked on it 60 times. It is now March 1.

The current system would say the clicks per day has to be calculated over January and February, therefore the clicks/day rate is ~1, 60/59. However, that isn't fair! In January, the ad couldn't be clicked. The clicks/day rate should be ~2, 60/28.

Note

Please note that with this change, you'd have to track if community ads don't get below the threshold as well: for example, when an ad reaches 6 votes, than gets below the 6, and then above the 6 again - the system should only count the periods it had 6 votes.

replaced http://meta.electronics.stackexchange.com/ with https://electronics.meta.stackexchange.com/
Source Link

To me, it looks like the clicks/day on a stats page like thisthis is calculated as the clicks, divided by the days from the "Created" timestamp. However, is that correct? "Created" refers to the date the ad was added, not to the day the ad reached the threshold of 6 votes.

###Example

Consider an ad that was added at January 1, and reached the threshold of 6 votes at February 1. Since then, people clicked on it 60 times. It is now March 1.

The current system would say the clicks per day has to be calculated over January and February, therefore the clicks/day rate is ~1, 60/59. However, that isn't fair! In January, the ad couldn't be clicked. The clicks/day rate should be ~2, 60/28.

###Note

Please note that with this change, you'd have to track if community ads don't get below the threshold as well: for example, when an ad reaches 6 votes, than gets below the 6, and then above the 6 again - the system should only count the periods it had 6 votes.

To me, it looks like the clicks/day on a stats page like this is calculated as the clicks, divided by the days from the "Created" timestamp. However, is that correct? "Created" refers to the date the ad was added, not to the day the ad reached the threshold of 6 votes.

###Example

Consider an ad that was added at January 1, and reached the threshold of 6 votes at February 1. Since then, people clicked on it 60 times. It is now March 1.

The current system would say the clicks per day has to be calculated over January and February, therefore the clicks/day rate is ~1, 60/59. However, that isn't fair! In January, the ad couldn't be clicked. The clicks/day rate should be ~2, 60/28.

###Note

Please note that with this change, you'd have to track if community ads don't get below the threshold as well: for example, when an ad reaches 6 votes, than gets below the 6, and then above the 6 again - the system should only count the periods it had 6 votes.

To me, it looks like the clicks/day on a stats page like this is calculated as the clicks, divided by the days from the "Created" timestamp. However, is that correct? "Created" refers to the date the ad was added, not to the day the ad reached the threshold of 6 votes.

###Example

Consider an ad that was added at January 1, and reached the threshold of 6 votes at February 1. Since then, people clicked on it 60 times. It is now March 1.

The current system would say the clicks per day has to be calculated over January and February, therefore the clicks/day rate is ~1, 60/59. However, that isn't fair! In January, the ad couldn't be clicked. The clicks/day rate should be ~2, 60/28.

###Note

Please note that with this change, you'd have to track if community ads don't get below the threshold as well: for example, when an ad reaches 6 votes, than gets below the 6, and then above the 6 again - the system should only count the periods it had 6 votes.

edited tags
Link
user65560
  • 9.9k
  • 2
  • 26
  • 52
added 700 characters in body
Source Link
user65560
  • 9.9k
  • 2
  • 26
  • 52
Loading
Source Link
user65560
  • 9.9k
  • 2
  • 26
  • 52
Loading