{"_id":"576a656d6f15260e001f8977","parentDoc":null,"project":"54aa7f773b56130b0056c86e","githubsync":"","user":"54aa7f3f9bb00c0b00cb899b","category":{"_id":"576a656c6f15260e001f893e","__v":0,"project":"54aa7f773b56130b0056c86e","version":"576a656c6f15260e001f8938","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-01-05T12:45:04.262Z","from_sync":false,"order":4,"slug":"faq","title":"FAQ"},"__v":1,"version":{"_id":"576a656c6f15260e001f8938","__v":3,"project":"54aa7f773b56130b0056c86e","createdAt":"2016-06-22T10:16:12.661Z","releaseDate":"2016-06-22T10:16:12.661Z","categories":["576a656c6f15260e001f8939","576a656c6f15260e001f893a","576a656c6f15260e001f893b","576a656c6f15260e001f893c","576a656c6f15260e001f893d","576a656c6f15260e001f893e","576a656c6f15260e001f893f","5797787ce2d8f40e0052b4a6","5b041bc0769904000374c645"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"For Marketers","version_clean":"4.0.0","version":"4.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-01-05T12:51:49.545Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"What happens to users inside a segment if they change their behaviour?\"\n}\n[/block]\nSegments are dynamic, meaning that the users can drop in and out of segments in real-time based on changes in their behaviour or location. So for example, if you build a segment today and there are 1,500 users that match the criteria you have set, it might not be the same number of users the next day, it fluctuates in real time.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Why doesn't my geofence work?\"\n}\n[/block]\nAs we rely on highly variable parameters from users devices, results when using geofences can sometimes differ. Occasionally geofences will not trigger or they trigger too late, this can be due to very inaccurate data being sent back by the device (over which we have not control). Some users (a minority) keep all location services on the device turned off due to privacy concerns meaning geofencing does not work at all. \n\nIn rare cases a geofence might trigger slightly before the user crosses the boundary threshold, this can be down to location accuracy of the device.\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"What size should I make my Geofences?\"\n}\n[/block]\nWe recommend 150-200 meters or larger for optimal results (but not exceeding 1000 meters). \n\nResults may vary depending on the distance from the nearest cell tower and the battery level of the user's device. In urban areas we have had a 98% success rate when testing geofences of 150 meters and larger.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Does location tracking wear down my customers battery?\"\n}\n[/block]\nNo, we have tested this extensively. Our proprietary geolocation  technology which is a part of the Pulsate SDK uses new methods of retrieving highly accurate location data while have zero impact on battery life.\n\nNot convinced? Implement our SDK, test it out, and see for yourself.\n\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"How secure is my data?\"\n}\n[/block]\nWe use bank grade security, implementing 256-bit encryption, secure socket layers and firewalls to keep your data safe and secure.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Where does Pulsate store data?\"\n}\n[/block]\nWe store all data securely on the Amazon cloud within their EU data centre which is located in Ireland.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"What data does Pulsate collect and store concerning my customers?\"\n}\n[/block]\nPulsate is fully compliant with all of the relevant data protection and privacy regulations including GDPR. \n\nFor a full overview on Pulsate's data protection and customer data policies, please see our [Privacy Policy](https://pulsate.readme.io/v4.0/docs/introduction).","excerpt":"","slug":"common-questions","type":"basic","title":"Frequently asked questions"}

Frequently asked questions


[block:api-header] { "type": "basic", "title": "What happens to users inside a segment if they change their behaviour?" } [/block] Segments are dynamic, meaning that the users can drop in and out of segments in real-time based on changes in their behaviour or location. So for example, if you build a segment today and there are 1,500 users that match the criteria you have set, it might not be the same number of users the next day, it fluctuates in real time. [block:api-header] { "type": "basic", "title": "Why doesn't my geofence work?" } [/block] As we rely on highly variable parameters from users devices, results when using geofences can sometimes differ. Occasionally geofences will not trigger or they trigger too late, this can be due to very inaccurate data being sent back by the device (over which we have not control). Some users (a minority) keep all location services on the device turned off due to privacy concerns meaning geofencing does not work at all. In rare cases a geofence might trigger slightly before the user crosses the boundary threshold, this can be down to location accuracy of the device. [block:api-header] { "type": "basic", "title": "What size should I make my Geofences?" } [/block] We recommend 150-200 meters or larger for optimal results (but not exceeding 1000 meters). Results may vary depending on the distance from the nearest cell tower and the battery level of the user's device. In urban areas we have had a 98% success rate when testing geofences of 150 meters and larger. [block:api-header] { "type": "basic", "title": "Does location tracking wear down my customers battery?" } [/block] No, we have tested this extensively. Our proprietary geolocation technology which is a part of the Pulsate SDK uses new methods of retrieving highly accurate location data while have zero impact on battery life. Not convinced? Implement our SDK, test it out, and see for yourself. [block:api-header] { "type": "basic", "title": "How secure is my data?" } [/block] We use bank grade security, implementing 256-bit encryption, secure socket layers and firewalls to keep your data safe and secure. [block:api-header] { "type": "basic", "title": "Where does Pulsate store data?" } [/block] We store all data securely on the Amazon cloud within their EU data centre which is located in Ireland. [block:api-header] { "type": "basic", "title": "What data does Pulsate collect and store concerning my customers?" } [/block] Pulsate is fully compliant with all of the relevant data protection and privacy regulations including GDPR. For a full overview on Pulsate's data protection and customer data policies, please see our [Privacy Policy](https://pulsate.readme.io/v4.0/docs/introduction).