{"__v":0,"_id":"5719767ec863120e0012a052","category":{"version":"5719767ec863120e0012a042","project":"56008ba98c0c9d0d00dcaeb0","_id":"5719767ec863120e0012a048","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-03-03T23:58:04.955Z","from_sync":false,"order":3,"slug":"techy-questions","title":"Techie Questions"},"parentDoc":null,"project":"56008ba98c0c9d0d00dcaeb0","user":"56008b651503430d007cc929","version":{"__v":4,"_id":"5719767ec863120e0012a042","hasDoc":true,"hasReference":true,"project":"56008ba98c0c9d0d00dcaeb0","createdAt":"2016-04-22T00:55:26.295Z","releaseDate":"2016-04-22T00:55:26.295Z","categories":["5719767ec863120e0012a043","5719767ec863120e0012a044","5719767ec863120e0012a045","5719767ec863120e0012a046","5719767ec863120e0012a047","5719767ec863120e0012a048","5719767ec863120e0012a049","57f45a18da14e71700d12e4a","582b71b15403840f008c0410","58c060cf3eee111b00a8b210"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"2.0.0","version":"2.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-03-09T23:21:10.976Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"Adding ThisData might seem scary, so let's answer the scary questions.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Do you block users from logging in?\"\n}\n[/block]\nNo, ThisData sits _after_ the log-in flow. So no matter how you authenticate users (username & password, SSO, etc), we won't get in the way.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"What happens if ThisData's API goes down?\"\n}\n[/block]\nSince ThisData sits after the login flow, your users should be unaffected. To ensure this is the case, you might want to add some error handling around the HTTP request. [Our official libraries](doc:libraries) handle this for you.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Will you slow down my log in process?\"\n}\n[/block]\n [Our official libraries](doc:libraries) use asynchronous (non-blocking) HTTP calls to the ThisData API. If you manually send us requests, you might want to do this in a new thread, or a background job. Otherwise yes, when you synchronously call ThisData's API within your login flow, there will be a small delay as the request is sent.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Will you email users when they first sign up to my app?\"\n}\n[/block]\nNo. No notifications or alerts will be generated for the first login event we see for a user - we don't know anything about them, so the activity is treated as \"normal\".\n\nIf your user logs in later in an unusual way, only _then_ will we send them a \"Was This You?\" notification. Additionally, there are some other times when we will or will not send notifications: see [when and where we send notifications](doc:was-this-you-notifications-when-and-where).\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Will you spam my users?\"\n}\n[/block]\nNo! We will only notify your users about unusual activity, and only when you've told us to. See [when and where we send notifications](doc:was-this-you-notifications-when-and-where).\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"How do I know if my users are getting your emails?\"\n}\n[/block]\nThe ThisData dashboard shows the number of notifications we are sending. These also appear in the Audit tab. In the Audit tab you can also see any deliverability issues we are running in to.\n\nThisData will send \"Was This You\" emails to your end users on your behalf. We use [Mandrill](https://mandrillapp.com/), a popular email service, to achieve this. \n\nEmail deliverability can be tricky, though! For most of our customers, these emails will contain your name and logo in the email, but be sent from `security:::at:::thisdata.com`. This is the easiest way to ensure your users receive and can respond to the emails quickly.","excerpt":"Adding ThisData might seem scary, so let's answer the scary questions","slug":"how-do-you-not-break-my-app","type":"basic","title":"How do you not break my app?"}

How do you not break my app?

Adding ThisData might seem scary, so let's answer the scary questions

Adding ThisData might seem scary, so let's answer the scary questions. [block:api-header] { "type": "basic", "title": "Do you block users from logging in?" } [/block] No, ThisData sits _after_ the log-in flow. So no matter how you authenticate users (username & password, SSO, etc), we won't get in the way. [block:api-header] { "type": "basic", "title": "What happens if ThisData's API goes down?" } [/block] Since ThisData sits after the login flow, your users should be unaffected. To ensure this is the case, you might want to add some error handling around the HTTP request. [Our official libraries](doc:libraries) handle this for you. [block:api-header] { "type": "basic", "title": "Will you slow down my log in process?" } [/block] [Our official libraries](doc:libraries) use asynchronous (non-blocking) HTTP calls to the ThisData API. If you manually send us requests, you might want to do this in a new thread, or a background job. Otherwise yes, when you synchronously call ThisData's API within your login flow, there will be a small delay as the request is sent. [block:api-header] { "type": "basic", "title": "Will you email users when they first sign up to my app?" } [/block] No. No notifications or alerts will be generated for the first login event we see for a user - we don't know anything about them, so the activity is treated as "normal". If your user logs in later in an unusual way, only _then_ will we send them a "Was This You?" notification. Additionally, there are some other times when we will or will not send notifications: see [when and where we send notifications](doc:was-this-you-notifications-when-and-where). [block:api-header] { "type": "basic", "title": "Will you spam my users?" } [/block] No! We will only notify your users about unusual activity, and only when you've told us to. See [when and where we send notifications](doc:was-this-you-notifications-when-and-where). [block:api-header] { "type": "basic", "title": "How do I know if my users are getting your emails?" } [/block] The ThisData dashboard shows the number of notifications we are sending. These also appear in the Audit tab. In the Audit tab you can also see any deliverability issues we are running in to. ThisData will send "Was This You" emails to your end users on your behalf. We use [Mandrill](https://mandrillapp.com/), a popular email service, to achieve this. Email deliverability can be tricky, though! For most of our customers, these emails will contain your name and logo in the email, but be sent from `security@thisdata.com`. This is the easiest way to ensure your users receive and can respond to the emails quickly.