{
  "id": 71665,
  "title": "which taget is used by kaggle",
  "url": "/competitions/ga-customer-revenue-prediction/discussion/71665",
  "author_name": "",
  "post_date": "2018-11-15T12:39:14.049538400Z",
  "votes": 11,
  "comment_count": 8,
  "views": 0,
  "content": "<p>We have two tagets in the dataset : totals.totalTransactionRevenue and totals.transactionRevenue\nThe official documentation says that totals.transactionRevenue is deprecated.</p>\n\n<p>I tried the one Line script to test which one kaggle is using on LB and the results are :\ntotals.transactionRevenue : score is 0.0\ntotals.totalTransactionRevenue : score is 0.03</p>\n\n<p>so it seems that kaggle is using the deprecated target and it would be nice from kaggle to let us know which taget to use.</p>",
  "messages": [
    {
      "id": "421796",
      "postDate": "11/15/2018 12:39:14",
      "content": "<p>We have two tagets in the dataset : totals.totalTransactionRevenue and totals.transactionRevenue\nThe official documentation says that totals.transactionRevenue is deprecated.</p>\n\n<p>I tried the one Line script to test which one kaggle is using on LB and the results are :\ntotals.transactionRevenue : score is 0.0\ntotals.totalTransactionRevenue : score is 0.03</p>\n\n<p>so it seems that kaggle is using the deprecated target and it would be nice from kaggle to let us know which taget to use.</p>",
      "rawMarkdown": "We have two tagets in the dataset : totals.totalTransactionRevenue and totals.transactionRevenue\nThe official documentation says that totals.transactionRevenue is deprecated.\n\nI tried the one Line script to test which one kaggle is using on LB and the results are :\ntotals.transactionRevenue : score is 0.0\ntotals.totalTransactionRevenue : score is 0.03\n\nso it seems that kaggle is using the deprecated target and it would be nice from kaggle to let us know which taget to use.",
      "votes": null
    },
    {
      "id": "421915",
      "postDate": "11/15/2018 15:04:12",
      "content": "<p>I've created a <a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71260#latest-419925\">discussion here</a> about that, but no answer from kaggle so far. I think the real target is transactionRevenue, but it would be good to know the difference between both features.</p>",
      "rawMarkdown": "I've created a [discussion here](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71260#latest-419925) about that, but no answer from kaggle so far. I think the real target is transactionRevenue, but it would be good to know the difference between both features.",
      "votes": null
    },
    {
      "id": "422035",
      "postDate": "11/15/2018 17:49:38",
      "content": "<p>The main problem is the big difference in scores, 0.03 is huge.\n1) Since Google considers that totals.transactionRevenue  is deprecated and if Kaggle is still using it on LB, then we are building a wrong model.\n2) What guarantee do we have that totals.transactionRevenue will still be used by Google by the end of January 2019? and that Kaggle would not switch to totals.totalTransactionRevenue for the private LB?</p>",
      "rawMarkdown": "The main problem is the big difference in scores, 0.03 is huge.\n1) Since Google considers that totals.transactionRevenue  is deprecated and if Kaggle is still using it on LB, then we are building a wrong model.\n2) What guarantee do we have that totals.transactionRevenue will still be used by Google by the end of January 2019? and that Kaggle would not switch to totals.totalTransactionRevenue for the private LB?",
      "votes": null
    },
    {
      "id": "422229",
      "postDate": "11/15/2018 23:46:51",
      "content": "<p>I totally agree. My guess is that totalTransactionRevenue also includes some tax or shipping</p>",
      "rawMarkdown": "I totally agree. My guess is that totalTransactionRevenue also includes some tax or shipping",
      "votes": null
    },
    {
      "id": "422343",
      "postDate": "11/16/2018 05:00:59",
      "content": "<p>I assume it's totals.totalTransactionRevenue as totals.transactionRevenue is depricated according to <a href=\"https://support.google.com/analytics/answer/3437719?hl=en\">https://support.google.com/analytics/answer/3437719?hl=en</a></p>",
      "rawMarkdown": "I assume it's totals.totalTransactionRevenue as totals.transactionRevenue is depricated according to https://support.google.com/analytics/answer/3437719?hl=en",
      "votes": null
    },
    {
      "id": "422658",
      "postDate": "11/16/2018 15:26:48",
      "content": "<p>No, Kaggle is using totals.transactionRevenue even though it's deprecated</p>",
      "rawMarkdown": "No, Kaggle is using totals.transactionRevenue even though it's deprecated",
      "votes": null
    },
    {
      "id": "422673",
      "postDate": "11/16/2018 15:51:40",
      "content": "<p>This question seems to be asked in many threads. I've looked into this here:\n<a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71779\">https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71779</a></p>\n\n<p>Sorry for opening yet another thread on this, but it seems that totals.transactionRevenue is meaningless as opposed to totals.totalTransactionRevenue.</p>",
      "rawMarkdown": "This question seems to be asked in many threads. I've looked into this here:\nhttps://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71779\n\nSorry for opening yet another thread on this, but it seems that totals.transactionRevenue is meaningless as opposed to totals.totalTransactionRevenue.",
      "votes": null
    },
    {
      "id": "422703",
      "postDate": "11/16/2018 16:46:14",
      "content": "<p>I hope that after the competition is scored next year, Kaggle would release the dataset it used to calculate the private score, so that competitors can double check at home.  I wouldn't want to be a competitor on the bubble and wonder whether my result was calculated with the correct target variable.</p>",
      "rawMarkdown": "I hope that after the competition is scored next year, Kaggle would release the dataset it used to calculate the private score, so that competitors can double check at home.  I wouldn't want to be a competitor on the bubble and wonder whether my result was calculated with the correct target variable.",
      "votes": null
    },
    {
      "id": "424038",
      "postDate": "11/19/2018 13:16:51",
      "content": "<p><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/70982#422808\">https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/70982#422808</a></p>\n\n<p>Refer to this one. Phil is saying that it is transaction revenue..</p>",
      "rawMarkdown": "https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/70982#422808\n\nRefer to this one. Phil is saying that it is transaction revenue..",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 421915,
      "author_name": "jsaguiar",
      "author_url": "",
      "post_date": "11/15/2018 15:04:12",
      "content": "<p>I've created a <a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71260#latest-419925\">discussion here</a> about that, but no answer from kaggle so far. I think the real target is transactionRevenue, but it would be good to know the difference between both features.</p>",
      "votes": null,
      "replies": [
        {
          "id": 422035,
          "author_name": "mchahhou",
          "author_url": "",
          "post_date": "11/15/2018 17:49:38",
          "content": "<p>The main problem is the big difference in scores, 0.03 is huge.\n1) Since Google considers that totals.transactionRevenue  is deprecated and if Kaggle is still using it on LB, then we are building a wrong model.\n2) What guarantee do we have that totals.transactionRevenue will still be used by Google by the end of January 2019? and that Kaggle would not switch to totals.totalTransactionRevenue for the private LB?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 422229,
          "author_name": "jsaguiar",
          "author_url": "",
          "post_date": "11/15/2018 23:46:51",
          "content": "<p>I totally agree. My guess is that totalTransactionRevenue also includes some tax or shipping</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 422343,
      "author_name": "michalgdak",
      "author_url": "",
      "post_date": "11/16/2018 05:00:59",
      "content": "<p>I assume it's totals.totalTransactionRevenue as totals.transactionRevenue is depricated according to <a href=\"https://support.google.com/analytics/answer/3437719?hl=en\">https://support.google.com/analytics/answer/3437719?hl=en</a></p>",
      "votes": null,
      "replies": [
        {
          "id": 422658,
          "author_name": "mchahhou",
          "author_url": "",
          "post_date": "11/16/2018 15:26:48",
          "content": "<p>No, Kaggle is using totals.transactionRevenue even though it's deprecated</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 422673,
      "author_name": "antoniorossi",
      "author_url": "",
      "post_date": "11/16/2018 15:51:40",
      "content": "<p>This question seems to be asked in many threads. I've looked into this here:\n<a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71779\">https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71779</a></p>\n\n<p>Sorry for opening yet another thread on this, but it seems that totals.transactionRevenue is meaningless as opposed to totals.totalTransactionRevenue.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 422703,
      "author_name": "dmitriyguller",
      "author_url": "",
      "post_date": "11/16/2018 16:46:14",
      "content": "<p>I hope that after the competition is scored next year, Kaggle would release the dataset it used to calculate the private score, so that competitors can double check at home.  I wouldn't want to be a competitor on the bubble and wonder whether my result was calculated with the correct target variable.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 424038,
      "author_name": "suchith0312",
      "author_url": "",
      "post_date": "11/19/2018 13:16:51",
      "content": "<p><a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/70982#422808\">https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/70982#422808</a></p>\n\n<p>Refer to this one. Phil is saying that it is transaction revenue..</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "421796": "We have two tagets in the dataset : totals.totalTransactionRevenue and totals.transactionRevenue\nThe official documentation says that totals.transactionRevenue is deprecated.\n\nI tried the one Line script to test which one kaggle is using on LB and the results are :\ntotals.transactionRevenue : score is 0.0\ntotals.totalTransactionRevenue : score is 0.03\n\nso it seems that kaggle is using the deprecated target and it would be nice from kaggle to let us know which taget to use.",
    "421915": "I've created a [discussion here](https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71260#latest-419925) about that, but no answer from kaggle so far. I think the real target is transactionRevenue, but it would be good to know the difference between both features.",
    "422035": "The main problem is the big difference in scores, 0.03 is huge.\n1) Since Google considers that totals.transactionRevenue  is deprecated and if Kaggle is still using it on LB, then we are building a wrong model.\n2) What guarantee do we have that totals.transactionRevenue will still be used by Google by the end of January 2019? and that Kaggle would not switch to totals.totalTransactionRevenue for the private LB?",
    "422229": "I totally agree. My guess is that totalTransactionRevenue also includes some tax or shipping",
    "422343": "I assume it's totals.totalTransactionRevenue as totals.transactionRevenue is depricated according to https://support.google.com/analytics/answer/3437719?hl=en",
    "422658": "No, Kaggle is using totals.transactionRevenue even though it's deprecated",
    "422673": "This question seems to be asked in many threads. I've looked into this here:\nhttps://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/71779\n\nSorry for opening yet another thread on this, but it seems that totals.transactionRevenue is meaningless as opposed to totals.totalTransactionRevenue.",
    "422703": "I hope that after the competition is scored next year, Kaggle would release the dataset it used to calculate the private score, so that competitors can double check at home.  I wouldn't want to be a competitor on the bubble and wonder whether my result was calculated with the correct target variable.",
    "424038": "https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/70982#422808\n\nRefer to this one. Phil is saying that it is transaction revenue.."
  },
  "source": "meta"
}