{"_id":"57fa6178f9c7091700d0d099","parentDoc":null,"user":"5668fa9755e4b32100935d41","__v":1,"project":"5668fab608f90021008e882f","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":"5697430b69393517000c82b5","version":"5668fab608f90021008e8832","__v":3,"pages":["56975a3d59a6692d003fadae","56a2c3dff4f3410d008a84dc","56d88ca37a04df0b00ddf1c7"],"project":"5668fab608f90021008e882f","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-14T06:41:15.588Z","from_sync":false,"order":10,"slug":"faq-troubleshooting","title":"FAQ / Troubleshooting"},"githubsync":"","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-10-09T15:25:44.514Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":6,"body":"LiftIgniter reports the metrics of interest to you during the trial. In some cases, you may wish to verify these metrics against third party tools, and also connect them with other metrics tracked by these tools.\n\nBelow are some notes on using Google Analytics for verification.\n\nSee also our guide on [debugging analytics discrepancies](doc:debugging-analytics-discrepancies).\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Verifying pageviews directly driven by clicks\"\n}\n[/block]\nYou can verify the number of pageviews that occur *directly* as a result of clicks on recommendations using the URL tags that we insert in recommendations tracked by LiftIgniter. This will work unless you called our setNoTag function or otherwise overrode our tagging.\n\nTo verify these numbers, go to Behavior > Site Content > All Pages. In the search bar, enter `li_source=LI` to filter to pageviews driven by LiftIgniter. If doing an A/B test, you can enter `li_source=base` to filter to pageviews driven by the corresponding baseline.\n\nIf you want to filter to pageviews driven by recommendations on a particular widget, you can enter `li_source=LI&li_medium=<widgetname>`, or, for the base slice, `li_source=base&li_medium=<widgetname>`.\n\nIf you are doing a 50/50 A/B test then comparing the pageview numbers for LiftIgniter and the baseline should help confirm our lifts. Note that numbers reported will never fully match between different analytics sources, but they should be in the same ballpark and the directional trends should match\n\nSome example images are provided below. Although not included in the pasted images, you should see, below them in the page, more information on the number of pageviews of specific click URLs as well.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/14c00f3-li-ga-verification.png\",\n        \"li-ga-verification.png\",\n        2838,\n        868,\n        \"#eef2f4\"\n      ],\n      \"caption\": \"Verification of overall number of pageviews driven directly by LiftIgniter recommendations using Google Analytics.\"\n    }\n  ]\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/78df1ed-li-specific-widget-ga-verification.png\",\n        \"li-specific-widget-ga-verification.png\",\n        2846,\n        864,\n        \"#eef2f4\"\n      ],\n      \"caption\": \"Verification of number of pageviews on a specific widget driven directly by LiftIgniter recommendations using Google Analytics.\"\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Tracking number of widget shown events\"\n}\n[/block]\nBy default, Google Analytics will not track the number of times our widget was *shown*. If you'd like to have this number verified using Google Analytics, you'd need to send [custom events to Google Analytics](https://developers.google.com/analytics/devguides/collection/analyticsjs/events) in the same part of the code where you call LiftIgniter's tracking function.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Cautionary note against UTM tags and pages/session calculation\"\n}\n[/block]\nAn important thing to remember if using UTM tags in your URLs: every time a user visits a page with UTM tags, Google Analytics starts a new session for that user. Therefore, if you are interested in doing a pages/session calculation, you should not add UTM tags in internal links. For more, see [here](https://support.google.com/analytics/answer/6205762?hl=en).","excerpt":"","slug":"verification-using-google-analytics","type":"basic","title":"Verification using Google Analytics"}

Verification using Google Analytics


LiftIgniter reports the metrics of interest to you during the trial. In some cases, you may wish to verify these metrics against third party tools, and also connect them with other metrics tracked by these tools. Below are some notes on using Google Analytics for verification. See also our guide on [debugging analytics discrepancies](doc:debugging-analytics-discrepancies). [block:api-header] { "type": "basic", "title": "Verifying pageviews directly driven by clicks" } [/block] You can verify the number of pageviews that occur *directly* as a result of clicks on recommendations using the URL tags that we insert in recommendations tracked by LiftIgniter. This will work unless you called our setNoTag function or otherwise overrode our tagging. To verify these numbers, go to Behavior > Site Content > All Pages. In the search bar, enter `li_source=LI` to filter to pageviews driven by LiftIgniter. If doing an A/B test, you can enter `li_source=base` to filter to pageviews driven by the corresponding baseline. If you want to filter to pageviews driven by recommendations on a particular widget, you can enter `li_source=LI&li_medium=<widgetname>`, or, for the base slice, `li_source=base&li_medium=<widgetname>`. If you are doing a 50/50 A/B test then comparing the pageview numbers for LiftIgniter and the baseline should help confirm our lifts. Note that numbers reported will never fully match between different analytics sources, but they should be in the same ballpark and the directional trends should match Some example images are provided below. Although not included in the pasted images, you should see, below them in the page, more information on the number of pageviews of specific click URLs as well. [block:image] { "images": [ { "image": [ "https://files.readme.io/14c00f3-li-ga-verification.png", "li-ga-verification.png", 2838, 868, "#eef2f4" ], "caption": "Verification of overall number of pageviews driven directly by LiftIgniter recommendations using Google Analytics." } ] } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/78df1ed-li-specific-widget-ga-verification.png", "li-specific-widget-ga-verification.png", 2846, 864, "#eef2f4" ], "caption": "Verification of number of pageviews on a specific widget driven directly by LiftIgniter recommendations using Google Analytics." } ] } [/block] [block:api-header] { "type": "basic", "title": "Tracking number of widget shown events" } [/block] By default, Google Analytics will not track the number of times our widget was *shown*. If you'd like to have this number verified using Google Analytics, you'd need to send [custom events to Google Analytics](https://developers.google.com/analytics/devguides/collection/analyticsjs/events) in the same part of the code where you call LiftIgniter's tracking function. [block:api-header] { "type": "basic", "title": "Cautionary note against UTM tags and pages/session calculation" } [/block] An important thing to remember if using UTM tags in your URLs: every time a user visits a page with UTM tags, Google Analytics starts a new session for that user. Therefore, if you are interested in doing a pages/session calculation, you should not add UTM tags in internal links. For more, see [here](https://support.google.com/analytics/answer/6205762?hl=en).