{"_id":"57fbf0d535c9ad0e00ac8a73","version":{"_id":"5668fab608f90021008e8832","__v":19,"project":"5668fab608f90021008e882f","createdAt":"2015-12-10T04:08:22.769Z","releaseDate":"2015-12-10T04:08:22.769Z","categories":["5668fab708f90021008e8833","569740f124490c3700170a64","569742b58560a60d00e2c25d","569742bd0b09a41900b2446c","569742cd69393517000c82b3","569742f459a6692d003fad8f","569743020b09a41900b2446d","5697430b69393517000c82b5","56a17776470ae00d00c30642","56a2c48a831e2a0d0069b1ad","56b535757bccae0d00e9a1cd","56e1ff6aa49fdc0e005746b5","57e1c88115bf6522002a5e4e","57fa65275ba65a17008b988f","57fbeea34002550e004c032e","58474584889b6c2d00fb86e9","58475dcc64157f0f002f1907","587e7b5158666c2700965d4e","58a349fc30852819007ba083"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.18.0","version":"1.18"},"category":{"_id":"57fbeea34002550e004c032e","project":"5668fab608f90021008e882f","__v":0,"version":"5668fab608f90021008e8832","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-10-10T19:40:19.460Z","from_sync":false,"order":12,"slug":"liftigniter-lab","title":"LiftIgniter Lab"},"githubsync":"","user":"5668fa9755e4b32100935d41","__v":1,"project":"5668fab608f90021008e882f","parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-10-10T19:49:41.864Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"The [Analytics Panel](https://lab.liftigniter.com/analytics) of the LiftIgniter Lab allows you to get analytics at a glance.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/2fde64e-analytics-panel.png\",\n        \"analytics-panel.png\",\n        1532,\n        1092,\n        \"#e2e7ed\"\n      ],\n      \"caption\": \"Sample LiftIgniter analytics panel. Note that data shown here is blended across different customers and therefore may not be internally consistent.\"\n    }\n  ]\n}\n[/block]\nAll sections of the Analytics Panel are controlled by the date range picker on the top left. As you change the date range, the numbers and charts in each section will change.\n\nWith the exception of the \"Most Clicked\" section, data for all other sections is available only at daily granularity, with days in Pacific Time, and updated daily around 6 AM Pacific Time with the previous day's data. Therefore, information for today and (if early AM Pacific Time, yesterday) will be missing. You can get the more up-to-date data from the [RealTime Panel](doc:realtime-panel); however, this data does not have the same combinations of drilldowns and the numbers are less reliable because real-time data is not deduplicated.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Entrance (% of Pageviews)\"\n}\n[/block]\nThe breakdown here is not specific to LiftIgniter widgets but rather covers your site-wide pageviews (as tracked by LiftIgniter). For each pageview (not necessarily the first pageview of a session) we look at the referrer to the first pageview of its session. We then classify this referrer as direct, media, search, social, sponsored, or unknown. For more on the available referrers, see [Referrer](doc:referrer), and count the percentages.\n\nIn particular, if two types of referrers refer the same number of sessions, but one of them creates much longer sessions on average, it will show up as contributing to a higher percentage of pageviews.\n\nNote that this data is available by default only for customers who use our JavaScript beacon to send activity data. For customers using our API integration, you will need to include a `sessionReferrer` field in activities specifying the referrer of the session in order to see this data.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"API calls\"\n}\n[/block]\nFor customers who use our JavaScript beacon, this is the number of widgets you registered over the date range for which you successfully fetch recommendations. Note that success is measured on the server side: if our model server receives the request and completes computing the response, it is counted as an API call. It is possible that the API call is counted even though the recommendations are not actually rendered (for instance, because the user bounces off the page).\n\nThe number of API calls as reported here should match the number of API calls that you see in your monthly bill, if your bill includes a cost component for API call fees.\n\nThis API calls number does not include any calls made by LiftIgniter internally as part of status checks, or any calls made through the LiftIgniter Lab to test recommendation quality.\n\nIf you have not yet launched LiftIgniter recommendation, the API call number should be 0, or close to 0 (it could be a little more if you were testing recommendations).\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Most Clicked (Normalized Score)\"\n}\n[/block]\nThis is a list of the most clicked items over the date range. The normalized score is obtained as follows: we take the 20 most clicked items over the date range, and then express the clicks on each of the top 20 as a percentage of the total number of clicks on the top 20.\n\nWe do not show items that do not exist in our inventory. In particular, if you have fast-moving inventory, selecting an older date range might show an empty list.\n\nYou can get more up-to-date and detailed information on clicked items in the [RealTime Panel](doc:realtime-panel). This will include items no longer in the inventory as well, though these will show up only as the URL rather than the title.\n\nThis list starts populating only after you have launched tracking on LiftIgniter recommendations.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Performance chart\"\n}\n[/block]\nThe performance chart is the centerpiece of the Analytics Panel. It allows you to get a bird's-eye view of how LiftIgniter has been doing on your overall traffic as well as how it has been doing on specific traffic segments.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/d812b86-analytics-panel-performance-chart.png\",\n        \"analytics-panel-performance-chart.png\",\n        1524,\n        744,\n        \"#e4e9f0\"\n      ],\n      \"caption\": \"Performance chart section of the Analytics Panel.\"\n    }\n  ]\n}\n[/block]\nHere's the different options you can change in the chart:\n\n* Metric: You can change the metric between the different metrics available. Note that some metrics are under \"Click\", some are under \"Engagement\", and some are under \"Conversion\". You may need to toggle between these on the right before being able to access your desired metric. For a full description of available metrics and what they mean, see [Metrics summary](doc:metrics-summary).\n* Widget: LiftIgniter recommendations are shown in widgets, and you can get all metrics separately for each widget. You can also select \"overall\" to get combined numbers across widgets.\n* Referrer: You can filter traffic by referrer type (direct, social, search, media, sponsored, unknown) and get all metrics for the filtered traffic.\n* Device: You can filter traffic by device type (desktop, mobile, tablet, unknown) and get all metrics for the filtered traffic.\n* Granularity: You can select a granularity of day, week, month, year, day-of-week, and month-of-year. For day, week, month, and year granularities, we group data based on your selected granularity and show it using the earliest data point of the time period. For day-of-week granularity, we show the weekly cycle, choosing the most recent week for labels. For month-of-year, we show the annual cycle.\n* Plot error margins: This plots the error margins as separate graphs for the metrics displayed. You can therefore see the error margins for each data point.\n\nIn addition, you can change the date range at the top of the Analytics Panel.\n\nOn the top right, you see a summary of the numbers: the overall value of the numbers for LiftIgniter and baseline over the entire time period selected, along with error margins (when the number is a ratio). If applicable, a percentage lift will also be shown.\n\nBelow the graph, you will see the summary of the metric totals for that metric. If the metric is defined as a ratio of two other metrics, then data for those other metrics is also included.\n\nFrom the bottom right, you can download a CSV summary of the data. This includes all metrics in the given selection (Click, Engagement, or Conversion).","excerpt":"","slug":"analytics-panel","type":"basic","title":"Analytics Panel"}
The [Analytics Panel](https://lab.liftigniter.com/analytics) of the LiftIgniter Lab allows you to get analytics at a glance. [block:image] { "images": [ { "image": [ "https://files.readme.io/2fde64e-analytics-panel.png", "analytics-panel.png", 1532, 1092, "#e2e7ed" ], "caption": "Sample LiftIgniter analytics panel. Note that data shown here is blended across different customers and therefore may not be internally consistent." } ] } [/block] All sections of the Analytics Panel are controlled by the date range picker on the top left. As you change the date range, the numbers and charts in each section will change. With the exception of the "Most Clicked" section, data for all other sections is available only at daily granularity, with days in Pacific Time, and updated daily around 6 AM Pacific Time with the previous day's data. Therefore, information for today and (if early AM Pacific Time, yesterday) will be missing. You can get the more up-to-date data from the [RealTime Panel](doc:realtime-panel); however, this data does not have the same combinations of drilldowns and the numbers are less reliable because real-time data is not deduplicated. [block:api-header] { "type": "basic", "title": "Entrance (% of Pageviews)" } [/block] The breakdown here is not specific to LiftIgniter widgets but rather covers your site-wide pageviews (as tracked by LiftIgniter). For each pageview (not necessarily the first pageview of a session) we look at the referrer to the first pageview of its session. We then classify this referrer as direct, media, search, social, sponsored, or unknown. For more on the available referrers, see [Referrer](doc:referrer), and count the percentages. In particular, if two types of referrers refer the same number of sessions, but one of them creates much longer sessions on average, it will show up as contributing to a higher percentage of pageviews. Note that this data is available by default only for customers who use our JavaScript beacon to send activity data. For customers using our API integration, you will need to include a `sessionReferrer` field in activities specifying the referrer of the session in order to see this data. [block:api-header] { "type": "basic", "title": "API calls" } [/block] For customers who use our JavaScript beacon, this is the number of widgets you registered over the date range for which you successfully fetch recommendations. Note that success is measured on the server side: if our model server receives the request and completes computing the response, it is counted as an API call. It is possible that the API call is counted even though the recommendations are not actually rendered (for instance, because the user bounces off the page). The number of API calls as reported here should match the number of API calls that you see in your monthly bill, if your bill includes a cost component for API call fees. This API calls number does not include any calls made by LiftIgniter internally as part of status checks, or any calls made through the LiftIgniter Lab to test recommendation quality. If you have not yet launched LiftIgniter recommendation, the API call number should be 0, or close to 0 (it could be a little more if you were testing recommendations). [block:api-header] { "type": "basic", "title": "Most Clicked (Normalized Score)" } [/block] This is a list of the most clicked items over the date range. The normalized score is obtained as follows: we take the 20 most clicked items over the date range, and then express the clicks on each of the top 20 as a percentage of the total number of clicks on the top 20. We do not show items that do not exist in our inventory. In particular, if you have fast-moving inventory, selecting an older date range might show an empty list. You can get more up-to-date and detailed information on clicked items in the [RealTime Panel](doc:realtime-panel). This will include items no longer in the inventory as well, though these will show up only as the URL rather than the title. This list starts populating only after you have launched tracking on LiftIgniter recommendations. [block:api-header] { "type": "basic", "title": "Performance chart" } [/block] The performance chart is the centerpiece of the Analytics Panel. It allows you to get a bird's-eye view of how LiftIgniter has been doing on your overall traffic as well as how it has been doing on specific traffic segments. [block:image] { "images": [ { "image": [ "https://files.readme.io/d812b86-analytics-panel-performance-chart.png", "analytics-panel-performance-chart.png", 1524, 744, "#e4e9f0" ], "caption": "Performance chart section of the Analytics Panel." } ] } [/block] Here's the different options you can change in the chart: * Metric: You can change the metric between the different metrics available. Note that some metrics are under "Click", some are under "Engagement", and some are under "Conversion". You may need to toggle between these on the right before being able to access your desired metric. For a full description of available metrics and what they mean, see [Metrics summary](doc:metrics-summary). * Widget: LiftIgniter recommendations are shown in widgets, and you can get all metrics separately for each widget. You can also select "overall" to get combined numbers across widgets. * Referrer: You can filter traffic by referrer type (direct, social, search, media, sponsored, unknown) and get all metrics for the filtered traffic. * Device: You can filter traffic by device type (desktop, mobile, tablet, unknown) and get all metrics for the filtered traffic. * Granularity: You can select a granularity of day, week, month, year, day-of-week, and month-of-year. For day, week, month, and year granularities, we group data based on your selected granularity and show it using the earliest data point of the time period. For day-of-week granularity, we show the weekly cycle, choosing the most recent week for labels. For month-of-year, we show the annual cycle. * Plot error margins: This plots the error margins as separate graphs for the metrics displayed. You can therefore see the error margins for each data point. In addition, you can change the date range at the top of the Analytics Panel. On the top right, you see a summary of the numbers: the overall value of the numbers for LiftIgniter and baseline over the entire time period selected, along with error margins (when the number is a ratio). If applicable, a percentage lift will also be shown. Below the graph, you will see the summary of the metric totals for that metric. If the metric is defined as a ratio of two other metrics, then data for those other metrics is also included. From the bottom right, you can download a CSV summary of the data. This includes all metrics in the given selection (Click, Engagement, or Conversion).