{"_id":"58474d8c098dbf3900807354","category":{"_id":"58474584889b6c2d00fb86e9","version":"5668fab608f90021008e8832","__v":0,"project":"5668fab608f90021008e882f","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-12-06T23:11:00.646Z","from_sync":false,"order":13,"slug":"drilldowns","title":"Drilldowns"},"githubsync":"","parentDoc":null,"project":"5668fab608f90021008e882f","__v":0,"user":"5668fa9755e4b32100935d41","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"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-12-06T23:45:16.521Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"This page describes how to get LiftIgniter performance analytics associated with in-app browsing for common apps such as Facebook, Twitter, and Pinterest. Currently, we are correctly tracking in-app browsing only for Android phones.\n\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"requestWith value\"\n}\n[/block]\nWe read the name of the request header \"X-Requested-With\" and store that in a field called `requestWith`. \n\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"App\",\n    \"h-1\": \"Common requestWith values\",\n    \"0-0\": \"Standard Android (not in-app)\",\n    \"0-1\": \"com.android.browser, com.android.browser42, com.htc.sense.browser\",\n    \"1-0\": \"Facebook\",\n    \"1-1\": \"com.facebook.katana, com.facebook.katanb, com.facebook.lite, com.facebook.orca\",\n    \"3-0\": \"Instagram\",\n    \"3-1\": \"com.instagram.android\",\n    \"2-0\": \"Twitter\",\n    \"2-1\": \"com.twitter.android\",\n    \"4-0\": \"Pinterest\",\n    \"4-1\": \"com.pinterest\"\n  },\n  \"cols\": 2,\n  \"rows\": 5\n}\n[/block]\nYou might see many requestWith values not in the above list. Common examples of other requestWith headers are those related to Amazon, antivirus software, dev/testing browsers (usually by developers), and specific nonstandard browsers (such as Internet Explorer on Android).\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Places where requestWith drilldown can be used\"\n}\n[/block]\nPresently, the requestWith drilldown can only be used in the [RealTime Panel](doc:realtime-panel) for the real-time chart. It cannot be used anywhere else.","excerpt":"","slug":"in-app-browsing","type":"basic","title":"In-app browsing"}
This page describes how to get LiftIgniter performance analytics associated with in-app browsing for common apps such as Facebook, Twitter, and Pinterest. Currently, we are correctly tracking in-app browsing only for Android phones. [block:api-header] { "type": "basic", "title": "requestWith value" } [/block] We read the name of the request header "X-Requested-With" and store that in a field called `requestWith`. [block:parameters] { "data": { "h-0": "App", "h-1": "Common requestWith values", "0-0": "Standard Android (not in-app)", "0-1": "com.android.browser, com.android.browser42, com.htc.sense.browser", "1-0": "Facebook", "1-1": "com.facebook.katana, com.facebook.katanb, com.facebook.lite, com.facebook.orca", "3-0": "Instagram", "3-1": "com.instagram.android", "2-0": "Twitter", "2-1": "com.twitter.android", "4-0": "Pinterest", "4-1": "com.pinterest" }, "cols": 2, "rows": 5 } [/block] You might see many requestWith values not in the above list. Common examples of other requestWith headers are those related to Amazon, antivirus software, dev/testing browsers (usually by developers), and specific nonstandard browsers (such as Internet Explorer on Android). [block:api-header] { "type": "basic", "title": "Places where requestWith drilldown can be used" } [/block] Presently, the requestWith drilldown can only be used in the [RealTime Panel](doc:realtime-panel) for the real-time chart. It cannot be used anywhere else.