{
  "fetched_at": "2026-10-20T02:23:54Z",
  "source_url": "https://www.kaggle.com/competitions/dl50-project1/data",
  "pages": [
    {
      "name": "rules",
      "content": "This is a page where you can include rules that participants must accept before joining. You may wish to include rules like:\n\n - Don't cheat!\n - Apply yourself!\n - Have fun!",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "data-description",
      "content": "**Information about the dataset:**\nThe dataset consists of 12,330 entries, each one representing a session (belonging to a user)\nin a 1-year period to avoid any tendency to a specific campaign, special day, user profile, or\nperiod. The dataset and the information about it are taken from Kaggle. However, changes\nmay have been applied.\n\n**Information about the attributes:**\nThe dataset consists of 10 numerical and 8 categorical attributes.  \n\n- **Revenue**: the class label.\n- **Administrative:** the number of the administrative pages visited by the user in\nthat session.\n- **Administrative Duration:** the total time spent by the user in administrative\npages\n- **Informational:** the number of the informational pages visited by the user in that\nsession.\n- **Informational Duration:** the total time spent by the user in informational\npages.\n- **Product Related:** the number of the product related pages visited by the user\nin that session.\n- **Product Related Duration:** the total time spent by the user in product related\npages.\n- **Bounce Rate (of a web page):** the percentage of users that entered and left\n(bounced) the website through this same webpage\n- **Exit Rate (of a web page):** the percentage of pageviews for this web page that\nwere the last in the session\n- **Page Value (of a web page):** the average value for a web page that a user visited\nbefore completing an e-commerce transaction\n- **Special Day:** the closeness of the visiting date to a special day (like Mother’s\nDay, Valentine's Day). The values are between 0 and 1, 0 being far from any\nspecial day and 1 being closest to a special day.\n- **operating system:**\n- **browser:** the operating system used\n- **region:** the region of the user\n- **traffic type:** the traffic type\n-** visitor type:** the visitor type (new visitor or returning visitor\n- **weekend:** whether the date of the visit is weekend or not\n- **month of the year:** the month of the year of the visit",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "**Data Co-Lab Engineering Lab Test**\nGiven various Information related to a customer’s behavior in online shopping websites,\nwe want to create a model that can predict whether that customer will generate revenue for the website's company or not.\nIt is therefore a binary classifcation problem.\nOur metric will be **Log-Loss**",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "<p>The evaluation pages describes how submissions will be scored and how students should format their submissions. You don't need a sub-title at the top (the page title appears above). For an example of a high quality evaluation page, see the 2013 KDD Cup page, which we have copied here:</p>\r\n<hr />\r\n<p>The evaluation metric for this competition is <a href=\"https://www.kaggle.com/wiki/MeanFScore\"> Mean F1-Score</a>. The F1 score, commonly used in information retrieval, measures accuracy using the statistics precision p and recall r. Precision is the ratio of true positives (tp) to all predicted positives (tp + fp). Recall is the ratio of true positives to all actual positives (tp + fn). The F1 score is given by:</p>\r\n<p>\\[ F1 = 2\\frac{p \\cdot r}{p+r}\\ \\ \\mathrm{where}\\ \\ p = \\frac{tp}{tp+fp},\\ \\ r = \\frac{tp}{tp+fn} \\]</p>\r\n<p>The F1 metric weights recall and precision equally, and a good retrieval algorithm will maximize both precision and recall simultaneously. Thus, moderately good performance on both will be favored over extremely good performance on one and poor performance on the other.</p>\r\n<h2>Submission Format</h2>\r\n<p><strong>For every author in the dataset</strong>, submission files should contain two columns: AuthorId and DuplicateAuthorIds. DuplicateAuthorIds should be a space-delimited list. Every AuthorId counts as his/her own duplicate, and every duplicate should be listed under each of its respective ids. For example, if you suspect author A, B, and C are the same, you should list (A,A B C), (B,B A C), (C,C A B).</p>\r\n<p>The file should contain a header and have the following format:</p>\r\n<pre>AuthorId,DuplicateAuthorIds<br />1,1<br /><span style=\"font-size: 14px; line-height: 1.4em;\">8,8<br />9,9 10<br /></span><span style=\"font-size: 14px; line-height: 1.4em;\">10,10 9<br /></span><span style=\"font-size: 14px; line-height: 1.4em;\">etc.</span></pre>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}