{"_id":"56ec9485406ab51700200633","user":"5668fa9755e4b32100935d41","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"},"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"},"parentDoc":null,"project":"5668fab608f90021008e882f","__v":1,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-03-18T23:51:33.709Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"If you encounter errors or have difficulties that are not resolved by reading this guide, or that our guide suggests that you contact us about, please email us at [support:::at:::liftigniter.com](mailto:support@liftigniter.com).\n\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"1. Urgent live issues for an already-launched product\"\n}\n[/block]\nOur expected response time for urgent live issues is: \n\n* Within 2 hours for queries sent during working hours on a business day (Monday to Friday, Pacific Time, 10 AM through 6 PM).\n* By 12 PM of the next business day for queries sent during non-work hours during the business week.\n* Within 12 hours for queries sent at other times.\n\nWe generally strive for much faster response times, and will generally provide at least a partial response as soon as possible.\n\nFor customers who already have LiftIgniter recommendations in production, and are experiencing issues with the recommendations, we strive to provide answers to questions as quickly as possible. These include issues with the recommendations we are returning, the way the recommendations are being rendered, and server issues such as timeouts.\n\nThe most likely reason for an already running system to suddenly stop working is changes to the inventory metadata. Please review our documentation on [Editing Fields/Hiding Item](doc:checking-data-fields), and in particular compare the set of fields you are requesting in recommendations with what LiftIgniter returns.\n\nIf writing to us about an urgent live issue, please include the following information:\n\n* The URL of the page where you are experiencing the issue (since some issues are specific to particular URLs).\n* As much information as possible from the Chrome Network Panel (see [Console Debugging](doc:console-debugging) for more information) including the full URL of the query sent to query.petametrics.com.\n* The most up-to-date code you are running on the client-side to register, fetch, render and track recommendations.\n\nPlease keep in mind that while we can diagnose the issue from our side and identify the source of the problem, we may not be able to rectify it if the problem is not with code or data that LiftIgniter directly controls. If your team's engineers or developers are not available to make the fix, we can do an emergency shutoff of LiftIgniter's recommendations if you need.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"2. Questions about product features\"\n}\n[/block]\nExpected initial response times regarding product features:\n\n* Within 4 hours for queries sent during working hours on a business day (Monday to Friday, Pacific Time, 10 AM through 6 PM).\n* By 2 PM of the next business day for queries sent during non-work hours during the business week.\n* Within 24 hours for queries sent at other times.\n\nIf you have questions about LiftIgniter's features, such as how a particular feature works, or how to implement a given functionality using LiftIgniter, you can contact us. We strive to provide an initial response within the timeframe indicated above. However, depending on the precise question and your use case, it may take more time to resolve the question fully. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"3. Code Review and Feature Activations\"\n}\n[/block]\nWe offer a free email-based Code Review service for the following:\n\n* **Rendering, tracking, and A/B testing implementation** for customers using our Javascript SDK. We strongly recommend using this service prior to pushing your code to production.\n* **Server-side code** including code to send requests or data to the activity, inventory, and model query API.\n\nAlso, for some features, we require you to contact LiftIgniter in order to be able to activate those features. Examples include [Recommend from category](doc:recommend-specific-category-of-items) and [Cross-site recommendation](doc:cross-site-recommendation).\n\nOur expected response time for Code Review and Feature Activation is 1 to 2 business days. Our working hours are Monday through Friday, Pacific Time.\n\nPlease budget the time for Code Review and Feature Activation when working on the integration.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"4. Recommendation quality, analytics, and performance\"\n}\n[/block]\nFor queries related to recommendation quality, analytics, and performance, we expect to be able to provide an initial response within 1 to 2 business days. Depending on the nature of the question, it may take longer to fully resolve the question.","excerpt":"","slug":"support","type":"basic","title":"Support"}
If you encounter errors or have difficulties that are not resolved by reading this guide, or that our guide suggests that you contact us about, please email us at [support@liftigniter.com](mailto:support@liftigniter.com). [block:api-header] { "type": "basic", "title": "1. Urgent live issues for an already-launched product" } [/block] Our expected response time for urgent live issues is: * Within 2 hours for queries sent during working hours on a business day (Monday to Friday, Pacific Time, 10 AM through 6 PM). * By 12 PM of the next business day for queries sent during non-work hours during the business week. * Within 12 hours for queries sent at other times. We generally strive for much faster response times, and will generally provide at least a partial response as soon as possible. For customers who already have LiftIgniter recommendations in production, and are experiencing issues with the recommendations, we strive to provide answers to questions as quickly as possible. These include issues with the recommendations we are returning, the way the recommendations are being rendered, and server issues such as timeouts. The most likely reason for an already running system to suddenly stop working is changes to the inventory metadata. Please review our documentation on [Editing Fields/Hiding Item](doc:checking-data-fields), and in particular compare the set of fields you are requesting in recommendations with what LiftIgniter returns. If writing to us about an urgent live issue, please include the following information: * The URL of the page where you are experiencing the issue (since some issues are specific to particular URLs). * As much information as possible from the Chrome Network Panel (see [Console Debugging](doc:console-debugging) for more information) including the full URL of the query sent to query.petametrics.com. * The most up-to-date code you are running on the client-side to register, fetch, render and track recommendations. Please keep in mind that while we can diagnose the issue from our side and identify the source of the problem, we may not be able to rectify it if the problem is not with code or data that LiftIgniter directly controls. If your team's engineers or developers are not available to make the fix, we can do an emergency shutoff of LiftIgniter's recommendations if you need. [block:api-header] { "type": "basic", "title": "2. Questions about product features" } [/block] Expected initial response times regarding product features: * Within 4 hours for queries sent during working hours on a business day (Monday to Friday, Pacific Time, 10 AM through 6 PM). * By 2 PM of the next business day for queries sent during non-work hours during the business week. * Within 24 hours for queries sent at other times. If you have questions about LiftIgniter's features, such as how a particular feature works, or how to implement a given functionality using LiftIgniter, you can contact us. We strive to provide an initial response within the timeframe indicated above. However, depending on the precise question and your use case, it may take more time to resolve the question fully. [block:api-header] { "type": "basic", "title": "3. Code Review and Feature Activations" } [/block] We offer a free email-based Code Review service for the following: * **Rendering, tracking, and A/B testing implementation** for customers using our Javascript SDK. We strongly recommend using this service prior to pushing your code to production. * **Server-side code** including code to send requests or data to the activity, inventory, and model query API. Also, for some features, we require you to contact LiftIgniter in order to be able to activate those features. Examples include [Recommend from category](doc:recommend-specific-category-of-items) and [Cross-site recommendation](doc:cross-site-recommendation). Our expected response time for Code Review and Feature Activation is 1 to 2 business days. Our working hours are Monday through Friday, Pacific Time. Please budget the time for Code Review and Feature Activation when working on the integration. [block:api-header] { "type": "basic", "title": "4. Recommendation quality, analytics, and performance" } [/block] For queries related to recommendation quality, analytics, and performance, we expect to be able to provide an initial response within 1 to 2 business days. Depending on the nature of the question, it may take longer to fully resolve the question.