{
  "id": 67238,
  "title": "Collect discussion in Google Analytics",
  "url": "/competitions/ga-customer-revenue-prediction/discussion/67238",
  "author_name": "",
  "post_date": "2018-09-30T13:22:45.846974200Z",
  "votes": 34,
  "comment_count": 4,
  "views": 0,
  "content": "<p>This discussion is based on Yevgeni Berkovitch's <a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66706\">Three big decisions</a>. I hope people who are challenging the Google Analytics Competition for the first time get a lot of insight.</p>\n\n<h2>1. <code>transaction level</code> vs <code>user level</code></h2>\n\n<p>Currently, there is a user level approach for oliver and a transaction level approach for others. \n- <a href=\"https://www.kaggle.com/ogrellier/user-level-lightgbm-lb-1-4480\">user_level_lightgbm LB 1.4480</a> olivier\n- <a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/kernels?sortBy=voteCount&amp;group=everyone&amp;pageSize=20&amp;competitionId=10038&amp;categoryIds=13102\">[LB 1.4439]GACR Prediction: EDA + LGB Baseline</a> by oskird</p>\n\n<h2>2.  what's your <code>encoding</code> method?</h2>\n\n<p>Most people use one-hot-encoding and label-encoding. But there are a lot of other encoding techniques. How about using this to increase your LB? </p>\n\n<ul>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66581\">Various reference to solve high cardinality</a> by YouHan Lee</li>\n<li><a href=\"https://www.kaggle.com/youhanlee/which-encoding-is-good-for-time-validation-1-4417\">Which encoding is good for time-validation? - 1.4417</a> by YouHan Lee</li>\n</ul>\n\n<h2>3. How about using <code>classification</code>?</h2>\n\n<p>The target variables of this competition are mostly 0, and the smaller number has a higher value. So classifying whether to buy or not to buy is a very important issue in raising your score.</p>\n\n<ul>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66675\">Could we use Classification ?\n</a> by olivier</li>\n<li><a href=\"https://www.kaggle.com/ogrellier/using-classification-for-predictions\">using-classification-for-predictions</a> by olivier</li>\n</ul>\n\n<h2>4.  <code>time-based-split</code> vs <code>k-fold</code> ?</h2>\n\n<p>I do not know in detail, but the conflict between the <code>k-fold</code> technique and the<code>time-based-split</code> technique conflicts with the current validation division. If you know well with this part, please answer me.</p>\n\n<h2>5. <code>Discrepancy between CV and LB scores</code></h2>\n\n<p>There is a lot of difference between cv-score and lb-score, as you know who submitted it. There is a discussion on why this is the reason why and how to approach it.</p>\n\n<ul>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66811\">Discrepancy between CV and LB scores</a> by Craig Armstrong</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66739\">So where does the discrepancy between local scores and corrected LB come from?</a> by Adams</li>\n</ul>\n\n<h2>6. <code>other useful information</code></h2>\n\n<ul>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66046\">Google Analytics columns description</a> by Alexander Firsov</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66697\">More than 10M single user revenue in test set</a> by AhmetErdem</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66440\">Will our models be useful?\n</a> by S D</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66815#latest-395855\">Date vs visitStartTime - explained</a> by Yannis Pappas</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66774\">[Finding] - Pageviews/Hits ratio &lt;0.4 guarantees no revenue</a> by Adams</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/65989\">Finding : totals_bounces and totals_transactionRevenue</a> by Maxwell</li>\n</ul>\n\n<p>It is the material that I arrange others documentation. because it was hard to keep searching. I hope it helps someone. Tell me if you can add anything.</p>",
  "messages": [
    {
      "id": "396327",
      "postDate": "09/30/2018 13:22:45",
      "content": "<p>This discussion is based on Yevgeni Berkovitch's <a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66706\">Three big decisions</a>. I hope people who are challenging the Google Analytics Competition for the first time get a lot of insight.</p>\n\n<h2>1. <code>transaction level</code> vs <code>user level</code></h2>\n\n<p>Currently, there is a user level approach for oliver and a transaction level approach for others. \n- <a href=\"https://www.kaggle.com/ogrellier/user-level-lightgbm-lb-1-4480\">user_level_lightgbm LB 1.4480</a> olivier\n- <a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/kernels?sortBy=voteCount&amp;group=everyone&amp;pageSize=20&amp;competitionId=10038&amp;categoryIds=13102\">[LB 1.4439]GACR Prediction: EDA + LGB Baseline</a> by oskird</p>\n\n<h2>2.  what's your <code>encoding</code> method?</h2>\n\n<p>Most people use one-hot-encoding and label-encoding. But there are a lot of other encoding techniques. How about using this to increase your LB? </p>\n\n<ul>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66581\">Various reference to solve high cardinality</a> by YouHan Lee</li>\n<li><a href=\"https://www.kaggle.com/youhanlee/which-encoding-is-good-for-time-validation-1-4417\">Which encoding is good for time-validation? - 1.4417</a> by YouHan Lee</li>\n</ul>\n\n<h2>3. How about using <code>classification</code>?</h2>\n\n<p>The target variables of this competition are mostly 0, and the smaller number has a higher value. So classifying whether to buy or not to buy is a very important issue in raising your score.</p>\n\n<ul>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66675\">Could we use Classification ?\n</a> by olivier</li>\n<li><a href=\"https://www.kaggle.com/ogrellier/using-classification-for-predictions\">using-classification-for-predictions</a> by olivier</li>\n</ul>\n\n<h2>4.  <code>time-based-split</code> vs <code>k-fold</code> ?</h2>\n\n<p>I do not know in detail, but the conflict between the <code>k-fold</code> technique and the<code>time-based-split</code> technique conflicts with the current validation division. If you know well with this part, please answer me.</p>\n\n<h2>5. <code>Discrepancy between CV and LB scores</code></h2>\n\n<p>There is a lot of difference between cv-score and lb-score, as you know who submitted it. There is a discussion on why this is the reason why and how to approach it.</p>\n\n<ul>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66811\">Discrepancy between CV and LB scores</a> by Craig Armstrong</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66739\">So where does the discrepancy between local scores and corrected LB come from?</a> by Adams</li>\n</ul>\n\n<h2>6. <code>other useful information</code></h2>\n\n<ul>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66046\">Google Analytics columns description</a> by Alexander Firsov</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66697\">More than 10M single user revenue in test set</a> by AhmetErdem</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66440\">Will our models be useful?\n</a> by S D</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66815#latest-395855\">Date vs visitStartTime - explained</a> by Yannis Pappas</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66774\">[Finding] - Pageviews/Hits ratio &lt;0.4 guarantees no revenue</a> by Adams</li>\n<li><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/65989\">Finding : totals_bounces and totals_transactionRevenue</a> by Maxwell</li>\n</ul>\n\n<p>It is the material that I arrange others documentation. because it was hard to keep searching. I hope it helps someone. Tell me if you can add anything.</p>",
      "rawMarkdown": "This discussion is based on Yevgeni Berkovitch's [Three big decisions](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66706). I hope people who are challenging the Google Analytics Competition for the first time get a lot of insight.\n\n## 1. `transaction level` vs `user level`\nCurrently, there is a user level approach for oliver and a transaction level approach for others. \n- [user_level_lightgbm LB 1.4480](https://www.kaggle.com/ogrellier/user-level-lightgbm-lb-1-4480) olivier\n- [[LB 1.4439]GACR Prediction: EDA + LGB Baseline](https://www.kaggle.com/c/ga-customer-revenue-prediction/kernels?sortBy=voteCount&amp;group=everyone&amp;pageSize=20&amp;competitionId=10038&amp;categoryIds=13102) by oskird\n\n## 2.  what's your `encoding` method?\nMost people use one-hot-encoding and label-encoding. But there are a lot of other encoding techniques. How about using this to increase your LB? \n\n- [Various reference to solve high cardinality](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66581) by YouHan Lee\n- [Which encoding is good for time-validation? - 1.4417](https://www.kaggle.com/youhanlee/which-encoding-is-good-for-time-validation-1-4417) by YouHan Lee\n\n## 3. How about using `classification`? \nThe target variables of this competition are mostly 0, and the smaller number has a higher value. So classifying whether to buy or not to buy is a very important issue in raising your score.\n\n- [Could we use Classification ?\n](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66675) by olivier\n- [using-classification-for-predictions](https://www.kaggle.com/ogrellier/using-classification-for-predictions) by olivier\n\n## 4.  `time-based-split` vs `k-fold` ?\nI do not know in detail, but the conflict between the `k-fold` technique and the` time-based-split` technique conflicts with the current validation division. If you know well with this part, please answer me.\n\n## 5. `Discrepancy between CV and LB scores`\nThere is a lot of difference between cv-score and lb-score, as you know who submitted it. There is a discussion on why this is the reason why and how to approach it.\n\n- [Discrepancy between CV and LB scores](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66811) by Craig Armstrong\n- [So where does the discrepancy between local scores and corrected LB come from?](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66739) by Adams\n\n## 6. `other useful information`\n- [Google Analytics columns description](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66046) by Alexander Firsov\n- [More than 10M single user revenue in test set](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66697) by AhmetErdem\n- [Will our models be useful?\n](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66440) by S D\n- [Date vs visitStartTime - explained](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66815#latest-395855) by Yannis Pappas\n- [[Finding] - Pageviews/Hits ratio &lt;0.4 guarantees no revenue](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66774) by Adams\n- [Finding : totals_bounces and totals_transactionRevenue](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/65989) by Maxwell\n\nIt is the material that I arrange others documentation. because it was hard to keep searching. I hope it helps someone. Tell me if you can add anything.",
      "votes": null
    },
    {
      "id": "396805",
      "postDate": "10/01/2018 12:00:46",
      "content": "<p>Oh, Thanks. Very good to see all the important discussions about this competition!</p>",
      "rawMarkdown": "Oh, Thanks. Very good to see all the important discussions about this competition!",
      "votes": null
    },
    {
      "id": "397260",
      "postDate": "10/02/2018 07:51:44",
      "content": "<p>Can you add a section with feature engineering ? cheers</p>",
      "rawMarkdown": "Can you add a section with feature engineering ? cheers",
      "votes": null
    },
    {
      "id": "397401",
      "postDate": "10/02/2018 13:00:23",
      "content": "<p>It's a good idea. However, features do not put people into the kernel or discussions because of their rankings. And need to verify that this is a good feature. yet, I'll try adding the proven features like <code>pageviews / hits.</code>. Thanks idea</p>",
      "rawMarkdown": "It's a good idea. However, features do not put people into the kernel or discussions because of their rankings. And need to verify that this is a good feature. yet, I'll try adding the proven features like `pageviews / hits.`. Thanks idea",
      "votes": null
    },
    {
      "id": "397402",
      "postDate": "10/02/2018 13:00:35",
      "content": "<p>haha. Thanks</p>",
      "rawMarkdown": "haha. Thanks",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 396805,
      "author_name": "youhanlee",
      "author_url": "",
      "post_date": "10/01/2018 12:00:46",
      "content": "<p>Oh, Thanks. Very good to see all the important discussions about this competition!</p>",
      "votes": null,
      "replies": [
        {
          "id": 397402,
          "author_name": "chocozzz",
          "author_url": "",
          "post_date": "10/02/2018 13:00:35",
          "content": "<p>haha. Thanks</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 397260,
      "author_name": "xaviermaxime",
      "author_url": "",
      "post_date": "10/02/2018 07:51:44",
      "content": "<p>Can you add a section with feature engineering ? cheers</p>",
      "votes": null,
      "replies": [
        {
          "id": 397401,
          "author_name": "chocozzz",
          "author_url": "",
          "post_date": "10/02/2018 13:00:23",
          "content": "<p>It's a good idea. However, features do not put people into the kernel or discussions because of their rankings. And need to verify that this is a good feature. yet, I'll try adding the proven features like <code>pageviews / hits.</code>. Thanks idea</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "396327": "This discussion is based on Yevgeni Berkovitch's [Three big decisions](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66706). I hope people who are challenging the Google Analytics Competition for the first time get a lot of insight.\n\n## 1. `transaction level` vs `user level`\nCurrently, there is a user level approach for oliver and a transaction level approach for others. \n- [user_level_lightgbm LB 1.4480](https://www.kaggle.com/ogrellier/user-level-lightgbm-lb-1-4480) olivier\n- [[LB 1.4439]GACR Prediction: EDA + LGB Baseline](https://www.kaggle.com/c/ga-customer-revenue-prediction/kernels?sortBy=voteCount&amp;group=everyone&amp;pageSize=20&amp;competitionId=10038&amp;categoryIds=13102) by oskird\n\n## 2.  what's your `encoding` method?\nMost people use one-hot-encoding and label-encoding. But there are a lot of other encoding techniques. How about using this to increase your LB? \n\n- [Various reference to solve high cardinality](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66581) by YouHan Lee\n- [Which encoding is good for time-validation? - 1.4417](https://www.kaggle.com/youhanlee/which-encoding-is-good-for-time-validation-1-4417) by YouHan Lee\n\n## 3. How about using `classification`? \nThe target variables of this competition are mostly 0, and the smaller number has a higher value. So classifying whether to buy or not to buy is a very important issue in raising your score.\n\n- [Could we use Classification ?\n](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66675) by olivier\n- [using-classification-for-predictions](https://www.kaggle.com/ogrellier/using-classification-for-predictions) by olivier\n\n## 4.  `time-based-split` vs `k-fold` ?\nI do not know in detail, but the conflict between the `k-fold` technique and the` time-based-split` technique conflicts with the current validation division. If you know well with this part, please answer me.\n\n## 5. `Discrepancy between CV and LB scores`\nThere is a lot of difference between cv-score and lb-score, as you know who submitted it. There is a discussion on why this is the reason why and how to approach it.\n\n- [Discrepancy between CV and LB scores](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66811) by Craig Armstrong\n- [So where does the discrepancy between local scores and corrected LB come from?](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66739) by Adams\n\n## 6. `other useful information`\n- [Google Analytics columns description](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66046) by Alexander Firsov\n- [More than 10M single user revenue in test set](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66697) by AhmetErdem\n- [Will our models be useful?\n](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66440) by S D\n- [Date vs visitStartTime - explained](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66815#latest-395855) by Yannis Pappas\n- [[Finding] - Pageviews/Hits ratio &lt;0.4 guarantees no revenue](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/66774) by Adams\n- [Finding : totals_bounces and totals_transactionRevenue](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/65989) by Maxwell\n\nIt is the material that I arrange others documentation. because it was hard to keep searching. I hope it helps someone. Tell me if you can add anything.",
    "396805": "Oh, Thanks. Very good to see all the important discussions about this competition!",
    "397260": "Can you add a section with feature engineering ? cheers",
    "397401": "It's a good idea. However, features do not put people into the kernel or discussions because of their rankings. And need to verify that this is a good feature. yet, I'll try adding the proven features like `pageviews / hits.`. Thanks idea",
    "397402": "haha. Thanks"
  },
  "source": "meta"
}